create-doc
Skill42 starsChanged 6 months agoMITView on GitHub
Create a new documentation file following project standards. Detects overlap with existing docs before creating.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- skeletonlabs/skeletontheir own version, first seen Oct 8, 2026
- avibebuilder/claude-primetheir own version, first seen May 10, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- skeletonlabs/skeleton★ 6.1ksame name
- avibebuilder/claude-prime★ 119same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-creatorSkill
- anti-overengineeringSkill
- audit-docsSkill
- auto-reviewSkill
- architectureSkill
- clean-codeSkill
- commitSkill
- dddSkill
- discoverySkill
- docs-indexSkill
- e2eSkill
- event-stormingSkill
- implement-featureSkill
- product-managerSkill
- refactor-featureSkill
- refactoring-mikado-stranglerSkill
- review-backSkill
- review-docSkill
- review-followupSkill
- review-frontSkill
- review-fullstackSkill
- securitySkill
- shipSkill
- skill-creatorSkill
- solidSkill
- dashboard-stylingSkill
- tddSkill
- update-docsSkill
- worktreeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read .claude/roles/documentalist.md — adopt this profile and follow all its rules.
- Distinctive: line 23
If the subject is vague, ask:
- Distinctive: line 30
MANDATORY: before any creation.
- Distinctive: line 41
STOP — do not create a new file
- Distinctive: line 48
Add links to existing sections
- Very specific: line 82
Run /docs-index to regenerate docs/INDEX.md with the new file.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create Documentation
Activation
This skill activates for:
- Creating a new documentation file
- Documenting a feature, a concept, or a component
/create-doc
Persona
Read .claude/roles/documentalist.md — adopt this profile and follow all its rules.
Workflow
Step 1: Clarify the Subject
If the subject is vague, ask:
- Which component/feature to document?
- Target audience: contributor, user, LLM?
- Scope:
reference,guide,architecture, orspec?
Step 2: Detect Duplicates
MANDATORY before any creation.
# List all existing docs
Glob docs/**/*.md
# Read the titles and H2/H3 of each file
# Compare with the requested subjectIf an existing doc already covers the subject:
- STOP — do not create a new file
- Suggest updating the existing doc via
/update-docs - Explain which file covers what
If partial overlap:
- Identify precisely which sections already exist
- The new doc must cover ONLY the missing content
- Add links to existing sections
Step 3: Create the File
Apply the template from PERSONA.md:
---
title: <Title>
scope: reference | guide | architecture | spec
related:
- src/path/to/source.ts
- docs/RELATED-DOC.md
last-updated: YYYY-MM-DD
---Writing rules:
- English only
- 1-2 summary sentences after the title
- One section = one concept
- Tables rather than lists for structured data
- Code blocks rather than prose for technical details
- Max 800 words — split if longer
Step 4: Naming
| Location | Convention |
docs/ top-level | SCREAMING-KEBAB.md (e.g., MCP-TOOLS-REFERENCE.md) |
| Subdirectory | kebab-case.md (e.g., docs/mcp/architecture.md) |
Step 5: Update the Index
Run /docs-index to regenerate docs/INDEX.md with the new file.
Anti-patterns
| Forbidden | Do Instead |
| Duplicate existing content | Link to the canonical source |
| Doc > 800 words | Split into multiple files |
| Sections unrelated to the title | Create a separate doc |
| Prose when a table suffices | Use a table |
| Mixing French and English | Everything in English |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

