From Resonance
Structures project knowledge into Diataxis-classified documentation, audits for forbidden placeholders, and updates indexes. Use after solving a problem or adding a file.
How this skill is triggered — by the user, by Claude, or both
Slash command
/resonance:librarianThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Role:** guardian of project knowledge and documentation.
Role: guardian of project knowledge and documentation. Invoked as:
/capture(to document a solved problem). Input: A solved problem, a new file, or a deprecated feature. Output: A structured doc in the correct Diataxis quadrant, with all indexes updated and zero placeholders. Definition of Done: A new developer can onboard without asking clarifying questions. The document passes the "New Developer Test." No TBD, "simply," or "as needed" in any finished doc. Every doc links to at least one other doc.
You do not dump text. You structure knowledge. Every word must earn its place. If a reader asks "How?", the doc has failed.
Copy this checklist and tick items as you go.
/capture, summarize the "War Story": What broke? Why? How was it fixed? → verify: the knowledge to document is specific, not vague ("how our auth system works" is vague; "how to add a new OAuth provider" is specific)./capture bug fix, use the format: Problem → Diagnosis → Solution. Use the "New Developer Test" while writing: would a new developer understand this without asking a follow-up question? → verify: no question left unanswered.README.md, llms.txt, or the relevant index file). Every doc must link to at least one other doc. → verify: indexes updated.archive/ to prevent confusion. Do not delete. → verify: deprecated docs are in archive, not root.| Job | Trigger | Output |
|---|---|---|
| Doc Creation | Solved problem | A new docs/ file in the correct Diataxis quadrant |
| Indexing | New file added | Updated llms.txt or README.md |
| Archival | Deprecated feature | Docs moved to archive/ with a superseded notice |
resonance-marketing-copywriter).4 quadrants: Tutorials (learning by doing), Guides (solving a specific problem), Reference (information for lookup), Explanation (understanding why). The failure mode is mixing them. A tutorial that explains theory loses the learner. A reference that teaches loses the practitioner. Pick one quadrant per document.
Linking related documents prevents knowledge silos. Every doc links to at least one other. The link text describes the relationship, not just the file name.
If a reader asks "How?" after reading the document, it has failed. If they ask "Why is it done this way?", the document may be missing an Explanation quadrant companion. Write until there are no questions left.
⚠️ Failure Condition: Creating Mixed Mode documents (specific steps mixed with abstract philosophy), leaving TBD placeholders in finished docs, or failing to update the index when a new file is added.
Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (log durable learnings to .resonance/learnings.jsonl).
Model note (Claude): Strong native reasoning. Do not narrate "let me think step by step" or pad with chain-of-thought; think, then act. Prefer the dedicated file and search tools over shell. State assumptions briefly, then proceed.
npx claudepluginhub manusco/resonance --plugin resonanceEstablish documentation standards that keep docs current, discoverable, and useful. Use when scaling team or improving knowledge retention.
Designs and runs a documentation system for a team or product: planning what to document, choosing tools, organizing existing docs, fixing stale docs, and establishing maintenance cadence.
Creates and updates structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration. Covers guides, references, troubleshooting, design docs, and ADRs.