agentleFS
vivekschaudharyvivekschaudhary/compass/app/AGENTS.md

compass / app

AGENTS.md2 starsChanged 20 days agoMITView on GitHub

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices. <!-- END:nextjs-agent-rules --> npm install <pkg> on macOS corrupts the lockfile for Linux. sharp (via next) ships per-platform optional variants; npm on darwin/arm64 installs only the darwin one, and an incremental install prunes the transitive deps of the variants it skipped — @img/sharp-wasm32 stays in the lock while its…

  • Deletes or force-pushes
  • Installs packages

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After changing dependencies, run:

    line 17

≈ “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
<!-- BEGIN:nextjs-agent-rules -->

This is NOT the Next.js you know

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.

<!-- END:nextjs-agent-rules -->

Adding a dependency? Rebuild the lockfile, don't just install

npm install <pkg> on macOS corrupts the lockfile for Linux. sharp (via next) ships per-platform optional variants; npm on darwin/arm64 installs only the darwin one, and an incremental install prunes the transitive deps of the variants it skipped — @img/sharp-wasm32 stays in the lock while its @emnapi/* dependencies are dropped.

Nothing local notices. npm ci on a Linux CI runner reads the wasm32 entry, looks for its deps, and refuses the whole install. This has bitten twice.

After changing dependencies, run:

npm run lockfile:rebuild

A resolve with no existing tree to fall back on is what restores the full set. Verify the actual CI condition before pushing — not just that npm install succeeded:

rm -rf node_modules && npm ci

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.