agentleFS
hashiiiiihashiiiii/rules-for-ai/AGENTS.md

rules-for-ai

AGENTS.md10 starsChanged 3 months agoMITView on GitHub

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
  1. Distinctive:

    Do not optimize too early

    line 3
  2. Distinctive:

    If a task causes difficulty, do it more frequently

    line 4
  3. Distinctive:

    Never assume intentions that the user did not state

    line 7
  4. Distinctive:

    Do not use emoji

    line 9
  5. Distinctive:

    Write comments that explain the reason

    line 11
  6. Distinctive:

    Do not write comments that only explain the action

    line 12
  7. Distinctive:

    Never use mocks or stubs

    line 13
  8. Distinctive:

    If the context contains resolved locale keys, use them

    line 18
  9. Distinctive:

    If the context does not contain resolved locale keys, read the first existing locale file in this order:

    line 19
  10. Very specific:

    If no locale file exists, use en_US for all keys

    line 29
  11. Very specific:

    Before you write, edit, or review English prose, always read and apply the hashiiiii-write-en skill.

    line 33
  12. Very specific:

    Before you write, edit, or review Japanese prose, always read and apply the hashiiiii-write-ja skill.

    line 34
  13. Very specific:

    Use the hashiiiii-git skill for Git operations

    line 38
  14. Very specific:

    Use the hashiiiii-issues skill for GitHub issue operations

    line 42
  15. Very specific:

    Use the hashiiiii-pull-request skill for GitHub pull request operations

    line 46
  16. Very specific:

    Use the hashiiiii-images skill to create image assets (logos, icons, favicons, and header images)

    line 50

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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:
    1. <absolute-git-dir>/rules-for-ai/LOCALE.md
    2. <repo>/.rules-for-ai/LOCALE.md
    3. ~/.config/rules-for-ai/LOCALE.md
    4. Bundled LOCALE.default.md in 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> with git rev-parse --absolute-git-dir
  • If no locale file exists, use en_US for all keys

Writing

  • Before you write, edit, or review English prose, always read and apply the hashiiiii-write-en skill.
  • Before you write, edit, or review Japanese prose, always read and apply the hashiiiii-write-ja skill.

Git

  • Use the hashiiiii-git skill for Git operations

Issues

  • Use the hashiiiii-issues skill for GitHub issue operations

Pull Requests

  • Use the hashiiiii-pull-request skill for GitHub pull request operations

Images

  • Use the hashiiiii-images skill to create image assets (logos, icons, favicons, and header images)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.