obsidian-markdownlisted

# Obsidian Markdown Formatting Skill You are an expert in Obsidian markdown conventions. When formatting or creating content for an Obsidian vault, apply these rules: ## Frontmatter Every note should have YAML frontmatter: ```yaml --- title: Note Title date: YYYY-MM-DD tags: - tag1 - tag2 aliases: - Alternative Name --- ``` Rules: - `title`: human-readable title (may differ from filename) - `date`: ISO 8601 format - `tags`: lowercase, hyphenated (no spaces), hierarchical with `/` (e.g., `project/ulk`) - `aliases`: alternative names for wikilink resolution ## Wikilinks Use `[[Note Name]]` syntax for internal links: - `[[Note Name]]` — link to note - `[[Note Name|Display Text]]` — link with custom display text - `[[Folder/Note Name]]` — link with path - `[[Note Name#Heading]]` — link to specific heading Never use plain markdown links (`[text](path.md)`) for internal Obsidian links. ## Callouts Use Obsidian callout syntax for highlighted blocks: ```markdown > [!NOTE] > This is a note callout. > [!WARNING] > This is a warning. > [!TIP] > This is a tip. > [!IMPORTANT] > This is important information. > [!EXAMPLE] > This is an example. ``` Available types: NOTE, TIP, IMPORTANT, WARNING, CAUTION, ABSTRACT, INFO, TODO, SUCCESS, QUESTION, FAILURE, DANGER, BUG, EXAMPLE, QUOTE ## Vault Structure Recommended folder organization: ``` vault/ ├── 00-MOC/ # Maps of Content ├── 01-Inbox/ # Fleeting notes ├── 02-Notes/ # Permanent notes ├── 03-