rules-for-ai
AGENTS.md10 starsChanged 3 months agoMITView on GitHub
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 repository11 other files it gives its agents.
- hallmarkSkill
- hashiiiii-explain-prSkill
- hashiiiii-gitSkill
- hashiiiii-imagesSkill
- hashiiiii-issuesSkill
- hashiiiii-localeSkill
- hashiiiii-pull-requestSkill
- hashiiiii-write-enSkill
- hashiiiii-write-jaSkill
- hashiiiii-zigSkill
- show-meSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
16 rules. About 0 are common, 9 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Do not optimize too early
- Distinctive: line 4
If a task causes difficulty, do it more frequently
- Distinctive: line 7
Never assume intentions that the user did not state
- Distinctive: line 9
Do not use emoji
- Distinctive: line 11
Write comments that explain the reason
- Distinctive: line 12
Do not write comments that only explain the action
- Distinctive: line 13
Never use mocks or stubs
- Distinctive: line 18
If the context contains resolved locale keys, use them
- Distinctive: line 19
If the context does not contain resolved locale keys, read the first existing locale file in this order:
- Very specific: line 29
If no locale file exists, use en_US for all keys
- Very specific: line 33
Before you write, edit, or review English prose, always read and apply the hashiiiii-write-en skill.
- Very specific: line 34
Before you write, edit, or review Japanese prose, always read and apply the hashiiiii-write-ja skill.
- Very specific: line 38
Use the hashiiiii-git skill for Git operations
- Very specific: line 42
Use the hashiiiii-issues skill for GitHub issue operations
- Very specific: line 46
Use the hashiiiii-pull-request skill for GitHub pull request operations
- Very specific: line 50
Use the hashiiiii-images skill to create image assets (logos, icons, favicons, and header images)
≈ “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
AGENTS
- Do not optimize too early
- If a task causes difficulty, do it more frequently
- Correct small defects before they become larger defects
- Never compromise
- Never assume intentions that the user did not state
- Insert a half-width space between full-width and half-width characters
- Do not use emoji
- Prioritize comments in tests
- Write comments that explain the reason
- Do not write comments that only explain the action
- Never use mocks or stubs
Language
- Project instructions (
CLAUDE.md/AGENTS.md) take precedence over resolved locale keys - If the context contains resolved locale keys, use them
- If the context does not contain resolved locale keys, read the first existing locale file in this order:
<absolute-git-dir>/rules-for-ai/LOCALE.md<repo>/.rules-for-ai/LOCALE.md~/.config/rules-for-ai/LOCALE.md- Bundled
LOCALE.default.mdin one of these locations:$CODEX_HOME/rules-for-ai/for Codex user installations<repo>/.agents/rules-for-ai/for Codex project and local installations<repo>/.cursor/rules-for-ai/for Cursor project and local installations- The plugin root for other installations
- Get
<absolute-git-dir>withgit rev-parse --absolute-git-dir - If no locale file exists, use
en_USfor all keys
Writing
- Before you write, edit, or review English prose, always read and apply the
hashiiiii-write-enskill. - Before you write, edit, or review Japanese prose, always read and apply the
hashiiiii-write-jaskill.
Git
- Use the
hashiiiii-gitskill for Git operations
Issues
- Use the
hashiiiii-issuesskill for GitHub issue operations
Pull Requests
- Use the
hashiiiii-pull-requestskill for GitHub pull request operations
Images
- Use the
hashiiiii-imagesskill to create image assets (logos, icons, favicons, and header images)
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.

