bloom
AGENTS.md46 starsChanged 48 days agoMITView on GitHub
Read CLAUDE.md for the shared architecture, coding, testing and app isolation rules. Those rules apply to every agent, including Codex. Read the matching SKILL.md before building an installed dev app, releasing, or doing the Swift work described below. Load supporting references only when relevant to the task. The maintained files live in .claude/skills/. Each entry under .agents/skills/ is a relative symlink to the same folder, so Claude and Codex use identical instructions. Add a matching symlink when adding a skill;…
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.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bloom-dev-buildSkill
- bloom-releaseSkill
- swift-concurrency-proSkill
- swift-testing-proSkill
- swiftui-proSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Read CLAUDE.md for the shared architecture, coding, testing and app isolation rules.
- Very specific: line 8
Read the matching SKILL.md before building an installed dev app, releasing, or doing the Swift work described below.
≈ “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 Bloom
Read CLAUDE.md for the shared architecture, coding, testing and app isolation rules. Those rules apply to every agent, including Codex.
Project skills
Read the matching SKILL.md before building an installed dev app, releasing, or doing the Swift
work described below. Load supporting references only when relevant to the task.
| Skill | Use for |
| bloom-dev-build | Build and install the isolated Bloom Dev app from a committed revision. |
| bloom-release | Publish a release, generate and publish notes on GitHub and runbloom.app, or package signed local artefacts. |
| swiftui-pro | Write or review Bloom's macOS SwiftUI views. |
| swift-concurrency-pro | Write or review async code, actor isolation, cancellation and streams. |
| swift-testing-pro | Write or review Swift Testing tests in BloomCoreTests. |
The maintained files live in .claude/skills/. Each entry under .agents/skills/ is a relative
symlink to the same folder, so Claude and Codex use identical instructions. Add a matching symlink
when adding a skill; keep references relative and commands relative to the repository root.
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.