Obsidian note templates, naming conventions, and wikilink rules for Zettelkasten output
From reading-assistantnpx claudepluginhub xiaolai/reading-assistant-for-claude --plugin reading-assistantThis skill uses the workspace's default tool permissions.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Designs KPI dashboards with metrics selection (MRR, churn, LTV/CAC), visualization best practices, real-time monitoring, and hierarchy for executives, operations, and product teams.
Transforms raw data into narratives with story structures, visuals, and frameworks for executive presentations, analytics reports, and stakeholder communications.
| Note type | Filename pattern | Wikilink pattern |
|---|---|---|
| MOC | MOC-{book-slug}.md | [[MOC-{book-slug}]] |
| Chapter | {book-slug}-ch{NN}-{title-slug}.md | [[{book-slug}-ch01-intro]] |
| Concept | {concept-slug}.md | [[concept-slug]] |
| Quote | {book-slug}-q{NNN}.md | [[{book-slug}-q001]] |
Concept notes have NO book prefix — they are cross-book by design.
Every note MUST have YAML frontmatter with:
type: moc | chapter | concept | quotebook: full book titleauthor: author nametags: array of tagscreated: ISO dateAdditional per-type:
chapter (number)chapter, speaker, verifiedchapter (where first seen)[[slug]] syntaxWhen obsidian_vault is configured:
obsidian/ contents to {vault}/{book-slug}/