Obsidian Narrative Vault
This skill enables seamless integration between the codebase and the "BRUTAL" world-building documentation.
Workflow
- •Information Retrieval:
- •Use
mcp_obsidian_search_notesto find relevant lore or design docs. - •Use
mcp_obsidian_read_notesto extract full narrative context.
- •Use
- •Consistency Analysis:
- •Compare code attributes (e.g., Species stats) against lore descriptions.
- •Identify "Narrative Drift" where mechanics no longer match the world description.
- •Documentation Sync:
- •Reference the lore-standards.md for vault structure.
- •Propose updates to lore when mechanics evolve.
Guidelines
- •Lore Over Logic: Narratives define the "feeling" of a species; mechanics should serve that feeling.
- •Search Patterns: Use keywords like
Species/,Regions/, orDesign/to narrow searches.
Artefacts to Update (lore sync)
- •Do NOT edit vault notes directly. When proposing lore changes, add a
./docs/todo/master_todo.mdentry referencing the vault paths and suggested edits. - •If mechanics change based on lore findings, add corresponding entries to
./docs/todo/master_todo.mdand update./.github/skills/species-trait-balancer/SKILL.mdreferences if needed. - •Record references to the exact Obsidian note paths in the master todo to preserve traceability.