agentleFS
Sign inStart free
boxlite-aiboxlite-ai/boxlite/make/AGENTS.md

boxlite / make

AGENTS.md2.6k starsChanged 34 days agoApache-2.0View on GitHub

- Prefer existing targets and options, e.g. make test:unit:vmm FILTER='test_name'. Add only reusable workflows to the appropriate .mk; no targets for individual tests or PRs. - Keep recipes to tool/script calls; put complex shell logic in scripts/. Follow runtime in build.mk. Preserve setup prerequisites. - Start recipe lines with a tab. Separate targets with a blank line. - Use lowercase target names and the existing colon hierarchy; escape colons in definitions, e.g. test\:unit\:vmm:. Use UPPER_SNAKE_CASE Make variables. - Use :=…

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 3 mentionsFeb 2026: 5 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 4 mentionsOct 2026: 31 mentionsNov 2026: 12 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the boxlite-ai/boxlite repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about boxlite-ai/boxlite

The biggest 5 of 56 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 56

Talked about on GitHub, Hacker News and Bluesky (56 times).

On GitHub · 50

45 more on GitHub
  • Other versions1 project uses a version of this.

    Word for word · 1

    1. boxlite-labs/boxlite★ 2.6k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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,439 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

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

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

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

    Prefer existing targets and options, e.g.

    line 5
  2. Very specific:

    Keep recipes to tool/script calls.

    line 8
  3. Very specific:

    Follow runtime in build.mk.

    line 9
  4. Distinctive:

    Start recipe lines with a tab.

    line 13
  5. Very specific:

    Use lowercase target names and the existing colon hierarchy.

    line 14
  6. Very specific:

    Use := for immediate values, ?= for overridable defaults, += to append, and = when expansion must be deferred.

    line 16
  7. Very specific:

    Use $(NAME) for Make variables and $$name for shell variables in recipes.

    line 18
  8. Very specific:

    Use && between dependent commands and \ continuations for shared shell state.

    line 19
  9. Very specific:

    Use $(MAKE) for recursive calls.

    line 20
  10. Distinctive:

    Update help.mk when public commands change.

    line 25
  11. Very specific:

    After recipe changes, run make help and the affected target.

    line 26

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

Make guidance

Target design

  • Prefer existing targets and options, e.g. make test:unit:vmm FILTER='test_name'. Add only reusable workflows to the appropriate .mk; no targets for individual tests or PRs.
  • Keep recipes to tool/script calls; put complex shell logic in scripts/. Follow runtime in build.mk. Preserve setup prerequisites.

Style

  • Start recipe lines with a tab. Separate targets with a blank line.
  • Use lowercase target names and the existing colon hierarchy; escape colons in definitions, e.g. test\:unit\:vmm:. Use UPPER_SNAKE_CASE Make variables.
  • Use := for immediate values, ?= for overridable defaults, += to append, and = when expansion must be deferred. Preserve existing expansion timing.
  • Use $(NAME) for Make variables and $$name for shell variables in recipes. Use && between dependent commands and \ continuations for shared shell state.
  • Use $(MAKE) for recursive calls. Preserve the root Makefile's macOS Make 3.81 compatibility and .PHONY/.DEFAULT handling.

Verification

  • Update help.mk when public commands change.
  • After recipe changes, run make help and the affected target.

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