amplifier-constellation-instance
AGENTS.md0 starsChanged yesterdayMITView on GitHub
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read the vision, then select the relevant boundary from the contract map. Shared promises and collaboration practice live in the Constellation umbrella; apply them without copying a second methodology or family contract here. Inspect current source, configuration and meaningful checks for the next outcome. Preserve exact protocol definitions in their existing homes. Guides and the bundled administration client add no…
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 31,439 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.
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Read the vision, then select the relevant boundary from the contract map.
- Distinctive: line 13
Keep release history, private deployment evidence and a maintained gap inventory out of the normal onboarding path.
- Distinctive: line 16
Use validation for checks appropriate to the change.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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
Working on Instance
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it.
Read the vision, then select the relevant boundary from the contract map. Shared promises and collaboration practice live in the Constellation umbrella; apply them without copying a second methodology or family contract here.
Inspect current source, configuration and meaningful checks for the next outcome. Preserve exact protocol definitions in their existing homes. Guides and the bundled administration client add no separate promises about future products. Keep release history, private deployment evidence and a maintained gap inventory out of the normal onboarding path.
Use validation for checks appropriate to the change. Check both producer and consumer when their shared behavior changes. Documentation changes need link and meaning review; no live operations follow from a documentation assignment.
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.