evergonlabsevergonlabs/aiframework/AGENTS.md

aiframework

AGENTS.md0 starsChanged 7 months agoMITView on GitHub

Make Claude Code understand your project instantly. Single Rust binary, zero deps. Stack: Rust Build: cd rust && cargo build --release Test: cd rust && cargo test Lint: cd rust && cargo clippy

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,700 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 repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- aif-analyzeSkill
- aif-enhanceSkill
- aif-evolveSkill
- aif-feedbackSkill
- aif-ingestSkill
- aif-learnSkill
- aif-pulseSkill
- aiframework-learnSkill
- aiframework-reviewSkill
- aiframework-shipSkill
- aif-readySkill
- aif-researchSkill
- aif-reviewSkill
- aif-shipSkill
- aif-statusSkill
- retroSkill
- sheal-askSkill
- sheal-checkSkill
- sheal-driftSkill
- sheal-retroSkill

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
All output is JSON (serde_json)
line 31

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

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

Files

AGENTS.md

AGENTS.md — aiframework

Make Claude Code understand your project instantly. Single Rust binary, zero deps.

Stack: Rust Build: cd rust && cargo build --release Test: cd rust && cargo test Lint: cd rust && cargo clippy

Commands

aiframework run --target .        # Full pipeline
aiframework index --target .      # Code index only
aiframework verify --target .     # Validate outputs
aiframework refresh               # Re-scan if changed

Key Files

rust/src/cli.rs — CLI (clap)
rust/src/scanner/ — 13 scanners
rust/src/indexer/ — code indexer + 13 parsers (8 tree-sitter)
rust/src/generator/ — 14 generators
rust/src/validator/ — 5 validators
rust/src/mcp/ — MCP JSON-RPC server
rust/data/languages.json — language registry

Conventions

All output is JSON (serde_json)
Tree-sitter AST parsing with regex fallback
Generators never overwrite user content
Tier system: lean < standard < full < enterprise

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.

Check your setup, free