No more starting from zero. AAMS is a declarative standard that gives AI agents a workspace, a memory, and a set of rules — across every tool, every session, every repo.
You clone a repo. Your agent starts fresh. It has no context, no memory, no agreed-upon structure. Every session it reinvents the wheel. Every tool (Copilot, Cursor, Claude, Codex) needs the same explanation again.
AAMS fixes this with a single file.
.agent.json at repo root. Every agent reads it. Every tool reads it.WORKING/ folder with session logs, memory, and whitepapers. Built automatically.Drop .agent.json into any repo. Your agent does the rest.
curl -sO https://raw.githubusercontent.com/DEVmatrose/AAMS/main/.agent.json
Hand the file to your agent and tell it to bootstrap. That's it.
AAMS is not a plugin. It's a file convention. Every tool that reads files picks it up automatically.
One file. Switch tools tomorrow. Your workspace stays.
This project — the project that describes the standard — used AAMS to build itself. Not a demo, not a tutorial. The actual repo.
What that looked like:
Read .agent.json → created WORKING/ → wrote the first workpaper →
built the spec → ran two external reviews → fixed every identified issue →
ingested 46 LTM entries and 114 chunks into ChromaDB → shipped this page.
Everything is documented in WORKING/WORKPAPER/closed/.
This is not proof of scale. It's proof that the workflow holds for at least one real project — the one you're reading about right now.
One file. That's all you need.
curl -sO https://raw.githubusercontent.com/DEVmatrose/AAMS/main/.agent.json
Drop .agent.json into your repo root. Hand it to your agent with the bootstrap prompt from prompts/bootstrap.md. Done.
Going deeper or building a framework?
https://github.com/DEVmatrose/AAMS