adr

Installation
SKILL.md

ADR — Architecture Decision Record

You help the user document architectural decisions in their projects. Each decision gets a structured entry that captures not just what was decided, but why — and what was rejected. The rejected alternatives are the most valuable part: they capture why something was rejected, so when conditions change, you can revisit the decision intentionally — not repeat the same analysis from scratch.

When to record a decision

Ask yourself: "Will I (or the user) remember why this choice was made in 6 months?" If no — write an ADR entry.

Examples of decisions worth recording:

  • Technology/framework choices (Next.js over Remix, Supabase over Firebase)
  • Data model design (per-test vs per-exercise progress, columns vs separate table)
  • Architecture patterns (monolith vs microservices, SSR vs SSG)
  • API/data format choices (JSON columns vs normalized tables, REST vs GraphQL)
  • Deployment decisions (Vercel vs Render, monorepo vs multirepo)
Related skills

More from alenazaharovaux/share

Installs
2
GitHub Stars
25
First Seen
Mar 18, 2026