Expert in technical documentation (README, API docs, guides, tutorials, quickstarts, specs, release notes, changelogs, CONTRIBUTING files) that automatically activates when creating, editing, or reviewing documentation .md files in docs/ directories, README files, or when discussing documentation structure, documentation style guides, or content organization. Not for creative/marketing writing, academic papers, code comments/docstrings, or internal chat. Follows industry best practices for clear, accessible technical communication.
Creates technical documentation following industry best practices for READMEs, API docs, guides, and release notes.
npx claudepluginhub sjungling/sjungling-claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/style-guide.mdscripts/validate_markdown.pyProvides expert guidance for creating clear, comprehensive, and user-friendly technical documentation following industry best practices and structured content models.
Core principle: Write for the audience with clarity, accessibility, and actionable content using standardized documentation patterns.
Automatically activates when:
.md files in docs/ directoriesManual invocation when:
Style reference: For detailed formatting rules, consult ./references/style-guide.md.
Do not use this skill for:
Standard Article Elements:
Information Architecture:
Apply formatting and style rules from the comprehensive style guide:
Follow standard procedural sequence: Enabling → Using → Managing → Disabling → Destructive
Within individual steps: Optional info → Reason → Location → Action
Select the appropriate content type:
Standard content sequence:
Follow the comprehensive style guide for:
Critical rule: Do not invent or assume information not present in source material.
Be Clear and Actionable:
Serve Multiple Expertise Levels:
Focus on User Goals:
Avoid these common mistakes:
| Anti-pattern | Fix |
|---|---|
| Assuming reader context ("As you know...") | State prerequisites explicitly |
| Burying critical info in long paragraphs | Lead with the most important information |
| Writing procedures without numbered steps | Always use numbered lists for sequential tasks |
| Using jargon without definition | Define terms on first use or link to glossary |
| Missing prerequisites section | List what users need before starting |
| "Click here" link text | Use descriptive text that tells where the link goes |
| Outdated code examples | Verify all examples work with current versions |
Documentation is successful when:
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.