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.