agentleFS
afittestideafittestide/asimi/AGENTS.md

asimi

AGENTS.md16 starsChanged 7 days agoMITView on GitHub

Language: Go Write idiomatic Go - Keep it simple, flat, and direct. Edict 1 is reserved for Court Infrastructure operations: - System-level operations (init, bootstrap, project setup) - Infrastructure decisions and precedents This ensures system operations have proper audit trails and prevents edict_id=0 from breaking precedent tracking. Use just <recipe> to manage the project:

  • 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 repository5 other files it gives its agents.

The file

Show its rules and text

We split this AGENTS.md into the rules it gives an agent

17 rules. About 0 are common, 13 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write idiomatic Go: - Keep it simple, flat, and direct.

    line 5
  2. Distinctive:

    Model friendly file structure: Keep file names specific and module names meaningfull

    line 7
  3. Distinctive:

    No wrappers: Avoid unnecessary abstractions

    line 8
  4. Distinctive:

    No build tags: Keep builds simple

    line 9
  5. Distinctive:

    Short, meaningful names: Follow Go conventions

    line 10
  6. Distinctive:

    Inline comments: Only for non-trivial code

    line 11
  7. Distinctive:

    Commit message : start with "fix:", "feat:" or "chore:", follow by short description and end with "e123" for edict 123

    line 12
  8. Distinctive:

    Few testfiles: don't start a new test file if the there's an exisiting file that can host your tests

    line 13
  9. Very specific:

    Use just <recipe> to manage the project:

    line 25
  10. Distinctive:

    default # List all available recipes

    line 32
  11. Distinctive:

    run # Run with debug logging

    line 44
  12. Very specific:

    test # Run the test suite, tee-ing output to ./heaven/tests/test-<datetime>.out

    line 45
  13. Very specific:

    test-atif # ASIMI_PROVIDER) — the test does not force a model.

    line 46
  14. Distinctive:

    test-coverage # Run tests with coverage

    line 47
  15. Distinctive:

    test-intent # Run intent/gherkin BDD scenarios

    line 48
  16. Distinctive:

    test-performance # Run performance benchmarks and guardrail tests

    line 49
  17. Very specific:

    test-race *packages="./court/" # Run tests under the race detector, tee-ing output to ./heaven/tests/test-race-<datetime>.out

    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

Language & Philosophy

Language: Go

Write idiomatic Go - Keep it simple, flat, and direct.

  • Model friendly file structure: Keep file names specific and module names meaningfull
  • No wrappers: Avoid unnecessary abstractions
  • No build tags: Keep builds simple
  • Short, meaningful names: Follow Go conventions
  • Inline comments: Only for non-trivial code
  • **Commit message **: start with "fix:", "feat:" or "chore:", follow by short description and end with "e123" for edict 123
  • Few testfiles: don't start a new test file if the there's an exisiting file that can host your tests

Reserved Edict IDs

Edict 1 is reserved for Court Infrastructure operations:

  • System-level operations (init, bootstrap, project setup)
  • Infrastructure decisions and precedents

This ensures system operations have proper audit trails and prevents edict_id=0 from breaking precedent tracking.

Common Commands

Use just <recipe> to manage the project:

  • bootstrap # Install development tools
  • build # Build the binary
  • build-sandbox # Build the sandbox container.
  • clean # Clean build artifacts
  • clean-sandbox # Clean up the sandbox container
  • default # List all available recipes
  • fmt # Format code
  • freeze-logs # Freeze the log files to ./heaven/logs/asimi[-deamon]-<datetime>.log
  • get-runs # Fetch failed CI runs since the last success, with their entire logs, to heaven/runs.
  • get-threats # Run vulnerability scanning, save output to ./heaven/threats/<tool>-<datetime>.out
  • hello-harbor *args # Recipe: build the latest asimi for linux, then hand it to Harbor
  • init-podman # Init and start the podman machine
  • install # Install dependencies
  • lint # Run linting
  • measure # Measure run_shell_command tool performance
  • nvim # Start neovim with the asimi plugin loaded (interactive dev session)
  • prune-branches # Li 礼), so resolve those by hand.
  • run # Run with debug logging
  • test # Run the test suite, tee-ing output to ./heaven/tests/test-<datetime>.out
  • test-atif # ASIMI_PROVIDER) — the test does not force a model.
  • test-coverage # Run tests with coverage
  • test-intent # Run intent/gherkin BDD scenarios
  • test-performance # Run performance benchmarks and guardrail tests
  • test-race *packages="./court/" # Run tests under the race detector, tee-ing output to ./heaven/tests/test-race-<datetime>.out

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.