madappgang/claude-code/documentation-standards
- community
- ext:[{"type":"config","description":"Configuration overrides"}]
Checking that the SKILL.md file is still in the repository.
Use when writing README files, API documentation, user guides, or technical documentation following industry standards from Google, Microsoft, and GitLab style guides.
Install
npx vskill@latest install madappgang/claude-code/documentation-standardsSemi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard
SKILL.md
Documentation Standards
Overview
Comprehensive documentation standards based on research from Google, Microsoft, GitLab, Red Hat style guides, and 60+ additional sources. Provides templates, best practices, and anti-pattern detection for AI agents writing documentation.
15 Best Practices (Ranked by Consensus)
UNANIMOUS (100% Agreement)
1. Use Active Voice and Present Tense
Why: Reduces cognitive load 20-30%, shortens sentences 15-25%
Implementation:
Validation: Check for "is/are/was/were + past participle" patterns
2. Start with 5-Minute Quick Start
Why: 70% of visitors are first-time users, time-to-first-success critical
Implementation:
npm install my-tool npx my-tool init npx my-tool start
Validation: Can a new user succeed in under 5 minutes with zero context?
3. Use Progressive Disclosure (Three-Tier Structure)
Why: Accommodates all skill levels, reduces overwhelm
Implementation:
4. Use Second Person ("You")
Why: Increases engagement, reduces word count 15-25%
Implementation:
5. Keep Sentences Under 25 Words
Why: Comprehension drops 30% when sentences exceed 30 words
Implementation:
6. Use Lists and Tables for Comparison
Why: 70% faster comprehension vs paragraphs
Implementation:
STRONG (67%+ Agreement)
7. Use Language-Specific Documentation Tools
Why: Deep language integration, automatic type inference
Decision Matrix:
8. Follow Diataxis Framework
Why: Clear taxonomy reduces confusion
Four Types:
| Type | Purpose | Length | When to Use | |
|---|---|---|---|---|
| Tutorial | Teach by doing | 15-60 min | "I'm new, show me" | |
| How-To | Solve problem | 5-15 min | "I need to do X" | |
| Reference | Describe what exists | As needed | "What parameters?" | |
| Explanation | Clarify concepts | 5-30 min | "Why does this work?" |
9. Show Code Examples with Expected Output
Why: Users know what success looks like
Implementation:
const user = await api.getUserById('user-123'); console.log(user.name, user.email);
John Doe john@example.com
const user = await api.getUserById('invalid-id'); // Throws: NotFoundError: User with ID 'invalid-id' not found
10. Provide Troubleshooting Section
Why: 50%+ of support questions are error-related
Template:
11. Organize by Task ("How do I...")
Why: Users think in terms of goals, not architecture
Implementation:
12. Add Prerequisites Checklist
Why: Eliminates invisible barriers for beginners
Template:
AI-SPECIFIC
13. Verify Examples Actually Work
Why: Prevents hallucination and outdated examples
Process:
- Read function implementation
- Extract actual parameters and return type
- Test example code
- Document actual output
14. Ground Documentation in Source Code
Why: Prevents documenting non-existent features
Process:
- Read source code FIRST
- Only document features that exist
- Use actual type signatures
- If uncertain, qualify with "typically", "generally"
15. Add Version Tracking
Why: Users need to know if docs apply to their version
Template:
7 Ready-to-Use Templates
Template 1: README Quick Start
Purpose: Project landing page with 5-minute setup Max Length: 80 lines Use When: Creating project README
Step 1: Install
npm install my-tool
Step 2: Initialize
npx my-tool init
Step 3: Start
npx my-tool start
Template 2: TSDoc Function Documentation
Purpose: Document TypeScript functions Format: TSDoc standard Use When: Documenting public APIs
Template 3: Error Documentation
Purpose: Document common errors and solutions Organization: By symptom Use When: Creating troubleshooting guides
npm ERR! code EACCES npm ERR! syscall access npm ERR! path /usr/local/lib
npm install --save-dev my-tool npx my-tool
mkdir ~/.npm-global npm config set prefix '~/.npm-global' export PATH=~/.npm-global/bin:$PATH
npm list my-package
// CORRECT import { func } from 'my-package';
// WRONG import { func } from 'my-package/lib/index';
Template 4: Tutorial Structure
Purpose: Teach by doing Length: 15-30 minutes Use When: Creating beginner tutorials
mkdir my-api cd my-api npm init -y
import express from 'express';
const app = express(); const PORT = 3000;
app.get('/', (req, res) => { res.json({ message: 'Hello, World!' }); });
app.listen(PORT, () => { console.log(Server running on http://localhost:${PORT}); });
npm run dev
Server running on http://localhost:3000
curl http://localhost:3000
{"message":"Hello, World!"}
lsof -i :3000 kill -9 <PID>
Template 5: Changelog
Purpose: Track version changes Format: Keep a Changelog standard Use When: Every release
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 98 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/dev/skills/documentation-standards/SKILL.md
Popularity
- Repository stars
- 272
- Repository forks
- 32
- 7-day trend score
- 28
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 6 May 2026, 5 months ago.
Extension points
configConfiguration overrides
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/madappgang/claude-code/documentation-standards)