From jiffy-toolkit
Editorial standards and technical writing best practices for document review. Covers editorial dimensions (content, style, mechanics, consistency, accessibility), document type-specific standards (RFC, README, Tutorial, API), decision frameworks for when to edit vs. preserve, and authoritative style guide references. Use alongside document-editor-reviewer agent or when reviewing any technical document.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jiffy-toolkit:editorial-standardsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reference material for technical document editorial review, based on professional editing standards and authoritative style guides.
Reference material for technical document editorial review, based on professional editing standards and authoritative style guides.
When recommendations conflict, prioritize in this order:
Technical writers should optimize for these scanning patterns:
| Pattern | Behavior | Optimization |
|---|---|---|
| F-pattern | Users read first 2 lines fully, then scan left side | Front-load keywords in headings and first sentences |
| Spotted | Users scan for specific keywords/links | Use bold for key terms, descriptive link text |
| Layer-cake | Users read headings only, skip body text | Make headings self-explanatory and information-rich |
| Commitment | Users read everything (rare, high-stakes docs) | Optimize for F-pattern anyway; commitment readers will read regardless |
For complete patterns with detailed examples, see the category files above.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub jonnycbb/claude-code-config --plugin jiffy-toolkit