intelig-agent-playbook AGENTS.md

Customer Platform — Agent Context

This is the canonical context file. Every agent reads it (Claude Code reads it via the @AGENTS.md line in CLAUDE.md; Codex, Cursor, Copilot, Gemini CLI, Aider and others read AGENTS.md natively). Keep it lean — it loads on every turn. Put detail in the files it links to, not here.

What you are working on

Fork note — replace this block with your product. One or two sentences: what the system is, the bounded context this repo owns, and its core lifecycle/invariants. Keep it tight; it loads on every turn. Pattern: "A <kind of system>. This codebase is its <Context> context: <what it does>, moving them through <STATE → STATE → STATE>. Small surface, real invariants."

Example used throughout this repo: a B2B SaaS backend whose Customer context registers a customer (a company + a primary contact) and moves it through PENDING → ACTIVE → SUSPENDED — a teaching example for building cleanly with an agent.

Prime directives

1. Spec before code. Work is organized by domain: each bounded context lives in product/domains/<domain>/ (its README.md is the durable description), and keeps its spec-first work-items in product/domains/<domain>/work-items/<work-item>/ (requirements → design → tasks → acceptance). Read the spec; implement one task at a time; stop at the acceptance gate. Don't invent scope the spec doesn't ask for.
2. Standards are law. Before writing code in an area, read the matching family in standards/ (start at standards/STANDARDS_INDEX.md → it tells you which families apply). Cite the rule ID where it clarifies intent (commit, PR, or a brief code comment, e.g. // DOM-002: factory method, no public constructor). Rule IDs read <FAMILY>-<NNN> — families are ARCH DOM CQRS API ES DB TS, each listed in standards/STANDARDS_DIGEST.md (so DOM-002 = the 2nd rule in the domain-model family).
3. Advisory vs enforced. Rules here are advisory. The mandatory ones are enforced by fitness-function tests (see standards/architecture.rules.md → Enforcement Map). If a test would stop you, the rule is not optional. If you keep wanting to break a rule, that's a signal to change the test, not to sneak past it.
4. Tag work to strategy. Active initiatives are in product/initiatives.md (the session hook prints them for you). Reference the initiative ID in the commit subject so code links back to why it exists.