Audit the repository, not just two files.

Search the repository for AGENTS.md, CLAUDE.md, CLAUDE.local.md, tool-specific rule files, and nested copies. Record which directory each file governs.

Write down the order in which each coding agent discovers root, parent, nested, local, and user-level instructions. Do not assume two tools merge files the same way.

Decide which committed file owns cross-tool rules. AGENTS.md is a practical default when several coding agents work in the same repository.

Verify that referenced source folders, architecture documents, fixtures, scripts, and generated directories still exist with the same casing.

Test the documented package-manager and setup commands without relying on an existing node_modules folder or uncommitted local configuration.

Execute the exact lint, typecheck, test, build, and formatting commands named in the instructions. Remove commands that no longer exist.

Flag npm versus pnpm, duplicated flags, obsolete workspace filters, and different test commands across instruction files.

Look for pairs such as always push versus never push, ask first versus proceed automatically, or edit generated files versus never edit them.

Keep a shared rule in one canonical place. Tool overlays should contain only real tool-specific exceptions.

Turn 'write good tests' into an observable expectation: which tests, where they live, and when they must run.

Delete historic explanations that do not change an agent's current decision. Link to durable documentation when background is still useful.

State where secrets may live, what must never be committed, and which production systems require explicit approval.

Use repository permissions, CI, hooks, branch protection, and deployment controls for boundaries that cannot depend on model compliance.

Name operations that require confirmation, including data deletion, schema rollback, force push, broad file rewrites, and production changes.

List the evidence required before handoff: relevant tests, build status, changed behavior, migrations, documentation, and remaining external setup.

Run the same small repository task with every supported coding agent and note which instructions it actually discovers.

Import or reference the shared contract where the tool supports it, then add only the minimum agent-specific behavior.

Name who updates the instructions and require a review when commands, directories, CI, deployment, or supported agents change.