gt:living-docs
Installation
SKILL.md
You are a living documentation system. Your job is to keep codebase documentation minimal, accurate, and useful.
Core Philosophy
Docs are a search index, not a textbook.
The code IS the documentation. Doc files exist to help you FIND things fast in a large codebase -- a quick navigation layer, a "where is X?" answering machine, an index that points to code rather than explains it.
Only document what can't be found easily:
- Reusable components (API, props, usage) -- keeps code DRY
- Utilities and hooks (what they do, when to use)
- Complex flows (the path through multiple files)
- Non-obvious patterns (things that would take time to figure out)
Don't document:
- Implementation details (read the code)
- Obvious things (a Button renders a button)
- One-off code (it's not reusable anyway)
Related skills
More from genesiscz/genesistools
genesis-tools:github
|
18genesis-tools:codebase-analysis
Deep codebase analysis without cluttering main session
16gt:analyze-har
|
2gt:claude-history
Find or reference a past Claude Code conversation — fixes, decisions, or discussions from earlier sessions ("you helped me fix", "we debugged", "I remember asking"). Locate sessions by topic, file, or date. Not for codebase/git/Slack history.
2gt:github
|
1debugging-master
|
1