Delegate independent tasks to specialized agents working concurrently with isolated context.
Document Feature: $ARGUMENTS
Generate technical and user documentation for a feature
SKILL.md
Full skill instructions
Document Feature: $ARGUMENTS
Generate comprehensive documentation for a feature in both developer and user-friendly formats.
Process
Phase 1: Feature Analysis
- Identify feature type: Frontend, Backend, or Full-stack
- Gather technical context: Files, types, dependencies, data flow
- Analyze user interaction: UI elements, step-by-step journey
Search in: /components/, /app/, /lib/, /types/, /contexts/
Phase 2: Developer Documentation
Create: docs/dev/$ARGUMENTS-implementation.md
Required sections:
- Overview and quick reference
- Architecture (component structure, data flow, types)
- Implementation details (core logic, state, events)
- Code examples (basic and advanced)
- Testing (coverage, manual checklist)
- Integration guide (config, dependencies)
- API reference (if applicable)
- Maintenance (known issues, future work)
Phase 3: User Documentation
Create: docs/user/how-to-$ARGUMENTS.md
Required sections:
- Overview (what it does, benefits)
- Getting started (prerequisites, access)
- Step-by-step instructions with screenshot placeholders
- Common use cases/scenarios
- Tips and best practices (do's, don'ts, pro tips)
- Troubleshooting (common problems + solutions)
- FAQ
- Related features
Phase 4: Screenshot List
Create: docs/screenshots/$ARGUMENTS-screenshots-needed.txt
List all screenshots needed with:
- Filename
- What to show
- What to highlight
Phase 5: Cross-References
- Update main documentation index
- Add links to related docs
- Update CLAUDE.md if new patterns introduced
Naming Conventions
| Type | Pattern | Example |
|---|---|---|
| Dev docs | [feature]-implementation.md | dark-mode-implementation.md |
| User docs | how-to-[feature].md | how-to-dark-mode.md |
| Screenshots | [feature]-[context].png | dark-mode-toggle.png |
Quality Standards
Developer docs: Technically accurate, includes file paths and line numbers, proper terminology
User docs: Non-technical language, visual aids, clear actionable steps, scannable formatting
Output Checklist
- Dev doc at correct path with all sections
- User doc at correct path with all sections
- Screenshot placeholder list generated
- Code examples syntactically correct
- Cross-references added
- Technical accuracy verified against code
More Other skills
brand-guidelines
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.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
