Architecture Compass

Goal

Set up ADR governance or align/review code against explicit ADRs, stack rules, runtime boundaries, and approved examples. In setup and new-repo modes, record every bundled guardrail as adopted, adapted, deferred, or rejected; conflicting target evidence requires an explicit rejection decision and rationale. Produce durable agent instructions, minimal reversible changes, and validation evidence.

When to use

• The user asks to set up ADR usage, ADR guardrails, or agent instructions in a repository.
• The user asks to make future agents rely on provided ADRs.
• The user asks to refactor existing code to match ADRs, architecture docs, stack rules, or approved examples.
• The user asks to add new implementation that must follow existing repository rules and patterns.
• The user asks to bootstrap a new repository or app with ADR-backed source structure and agent guardrails.
• The user asks to review a PR, branch, or diff for architecture drift.
• The user asks where files should live across routes, components, hooks, library modules, server-only modules, shared packages, backend services, env/config, or infrastructure.
• The task touches Next.js App Router structure, Server Components, Hydrated components, TanStack Query read paths, Server Action write paths, or backend runtime composition.
• The task may require a stack-rule deviation or a new durable ADR.

When not to use