builderbot / staged
AGENTS.md105 starsChanged 7 months agoApache-2.0View on GitHub
rely on git hooks for commit/push checks; don't run just ci before every commit. run just ci manually only when you want early pre-push feedback. generally don't run the dev server unless asked, usually it is run from a UI integration. We are intentionally conservative with our data models. Before adding fields or new types to the backend, get human review. Generally we want to avoid reconciliation of state, so git is authoritative for anything it tracks. Prefer small, composable…
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 20
Prefer small, composable components over large monolithic ones.
- Very specific: line 26
All components use var(--*) for colors—no hardcoded values.
- Very specific: line 30
Keep src/lib code files smaller and organized by responsibility.
≈ “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
AGENTS.md
Commands
rely on git hooks for commit/push checks; don't run just ci before every commit.
run just ci manually only when you want early pre-push feedback.
generally don't run the dev server unless asked, usually it is run from a UI integration.
Backend
We are intentionally conservative with our data models. Before adding fields or new types to the backend, get human review.
Generally we want to avoid reconciliation of state, so git is authoritative for anything it tracks.
Frontend
Components
Prefer small, composable components over large monolithic ones. Extract repeated UI blocks into focused subcomponents with clear props.
Theming
Colors defined in src/lib/theme.ts, applied via CSS custom properties in app.css.
All components use var(--*) for colors—no hardcoded values.
Rust
Keep src/lib code files smaller and organized by responsibility.
Split growing modules into focused submodules before files become hard to navigate.
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 repository5 other files it gives its agents.
- apps/penpal/CLAUDE.mdCLAUDE.md
- anchorsSkill
- anchor-stabilitySkill
- monitorSkill
- openSkill
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.