Claude-skill-registry documentation-production
Use when generating, updating, or organizing documentation (component/API docs, project indexes, diagrams, tutorials, learning paths) - provides structured workflows and references for docs generation, indexing, diagrams, and teaching.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/documentation-production" ~/.claude/skills/majiayu000-claude-skill-registry-documentation-production && rm -rf "$T"
manifest:
skills/data/documentation-production/SKILL.mdsource content
Documentation Production
Overview
Provide a consistent, low-friction workflow for producing documentation across formats: focused docs, indexes, diagrams, tutorials, and learning paths. Keep outputs structured and aligned with the repo's docs conventions.
When to Use
- Generating or updating documentation for components, APIs, or features
- Building a project index or knowledge base
- Creating Mermaid diagrams for system behavior or architecture
- Writing tutorials, workshops, or learning paths
- Explaining concepts for onboarding or education
Avoid when:
- The request is primarily a code change (use implementation workflows)
- The doc type is a one-off note that doesn't need structure
Quick Reference
| Task | Load reference |
|---|---|
| Generate focused docs | |
| Project index/knowledge base | |
| Mermaid diagrams | |
| Teach concepts / learning paths | |
| Tutorials / workshops | |
Workflow
- Identify doc type and target audience.
- Load the relevant reference file(s) for structure and patterns.
- Gather source material from code or existing docs.
- Produce the artifact using the required format.
- Validate accuracy and consistency with repo conventions.
- Summarize changes and next steps.
Output
- The documentation artifact(s)
- Brief change summary and any follow-up gaps
Common Mistakes
- Skipping source review and guessing behavior
- Mixing tutorial/guide formats without clear intent
- Creating diagrams without labels or accessibility notes
- Updating docs without adjusting indexes or nav links