agentleFS
Sign inStart free
vanillagreencomvanillagreencom/kendex/crates/AGENTS.md

kendex / crates

AGENTS.md76 starsChanged 2 months agoMITView on GitHub

The Rust workspace: core holds the domain, cli and app are thin shells over it, and each has its own AGENTS.md. test_util.rs is the test module every crate's test binaries include by path.

The file

Create a free account to mount
Files
AGENTS.md

crates/

The Rust workspace: core holds the domain, cli and app are thin shells over it, and each has its own AGENTS.md. test_util.rs is the test module every crate's test binaries include by path.

  • A test that runs the kendex binary hands it a fixture home: fixture_env() from test_util.rs, or a HOME with KENDEX_REAL_HOME=1 on the next line. A debug build otherwise runs in the dev sandbox and a release build on the real machine. Two tools/guard lanes check it, per launch in a file naming the binary and per HOME set; cli/tests/dev_sandbox.rs proves the sandbox.

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