CLAUDE.md@templates/project · diff

git:20260402.166ecf0 to git:20260403.c830377

5 added, 4 removed. Audit A to A.

# Claude Repo Routing

Use `.agent/project.yaml` and `.agent/context/*` as the repo-local source of truth generated by Shrey Junior.

Profile: `{{profileName}}`

Execution mode: `{{executionMode}}`

Prefer this lightweight guidance file over invasive repo-local runtime config in v2.

Authority order:

1. existing trusted repo authority files already in the repo

2. promoted canonical docs explicitly referenced by those files

3. generated Shrey Junior overlays

4. `.agent/context/*`

5. fallback templates

Before medium/high complexity work or resuming a prior phase:

1. read the existing repo authority files and any promoted canonical docs they reference

2. read `.agent/state/active-role-hints.json`

3. read `.agent/state/current-phase.json`

4. read the latest task packet, latest handoff, latest reconcile, and latest dispatch manifest when present

5. read the relevant `.github/instructions/*.instructions.md`

6. read relevant `.github/agents/*.md`, `.agent/roles/*.md`, and `.agent/templates/role-result.md`

7. read `.agent/checks.yaml` and `.agent/scripts/verify-contract.sh`

8. read `.agent/project.yaml`

- 9. read `.agent/context/architecture.md`

- 10. read `.agent/context/conventions.md`

- 11. read `.agent/tasks/` packets when present

+ 9. read `.agent/context/commands.md`, `.agent/context/tool-capabilities.md`, and `.agent/context/mcp-capabilities.md`

+ 10. read `.agent/context/architecture.md`

+ 11. read `.agent/context/conventions.md`

+ 12. read `.agent/tasks/` packets when present

Do not rely on machine-local `.claude/*` files as portable authority unless the repo explicitly routes to them.

Cloud-hosted runtimes may not see machine-global files, so treat repo-local artifacts as the portable contract.

Workflow rules:

- trivial work may stay direct when it is local, low-risk, and does not affect contracts, auth, security, release behavior, or multiple files

- use `run` for non-trivial single-owner work that needs repo-aware framing

- use `fanout` for guarded or complex work that benefits from planner / implementer / reviewer / tester separation

- use `dispatch`, `collect`, and `reconcile` when simultaneous small-role work is useful and outputs must be compared explicitly

- require `checkpoint` and `handoff` when Claude is taking over after another tool or handing work back

- consult `push-check` before recommending push on non-trivial or guarded work

- consult `release-check` or `phase-close` when closing a phase or approaching release readiness

- - treat `.agent/state/active-role-hints.json` as the quickest repo-local pointer for current role focus, next file to open, and latest continuity artifacts

+ - treat `.agent/state/active-role-hints.json` as the quickest repo-local pointer for current role focus, next file to open, next command to consider, and latest continuity artifacts

Gate behavior:

- if policy or reconcile state is blocked, treat it as a mandatory gate rather than advisory noise

- if authority files disagree, stop and warn instead of proceeding confidently

- if promoted canonical docs exist, surface them early instead of restarting context from scratch

Specialists and MCP:

- prefer specialist-aware routing when the task clearly maps to frontend, backend, fullstack, python, data-platform, QA, security, docs, refactor, architecture, or push/release work

- MCP usage follows policy, capability, trust, profile, specialist, and approval rules; do not call MCP tools opportunistically