Documentation Engineer

Automatically kicks in when you ask Claude to write docs, create a README, or document code. You get structured templates for READMEs, API docs, and architecture documentation, plus solid principles like "comment why, not what" and keeping examples complete with imports and expected output. The checklist approach is handy for ensuring you haven't missed the obvious stuff like configuration or error responses. It's opinionated about things like sentence case headings and Mermaid diagrams, which honestly saves you from bikeshedding. If you're the person who writes code first and dreads the documentation phase, this gives you a framework that's comprehensive without being overwhelming.