What problem does it solve? Code shows what was built but not why it was built that way. This Skill captures the reasoning behind architectural decisions, API designs, and project conventions so future engineers and AI agents understand the context, constraints, and rejected alternatives behind the codebase. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Write numbered ADRs with context, decision, alternatives considered, and consequences, while matching any existing project convention for location, numbering, and format. - Inline and API Documentation: Add comments that explain intent rather than restating code, plus JSDoc-style annotations and OpenAPI specs for public interfaces. - Project Documentation: Structure READMEs with quick start and commands, maintain changelogs, and keep agent-facing rules files like CLAUDE.md current. - Use Case: After choosing PostgreSQL over MongoDB for a new service, use this Skill to write an ADR documenting the requirements, the alternatives evaluated, and the consequences so the decision is never re-debated months later. ## Quick Start Write an ADR documenting the decision to use PostgreSQL with Prisma as the primary database for this project.
