AE-CTX-001 is a Blocker. While it is active, the final Charter score is held at ≤59 — the repo cannot reach a passing score until a context file exists.
Why this rule
Agents operate from what they can read in the repo. A missing or empty context file means the agent starts every session with no orientation — it guesses at the stack, invents build commands, and may edit files it should leave alone. A context file that exceeds the token budget gets truncated, so the agent receives an arbitrary prefix and silently loses the constraints that fell past the cutoff.What triggers it
Charter looks for any of the following files in the repo root:AGENTS.md, CLAUDE.md, .cursor/rules, .windsurfrules, .github/copilot-instructions.md, opencode.md, codex.md, DESIGN.md, SKILL.md.
The finding fires when:
- No recognized context file exists
- The file is empty or contains only placeholder text (e.g. “Add your project details here”)
- The file exceeds the 600-token budget that agent context windows reliably fit
Examples
- Failing
- Passing
AGENTS.md (placeholder)
AGENTS.md (over budget)
How to fix
1
Preview the scaffolded file
Run
charter fix with --rule AE-CTX-001 --dry-run to see what Charter will create before writing anything.2
Create the context file
Run
charter fix --rule AE-CTX-001 to scaffold a minimal AGENTS.md at the repo root.3
Reflect your actual project
Edit the file to include your real stack, verification command, edit boundaries, and any hard constraints. Generic scaffolding still satisfies the rule syntactically but gives agents nothing useful.
4
Stay within budget
Aim for under 400 tokens. The value of a context file degrades when it grows past the 600-token budget — trim ruthlessly and link to longer docs rather than inlining them.
Score impact
Blocker (−20 per finding). This finding engages the Blocker cap — the final score is held at ≤59 while it is active. Caps are reserved for raw-secret and Blocker findings.Edge cases
A repo usingCLAUDE.md, DESIGN.md, or SKILL.md instead of AGENTS.md passes if the file satisfies the same content requirements. Charter accepts any recognized filename — the check is on content and budget, not the specific filename.
Related rules
AE-CTX-002
Context file must stay consistent with the actual repo state.
AE-CTX-004
Agent session artifacts must be gitignored.
AE-CTX-006
Emphatic directive density degrades adherence.
AE-CC-002
Edit scope must be declared explicitly.