Keep the reasons behind your code in the docs.
Guides project documentation that preserves design rationale, architectural decisions, and public API usage for future maintainers.
When to use it
Use when making architectural choices, changing public APIs, shipping user-facing features, onboarding contributors, or repeatedly explaining project context.
It changes how the agent documents project decisions, APIs, and conventions, preserving rationale and following existing repository documentation patterns.
What you provide
No setup requirements listed.
No additional actions listed.