From praxis
Documentation writing conventions — style, structure, tone, and quality standards.
How this skill is triggered — by the user, by Claude, or both
Slash command
/praxis:docs-patternsWhen to use
Writing, editing, or reviewing documentation files.
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before writing, **read 2-3 existing docs in the same category** to match their tone and structure.
Before writing, read 2-3 existing docs in the same category to match their tone and structure.
Tone: Technical but accessible. Imperative for instructions ("Use X..."), declarative for specifications ("The User model has these fields..."). No marketing language.
Brevity is paramount. A doc that could be 100 lines should not be 300. Every paragraph must earn its place. If a table communicates it better than prose, use a table. If a link to another doc covers it, don't restate it. Be precise, not exhaustive.
All docs follow a consistent pattern:
[Doc Name](FILENAME.md)npx claudepluginhub jartan-llc/grimoire --plugin praxisGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.