agentleFS
Sign inStart free
1bye1bye/rake/AGENTS.md

rake

AGENTS.md131 starsChanged 5 days agoApache-2.0View on GitHub

For Rust work, read .agents/workflow/rust/AGENTS.md and its task-specific guides. For Rust runtime and target boundaries, read .agents/workflow/rust/stacks.md. Preserve this project's specific instructions and existing tooling. <!-- workflow:end --> After editing, run rake format then rake lint. Use rake lint --fix for machine-safe fixes. Full guide: .agents/skills/rake-gpui/SKILL.md (rake lint --guide). <!-- rake-lint:end -->

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

The file

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

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After editing, run rake format then rake lint.

    line 12
  2. Very specific:

    Use rake lint --fix for machine-safe fixes.

    line 13
  3. Distinctive:

    Always prefer exact class utilities to equivalent pure style closures.

    line 15
  4. Distinctive:

    Never hard-code colors, typography sizes or radii in themed views.

    line 16
  5. Distinctive:

    Never enable debug assertions in release profiles.

    line 17
  6. Distinctive:

    Always give icon-only or dynamic buttons an aria-label, preserving any visible words.

    line 18
  7. Distinctive:

    Always supply img alt text.

    line 19
  8. Distinctive:

    Never derive loop IDs from positions.

    line 20
  9. Distinctive:

    Always explain suppressions.

    line 21

≈ “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
<!-- workflow:begin -->

Rust workflow

For Rust work, read .agents/workflow/rust/AGENTS.md and its task-specific guides. For Rust runtime and target boundaries, read .agents/workflow/rust/stacks.md. Preserve this project's specific instructions and existing tooling.

<!-- workflow:end --><!-- rake-lint:begin -->

Rake agent rules

After editing, run rake format then rake lint. Use rake lint --fix for machine-safe fixes.

  • Always prefer exact class utilities to equivalent pure style closures.
  • Never hard-code colors, typography sizes or radii in themed views; use theme values.
  • Never enable debug assertions in release profiles; use a separate diagnostics profile.
  • Always give icon-only or dynamic buttons an aria-label, preserving any visible words.
  • Always supply img alt text; use alt="" only for decorative images.
  • Never derive loop IDs from positions; use stable data keys.
  • Always explain suppressions; use allow-file only for a whole-file decision.

Full guide: .agents/skills/rake-gpui/SKILL.md (rake lint --guide).

<!-- rake-lint:end -->

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