devctl
AGENTS.md2 starsChanged 51 days agoMITView on GitHub
When asked to onboard this repository to devctl, or to add or fix .devctl/config.yaml (including the demo under examples/demo-platform/.devctl/), follow skills/devctl-onboard/SKILL.md and its references/ files. Validate with devctl config validate before reporting done. Do not author .devctl YAML from the JSON Schema alone — skills/devctl-onboard/references/authoring.md carries the rules the loader rejects on and the schema does not state. When asked to debug a service this devctl is already running — a crash, a health failure, a bad response, a missing…
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,700 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 repository6 other files it gives its agents.
- app/CLAUDE.mdCLAUDE.md
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/devctl-debug.mdcCursor rule
- .cursor/rules/devctl-onboard.mdcCursor rule
- devctl-debugSkill
- devctl-onboardSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
When asked to onboard this repository to devctl, or to add or fix .devctl/config.yaml (including the demo under …
- Very specific: line 5
Do not author .devctl YAML from the JSON Schema alone — skills/devctl-onboard/references/authoring.md carries the rules the loader rejects …
- Very specific: line 7
When asked to debug a service this devctl is already running — a crash, a health failure, a bad response, a missing environment value — …
≈ “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
Agents
When asked to onboard this repository to devctl, or to add or fix .devctl/config.yaml (including the demo under examples/demo-platform/.devctl/), follow skills/devctl-onboard/SKILL.md and its references/ files. Validate with devctl config validate before reporting done.
Do not author .devctl YAML from the JSON Schema alone — skills/devctl-onboard/references/authoring.md carries the rules the loader rejects on and the schema does not state.
When asked to debug a service this devctl is already running — a crash, a health failure, a bad response, a missing environment value — follow skills/devctl-debug/SKILL.md. That skill reads status, logs, print-env, and proxy traffic. It does not rewrite .devctl YAML.
Contributing to this application itself: CONTRIBUTING.md, docs/internals/README.md, docs/typescript.md, and docs/architecture.md. Follow the hexagonal layering rules in .cursor/rules/architecture.mdc. Run cd app && bun run check:architecture after structural changes. After adding or removing modules, also run bun run check:dead and bun run check:dup.
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.