sakuralang / assets
AGENTS.md4 starsChanged 24 days agoApache-2.0View on GitHub
This project uses Sakura Lang. Run sakura --version and read sakura prompt before writing source; the guide in that executable matches the compiler. Use the sakura skill when it is installed. Look up unfamiliar APIs with sakura doc or the MCP tool symbol_query before guessing an import. Run sakura check --json, sakura fmt --check and sakura test --json. A successful check may still contain holes (?name); finish them before the final sakura build. Use sakura explain CODE for any diagnostic.
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 32,671 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- compiler/AGENTS.mdAGENTS.md
- website/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/sakura/assets/CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- sakuraSkill
The file
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 8
Run sakura check --json, sakura fmt --check and sakura test --json.
- Very specific: line 19
When the MCP server sakura is connected, confirm that compiler_info.workspace_root is this project before trusting its results.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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
Agent instructions
This project uses Sakura Lang. Run sakura --version and read sakura prompt
before writing source; the guide in that executable matches the compiler. Use
the sakura skill when it is installed. Look up unfamiliar APIs with
sakura doc or the MCP tool symbol_query before guessing an import.
Run sakura check --json, sakura fmt --check and sakura test --json. A
successful check may still contain holes (?name); finish them before the
final sakura build. Use sakura explain CODE for any diagnostic.
For repairs, freeze the agreed signatures, contracts, tests and permissions
against the task's baseline commit (--frozen-specs). Do not weaken a contract
or widen [permissions] or an effect row to make a check pass; report any
interface change. Audit output inventories trust and verify statuses describe
single obligations: neither a clean check nor exit 0 from sakura verify
certifies the whole program.
When the MCP server sakura is connected, confirm that
compiler_info.workspace_root is this project before trusting its results.
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.

