Obsidian Markdown (Vault-Safe)

Goal

Author and edit Markdown that renders correctly in Obsidian, including its extensions (wikilinks, embeds, callouts, properties).

Guardrails

• Keep output Obsidian-safe: prefer wikilinks over relative paths when referring to vault notes.
• Preserve existing block IDs, aliases, and properties unless intentionally changed.
• Avoid features Obsidian does not support (e.g., GitHub task lists with sub-checkbox syntax that differs from Obsidian).
• Use fenced code blocks for code; escape pipes inside tables.

Workflow

1. Confirm context.
   • Identify target vault conventions (title casing, tags, properties).
   • Note existing block IDs and do not regenerate unless requested.
2. Draft with Obsidian syntax.
   • Use wikilinks for internal references; embeds with ![[...]].
   • Add properties/frontmatter only when needed by the vault.
3. Validate structure.
   • Check links: headings [[Note#Heading]], blocks [[Note#^block-id]].
   • Ensure callouts use [!type] and optional +/- for fold state.
   • Escape table pipes and Markdown literals inside links/code.
4. Provide diff-friendly output.
   • Maintain surrounding spacing; avoid trailing spaces unless intentional line breaks.

Common Moves

• Convert Markdown links to wikilinks for internal notes.
• Add block IDs (^id) to paragraphs/lists that will be referenced.
• Wrap guidance/examples in callouts (> [!note] etc.).
• Use properties for tags/aliases; keep YAML minimal and valid.

References (load when needed)

• obsidian-markdown/references/quick-reference.md: syntax snippets for links, embeds, callouts, lists, tables, math, diagrams, comments.
• obsidian-markdown/references/properties-and-tags.md: frontmatter/property types, tag rules, examples.
• obsidian-markdown/references/example-note.md: end-to-end example note using callouts, tasks, code, mermaid.
• obsidian-markdown/references/resources.md: official Obsidian help links.