What problem does it solve? Major technical decisions—database selection, architecture patterns, authentication schemes, deployment platforms—often lose their rationale over time, causing teams to revisit settled questions or repeat past mistakes. This Skill captures the context, options, trade-offs, and consequences of each significant decision in a standardized Architecture Decision Record (ADR). ## Core Features & Use Cases - Nygard Lightweight ADR Format: Generates structured ADR documents with status, date, context, considered options, decision, and honest consequences (including negative impacts). - Decision Trees for Common Choices: Provides quick-reference selection guides for databases (PostgreSQL vs MongoDB vs Redis), architecture patterns (Monolith vs Modular Monolith vs Microservices), CAP theorem trade-offs, caching strategies, API styles (REST vs GraphQL vs gRPC), authentication (JWT vs Session vs OAuth), and deployment platforms (Cloudflare Pages, Vercel, Fly.io). - Organized Storage & Indexing: Saves ADRs to docs/adr/ with numbered kebab-case filenames (e.g., ADR-001-use-postgresql-as-primary-database.md) and maintains an index README. - Use Case: When deciding whether to adopt Next.js App Router for a client project, invoke this Skill to produce ADR-002 documenting the alternatives considered, the rationale, and the accepted constraints. ## Quick Start Ask the AI to create an ADR for your current technology decision, such as choosing a database or deployment platform, and save it under docs/adr/.
