Developer documentation including API references, guides, and getting started content
Generates comprehensive developer documentation including quickstarts, tutorials, how-to guides, concepts, and API references. Claude will use this when you need to create or update documentation for a product area, triggered by requests like "write docs for the new auth endpoint" or "create a quickstart for our SDK.
/plugin marketplace add pluginagentmarketplace/custom-plugin-devrel-engineer/plugin install devrel-engineer-plugin@pluginagentmarketplace-devrel-engineerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/docs-structure.yamlreferences/DOCS_GUIDE.mdscripts/doc_generator.pyCreate comprehensive, usable documentation that helps developers succeed.
parameters:
required:
- doc_type: enum[quickstart, tutorial, howto, concept, reference]
- product_area: string
optional:
- api_spec: object
- target_ttfhw: duration
output:
documentation:
content: markdown
code_samples: array[CodeBlock]
navigation: object
| Type | Purpose | Example |
|---|---|---|
| Quickstart | First 5 minutes | "Hello World in 5 min" |
| Tutorial | Learn by doing | "Build your first app" |
| How-to | Solve specific task | "How to authenticate" |
| Concept | Understand system | "How caching works" |
| Reference | Look up details | "API endpoint list" |
Docs Site
├── Getting Started
│ ├── Quickstart
│ ├── Installation
│ └── First API Call
├── Guides
│ ├── Authentication
│ ├── Error Handling
│ └── Best Practices
├── API Reference
│ ├── Endpoints
│ ├── Parameters
│ └── Response Codes
└── Resources
├── FAQ
├── Changelog
└── Migration Guides
# Page Title
Brief intro (what this covers, who it's for)
## Prerequisites
What they need before starting
## Main Content
Step-by-step or organized sections
## Next Steps
What to do after this
Write (MD) → Review (PR) → Build (CI) → Deploy (CD)
↓ ↓ ↓ ↓
Local GitHub Docusaurus Vercel
retry_patterns:
outdated_content:
strategy: "Sync with latest API version"
user_confusion:
strategy: "Add examples, clarify language"
broken_code_samples:
strategy: "Test in CI, fix immediately"
| Failure Mode | Detection | Recovery |
|---|---|---|
| Outdated | API changed | Update with deprecation |
| Broken links | 404 errors | Fix or redirect |
| User can't complete | Feedback | Add missing steps |
□ All code samples tested?
□ Prerequisites complete?
□ Links working?
□ Version numbers specified?
□ Screenshots current?
□ Follows style guide?
test_documentation:
unit_tests:
- test_code_samples:
assert: "All code runs"
- test_links:
assert: "No 404s"
integration_tests:
- test_ttfhw:
assert: "<10 min to first success"
| Metric | Target |
|---|---|
| Time to first success | <10 min |
| Doc search success | >80% |
| Ticket deflection | 60%+ |
| User satisfaction | >4.0/5 |
metrics:
- pages_updated: integer
- code_samples_tested: integer
- user_satisfaction: float
- search_success_rate: float
See assets/ for documentation templates.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.