Agent skill
documentation-best-practices
Provides templates, standards, and best practices for writing clear, comprehensive technical documentation
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/documentation-best-practices
SKILL.md
Overview
This skill provides guidelines for creating high-quality documentation including docstrings, API documentation, README files, and usage guides.
Documentation Coverage Targets
- Public APIs: 100% documented
- Internal Functions: 80%+ documented
- Complex Logic: Must have explanation comments
- Overall: 85%+ coverage
Docstring Templates
Python (Google Style)
def function_name(param1: str, param2: int) -> bool:
"""Brief one-line description.
Longer detailed explanation if needed.
Args:
param1: Description of param1
param2: Description of param2
Returns:
Description of return value
Raises:
ValueError: When and why
"""
JavaScript (JSDoc)
/**
* Brief one-line description.
*
* @param {string} param1 - Description of param1
* @param {number} param2 - Description of param2
* @returns {boolean} Description of return value
* @throws {Error} When and why
*/
README Structure
- Project Title & Description
- Installation: Step-by-step setup
- Usage: Basic examples
- API Documentation: Overview or link
- Contributing: Guidelines (if applicable)
- License: Project license
When to Apply
Use when generating documentation, updating docstrings, creating README files, or maintaining API documentation.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?