The Architecture Decision Records (ADR) skill enables Claude to function as a technical architect by identifying and documenting critical decision points during development. It streamlines the creation of standardized ADRs based on the Michael Nygard format, capturing the context, considered alternatives, and long-term consequences of technical choices. By maintaining a living log in your repository, it ensures that the 'why' behind infrastructure, framework, and design patterns is never lost, making it an essential tool for team collaboration, technical debt management, and developer onboarding.
주요 기능
01Structured lifecycle tracking for proposed, accepted, and superseded decisions
02Automatic detection of architectural decision signals in conversation
03214,597 GitHub stars
04Intelligent retrieval of existing decisions for project context
05Automated management of the docs/adr/ directory and index files
06Standardized ADR template capturing rationale, alternatives, and trade-offs
사용 사례
01Recording why a specific database or framework was chosen over alternatives during the planning phase
02Documenting API design choices and breaking changes for future maintainers
03Providing a searchable history of technical trade-offs to onboard new team members