## Markdown Project File Workflow When creating a markdown (.md) project file for the Obsidian vault, draft it as an email to `tjcherb@plantbasedsoutherner.com` using the format below. ### Device routing - **Phone/mobile** → use `message_compose` tool - **Desktop** → use Gmail API `gmail_create_draft` tool - If device is already known from earlier in the conversation, don't re-ask. - Only create a downloadable `.md` file if I explicitly request it. ### Subject line format ``` [n8n] -t -p ``` - `-t` *(required)* — target folder under `HomeLab/`. n8n auto-prefixes `HomeLab/`, so `-t Tech/Projects` files to `PBS/Tech/Projects`. - `-p` *(required)* — project slug. Lowercase, dashes only, no spaces. Becomes the filename. - Flag order doesn't matter. **Choosing `-t`:** Propose a subfolder path under `HomeLab/` that fits the work — e.g., `Tech/Projects`, `Tech/Sessions`. Nested paths are fine. These are examples, not a fixed menu — if the work suggests a new area, propose it and flag it so we can confirm before filing. **Examples:** ``` [n8n] -t Tech/Projects -p security-hardening [n8n] -t Tech/Sessions -p traefik-debugging ``` ### Markdown body requirements 1. Obsidian-compatible format 2. YAML frontmatter at the top (template below) 3. Obsidian checkbox syntax `- [ ]` for tasks 4. Fenced code blocks for commands and configs ### Frontmatter template ```yaml --- project: type: status: active path: tags: - created: updated: --- ``` **Field reference:** - `project` *(read by n8n)* — must match the `-p` slug. Becomes the filename. - `type` *(Obsidian only, not read by n8n)* — document kind. Standard values: `project-plan`, `session-notes`, `reference`, `content-plan`, `recipe-dev`, `brand-assets`, `tech-setup`, `campaign`. - `status` — `active`, `paused`, `completed`, `archived`. - `tags` — topic tags. Common: `pbs`, `website`, `wordpress`, `content`, `recipe`, `branding`, `sunnie`, `mailerlite`, `youtube`, `instagram`, `sunnies`. - `created` / `updated` — ISO dates (`YYYY-MM-DD`). - `path` — target folder path in your Obsidian vault, so n8n knows exactly where to drop the file. Use the same value you chose for `-t` above (see "Choosing `-t`"). If a `type`, `tag`, or `status` value doesn't fit the standard options, flag it and ask rather than guessing.