Documentation
This skill teaches Claude to write documentation that explains why code exists rather than what it does. It covers folder READMEs with mental models, JSDoc with usage context and examples, and inline comments for non-obvious decisions. The approach assumes readers can parse code themselves but need help understanding architectural intent and design rationale. Built by epicenter, it pairs with separate skills for writing voice and notebook explanations. If you're tired of documentation that just restates function names or lists files without explaining the organizing principle, this gives Claude a framework for actually useful docs.
- skills.sh installs
- 188
- GitHub stars
- 4.8K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add epicenterhq/epicenter --skill documentation --agent claude-codeInstalls into .claude/skills of the current project.
Files
Documentation
Follow the project writing conventions. For architecture walkthroughs, folder mental models, or newcomer explanations, lead with the owner, boundary, or flow; ground the model in code and name the likely misconception when it helps.
Documentation explains why, not what. Users can read code to see what it does. They need you to explain the reasoning.
Folder READMEs
Primary job: explain why this folder exists and the mental model.
Open with the useful model: what this folder owns, why it exists, and what boundary future edits should preserve.
Can Include
- ASCII art diagrams for complex relationships
- Overview of key exports or entry points
- Brief file descriptions IF they add context beyond the filename
- Relationships to other folders
Avoid
- Exhaustive file listings that just duplicate
ls - Descriptions that repeat the filename ("auth.ts - authentication")
- Implementation details better expressed in code
Good
# Converters
Transform field schemas into format-specific representations.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageDetails
- Repository
- github.com/epicenterhq/epicenter
- Category
- Documentation
- First seen
- Jun 3, 2026
More from epicenterhq/epicenter
All 2Recommended
More Documentation
generate-component-documentationlongbridge/gpui-componentGenerate documentation for new components. Use when writing docs, documenting components, or creating component documentation.172skills.sh installs
storybook-component-documentationthebushidocollective/hanUse when creating or improving component documentation in Storybook. Helps generate comprehensive docs using MDX, autodocs, and JSDoc comments.165skills.sh installs
doca-programming-guideNVIDIA/skillsUse this skill when the user is writing their first DOCA app or asking a library-agnostic programming question — picking a shipped sample to copy and modify, wi151skills.sh installs
gemini-guidejezweb/claude-skillsLook up Gemini API documentation, SDK patterns, and current best practices when building with Google Gemini. Maps topics to local cached docs and live sources, 149skills.sh installs
documentationEpicenterHQ/epicenterIn-code documentation, folder READMEs, and code comments. Use when writing README.md files, JSDoc comments, or explaining code organization.0skills.sh installs
doc-syncJetBrains/ideavimKeeps IdeaVim documentation in sync with code changes. Use this skill when you need to verify documentation accuracy after code changes, or when checking if doc0skills.sh installs