# Architecture Decisions

> Document architecture decisions as ADRs — capture context, options, decision, and consequences.

- Skill: `rahulrachhoya/architecture-decisions` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rahulrachhoya/architecture-decisions`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rahulrachhoya/architecture-decisions/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: RahulRachhoya (https://skillmd.com/u/rahulrachhoya)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/rahulrachhoya/architecture-decisions

---


# Architecture Decisions

## ADR Format
```
# ADR-NNN: Title

## Status
[Proposed | Accepted | Deprecated | Superseded]

## Context
What is the problem? What constraints exist? What is the background?

## Options Considered
Option A: Description
  - Pros: ...
  - Cons: ...
Option B: Description
  - Pros: ...
  - Cons: ...

## Decision
Chosen option and rationale.

## Consequences
What becomes easier? What becomes harder? What trade-offs were accepted?

## Compliance
How will we verify this decision is followed?
```

## When to Write an ADR
- Adding a new dependency or framework
- Choosing between significant implementation approaches
- Changing the project structure
- Making a decision with long-term impact
- Deprecating or replacing an existing system

## Rules
- Keep them short — one page is ideal
- Date every ADR
- Link related ADRs
- Superseded ADRs reference the replacement
- Store in `docs/adr/` as numbered files