canlicapital
AGENTS.md6 starsChanged 43 days agoMITView on GitHub
Before starting a new phase, making a release decision, or continuing after chat compaction, read docs/goal/README.md, docs/goal/REQUIREMENTS.md, and docs/goal/STATUS.md. Then read the relevant entries in docs/goal/PHASES.md and docs/goal/LOG.md. These are the user's requested continuity records. Update STATUS and LOG at each material transition: phase start, completed change, validation result, blocker, scope correction, deployment, or handoff. Link actual artifacts/commands/commits. Label plans, local work, deployed changes and measured outcomes separately. A record is not evidence that an action happened: verify the underlying…
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Before starting a new phase, making a release decision, or continuing after chat compaction, read docs/goal/README.md, …
- Very specific: line 8
Update STATUS and LOG at each material transition: phase start, completed change, validation result, blocker, scope correction, deployment, …
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CanliCapital ongoing goal
Before starting a new phase, making a release decision, or continuing after chat
compaction, read docs/goal/README.md, docs/goal/REQUIREMENTS.md, and
docs/goal/STATUS.md. Then read the relevant entries in docs/goal/PHASES.md
and docs/goal/LOG.md. These are the user's requested continuity records.
Update STATUS and LOG at each material transition: phase start, completed change, validation result, blocker, scope correction, deployment, or handoff. Link actual artifacts/commands/commits. Label plans, local work, deployed changes and measured outcomes separately. A record is not evidence that an action happened: verify the underlying artifacts before repeating a claim. Never erase failed results to make a phase appear complete. New user instructions take precedence; record them.
Preserve all active objectives in REQUIREMENTS. Do not substitute sitemap capacity or local page counts for actual indexing, or backtest metrics for forward evidence.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository2 other files it gives its agents.
- public/llms-full.txtllms.txt
- public/llms.txtllms.txt
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.