obsidian-vault-guide

Standardize Obsidian vault conventions by encoding naming standards and frontmatter metadata to ensure cross-skill compatibility. This provides a structured vault layout that enables automated discovery and reliable execution across dependent workflows.

Frontmatter metadata drives automated discovery and activation by dependent skills. Implementing standardized frontmatter in your Obsidian vault allows other tools to validate note structures and reliably trigger vault operations.

Structure wikilinks using clear vault reference guidelines to support scalable knowledge graphs. Standardized wikilink conventions ensure graph growth remains manageable and interconnected notes are reliably discovered by dependent skills.

Yes, you can use templates to enforce vault design standards in Obsidian. Templates encode frontmatter metadata and naming conventions, ensuring newly created notes automatically comply with cross-skill compatibility requirements.

Vault compatibility implements optional resource directories to support discovery and extension by other skills. These optional directories organize supplementary vault assets while maintaining the standardized layout required for interoperability.

Obsidian notes fail cross-skill validation when frontmatter metadata and naming conventions do not match encoded vault standards. Applying standardized vault layouts and wikilink rules ensures dependent skills can correctly discover and validate notes.