What problem does it solve? Keeping a personal Obsidian vault consistent is hard: notes drift in structure, tags multiply, timestamps get guessed, and unverified facts creep into long-term notes. This Skill enforces one canonical note template and workflow so every note you create or edit stays uniform, connected, and trustworthy. ## Core Features & Use Cases - Template enforcement: Applies a fixed frontmatter shape, canonical section headings (Intro, Mental model, How it works, Example, Commands, Further reading, Reference), and nested tag conventions to every note. - Edit-first workflow: Searches the vault before writing, defaults to extending existing notes, adds backlinks to related notes, and reads the vault's base template at 98-Templates/Note Template.md before creating new files. - Fact validation discipline: Requires running date for real timestamps, verifying commands and links against live sources, and marking anything unverifiable instead of guessing. - Use Case: Ask to document a networking concept like Linux bridges; the Skill finds related notes, drafts a concise concept note with a compile-checked D2 diagram, links it both ways, and keeps prose free of em dashes and unverified claims. ## Quick Start Create an Obsidian note in my vault explaining how Linux network namespaces work, following my note template.
