Skip to content
Document Feature: $ARGUMENTS logo

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

  1. Identify feature type: Frontend, Backend, or Full-stack
  2. Gather technical context: Files, types, dependencies, data flow
  3. 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:

  1. Overview and quick reference
  2. Architecture (component structure, data flow, types)
  3. Implementation details (core logic, state, events)
  4. Code examples (basic and advanced)
  5. Testing (coverage, manual checklist)
  6. Integration guide (config, dependencies)
  7. API reference (if applicable)
  8. Maintenance (known issues, future work)

Phase 3: User Documentation

Create: docs/​user/​how-to-$ARGUMENTS.md

Required sections:

  1. Overview (what it does, benefits)
  2. Getting started (prerequisites, access)
  3. Step-by-step instructions with screenshot placeholders
  4. Common use cases/​scenarios
  5. Tips and best practices (do's, don'ts, pro tips)
  6. Troubleshooting (common problems + solutions)
  7. FAQ
  8. 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

TypePatternExample
Dev docs[feature]-implementation.mddark-mode-implementation.md
User docshow-to-[feature].mdhow-to-dark-mode.md
Screenshots[feature]-[context].pngdark-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

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K
View

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.

179.7K 100.1K
View

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.

179.7K 89.5K
View

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.).

179.7K 76.1K
View

Fundamental design principles for writing maintainable, testable Python code.

40.2K 21.9K
View

Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.

40.2K 20K
View

Generate Playwright tests from scenarios using interactive browser exploration and validation.

39.7K 18.2K
View

Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.

40.2K 14.7K
View

GDPR-compliant data handling with consent management, data subject rights, and privacy controls.

40.2K 14.3K
View

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.

40.2K 13.5K
View

Detailed multi-file refactor planning with safety checks and rollback guidance.

39.7K 13K
View