architecture-decision-records
Create clear architecture decisions fast
Teams lose context when decisions are undocumented or scattered. This skill provides ADR templates, lifecycle guidance, and review checklists to capture decisions consistently.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "architecture-decision-records". Write an ADR to adopt Redis for caching product pages.
Expected outcome:
- ADR-0010: Use Redis for product page caching
- Status: Accepted
- Context: Slow page loads during peak traffic
- Decision: Add Redis as a read through cache
- Consequences: Faster reads, added cache invalidation work
Using "architecture-decision-records". Create an ADR for choosing between REST and GraphQL.
Expected outcome:
- ADR-0015: Use GraphQL for the API layer
- Status: Accepted
- Context: Mobile clients need flexible data fetching
- Decision: Adopt GraphQL with Apollo Server
- Considered: REST API with pagination, Falcor
- Positive: Reduced over-fetching, strong typing
- Negative: Added complexity, caching challenges
Security Audit
SafePure documentation skill containing only templates and guidance for writing Architecture Decision Records. All 56 static findings are false positives: detected patterns are markdown documentation examples, harmless text strings in prose, and legitimate documentation links. No executable code, file access, network activity, or external commands are present.
Risk Factors
🌐 Network access (9)
⚙️ External commands (25)
Quality Score
What You Can Build
Document major choices
Create structured ADRs for database, platform, and integration decisions.
Standardize decision logs
Adopt a consistent ADR process and review checklist across teams.
Review past decisions
Understand historical choices and their consequences during onboarding.
Try These Prompts
Create a lightweight ADR for adopting TypeScript in our frontend. Include context, decision, and consequences.
Write a standard ADR comparing PostgreSQL, MySQL, and MongoDB for our product catalog.
Draft a deprecation ADR to replace MongoDB with PostgreSQL, including a migration plan.
Create an RFC style ADR for event sourcing in order management, with motivation, design, drawbacks, and alternatives.
Best Practices
- Write ADRs before implementation begins
- Record both positive and negative consequences
- Link related ADRs and update status over time
Avoid
- Editing accepted ADRs instead of superseding them
- Omitting context and decision drivers
- Using vague language without clear decisions