Team-Shared Configurations

A team-shared AGENTS.md checked into the repository is the single most impactful configuration you can create. It ensures every team member — and every CI pipeline — gets the same project context, the same rules, and the same commands. Without it, each developer's Codex experience depends on their personal config, which means inconsistent output quality and style drift across the team.

The shared config should contain everything that is objectively true about the project: architecture, build commands, test commands, naming conventions, forbidden patterns, and domain-specific rules. Leave personal preferences (model choice, approval mode, editor integration) out of the shared config — those belong in AGENTS.override.md or the developer's global config.

# Team Standards

## Architecture
- [Project-specific architecture details here]

## Commands
- `npm test` — run all tests (required before commit)
- `npm run lint` — ESLint check (required before commit)
- `npm run typecheck` — TypeScript strict check

## Conventions
- [Team-agreed coding conventions]

## Rules
- [Hard constraints that apply to all team members]

## Agent Notes
- Personal overrides go in AGENTS.override.md (gitignored)
- Model preferences go in your ~/.codex/config.toml
- Do NOT add personal rules to this file — they belong in your override

1. Bootstrap with /init Run `codex /init` to generate a starter AGENTS.md from your codebase. Review and refine the output as a team.
2. Add to PR template Include "AGENTS.md updated?" in your PR checklist so config changes get reviewed alongside code.
3. Document the override pattern Add a section explaining AGENTS.override.md for personal customization. New team members need to know the convention.