Architecture Decision Records help teams capture important choices about system design. These lightweight documents explain why a decision was made and what impact it will have. They include the context, the decision, the consequences, and any alternatives considered.
Developers and architects use ADRs to keep a clear history of technical choices. New team members can quickly understand past decisions. This skill provides ready-to-use templates that follow the well-known Nygard format. It helps you avoid repeating old debates and makes your team's reasoning clear.
Use this skill whenever you make a significant architectural choice. It guides you to write a record that everyone can follow. The templates ensure you include all key sections. Your project will have a durable memory of how and why it evolved.
Global
mkdir -p ~/.claude/skills/architecture-decision-recordProject
mkdir -p .claude/skills/architecture-decision-recordSource Repository
Grill With Docsmattpocock/skills
Stress-test your plan, refine your terms, and update docs instantly
Lark Doclarksuite/cli
Create read summarize edit translate and manage Lark cloud documents
To Prdmattpocock/skills
Generate a complete PRD from your conversation and codebase understanding
Github Actions Docsxixu-me/skills
Answers your GitHub Actions questions with exact official documentation links
Readme I18nxixu-me/skills
Localize your repo READMEs automatically with structure and selector intact
Domain Modelingmattpocock/skills
Define clear terms and record key decisions for a shared project language
Ubiquitous Languagemattpocock/skills
Build a shared glossary of terms from your conversations with clear definitions
Edit Articlemattpocock/skills
Polish your article drafts by improving clarity structure and flow