AGENTS.md, project.json, and rules: the smallest APC boundary that works APC stays useful...
AGENTS.md, project.json, and rules: the smallest APC boundary that works
APC stays useful only if its layers stay small and distinct. The mistake is to turn one file into a catch-all for every kind of project knowledge. That feels simpler on day one, then turns into drift, duplication, and tool-specific clutter.
The better split is narrow:
AGENTS.md for the repo-wide contract
.apc/project.json for stable project metadata
Stop hand-maintaining a separate instructions file for Claude, Cursor, Codex, Gemini, Copilot and Aider. @mongez/agent-kit…
Every AI coding agent wants project context. Claude Code, Codex, Cursor, OpenCode, Windsurf, and...
A rules file starts as one page. Six months later it is fourteen pages and nobody can remember what...
A valid AGENTS.md is not a compliant agent. A real muster run: a live model breaks a rule the file got right, a bigger model only…
The instruction file that runs my codebase started as a junk drawer. The rules that ended up...
This is the first part of a series about why even the most powerful AI agents today need more than...
