Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
If the user has not specified a decision topic, ask for it before proceeding. One clarifying question is sufficient — ask for the decision, the context that led to it, and any alternatives they considered.
Write an ADR using the MADR (Markdown Any Decision Records) template below. Fill in all sections based on what the user has provided. Use direct, factual language throughout.
# [Short title describing the decision and its solution]
## Status
[Proposed | Accepted | Deprecated | Superseded by ADR-XXX]
## Context
[Describe the problem, constraint, or situation that made this decision necessary.
Include any relevant technical context, business requirements, or constraints.
This section answers: what forced us to make a decision?]
## Decision
[State the decision clearly and directly.
Start with "We will..." or "We decided to..."
Explain the key reasoning in one to three sentences.]
## Alternatives considered
- **[Alternative 1]**: [Brief description]. Rejected because [reason].
- **[Alternative 2]**: [Brief description]. Rejected because [reason].
## Consequences
**Positive:**
- [What becomes easier, faster, or safer as a result]
**Negative:**
- [What becomes harder, more expensive, or constrained as a result]
**Neutral:**
- [Things that change but are neither clearly good nor bad]
After writing the document, check whether either of these directories exists:
docs/adr/docs/decisions/If one exists, offer to save the file there with a filename following the pattern NNNN-short-title.md where NNNN is the next sequential number (check existing files to determine the sequence). If neither directory exists, output the document to the conversation and suggest the user create docs/adr/ and save it there.
Do not combine multiple decisions into one ADR. If the user describes two distinct decisions, write two separate ADRs.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.
The English summary is being prepared. Showing the original description.