agentleFS
VincenzoImpVincenzoImp/openings/AGENTS.md

openings

AGENTS.md7 starsChanged 3 days agoMITView on GitHub

Read README.md, CONTRIBUTING.md and docs/developer/architecture.md before changing behavior. The running OpenAPI schema and MCP tools/list are the contract. - Keep business logic in shared services. Every dashboard action is a REST operation; every operation that is not owner-only is an MCP tool or names the MCP tool that does its work (mcp=). REST is the superset; keep tools/list within its budget (test_mcp_budget.py). - Preserve version checks, document immutability, exact file ownership, reversible dismissal and deliberate permanent deletion. - Keep incomplete…

  • 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 33,315 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 repository8 other files it gives its agents.

The file

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

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Read README.md, CONTRIBUTING.md and docs/developer/architecture.md before changing behavior.

    line 3
  2. Very specific:

    Keep business logic in shared services.

    line 6
  3. Distinctive:

    Keep incomplete automatic candidates in collection checkpoints.

    line 12
  4. Distinctive:

    Keep SQLite portable and the core independent of model, browser and TeX runtimes.

    line 16
  5. Very specific:

    Use focused invariant tests and practical complete workflows after meaningful changes.

    line 22
  6. Distinctive:

    Prefer small, clear services and coherent commits.

    line 25
  7. Distinctive:

    Do not merge, publish artifacts or deploy an installation unless the current task explicitly authorizes that action.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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

Working on Openings

Read README.md, CONTRIBUTING.md and docs/developer/architecture.md before changing behavior. The running OpenAPI schema and MCP tools/list are the contract.

  • Keep business logic in shared services. Every dashboard action is a REST operation; every operation that is not owner-only is an MCP tool or names the MCP tool that does its work (mcp=). REST is the superset; keep tools/list within its budget (test_mcp_budget.py).
  • Preserve version checks, document immutability, exact file ownership, reversible dismissal and deliberate permanent deletion.
  • Keep incomplete automatic candidates in collection checkpoints; admit usable posting text before archive and count bookkeeping. Preserve manual partial input.
  • Enforce one non-Closed application per job in shared services and SQLite. Starting an application shortlists its job; document work never submits it.
  • Keep SQLite portable and the core independent of model, browser and TeX runtimes. Generation and compilation belong to an external agent.
  • Provider requests must use the shared persisted gate, including previews, redirects and manual runs. Never bypass it with an unguarded HTTP client.
  • Ship English code/UI/docs and synthetic public fixtures. Keep databases, credentials, personal documents and machine-specific deployment files out of Git.
  • Use focused invariant tests and practical complete workflows after meaningful changes. Attach the screenshots project's images of every changed screen to the PR (npm --prefix frontend run screenshots).
  • Prefer small, clear services and coherent commits. Parallel work should use isolated worktrees and explicit file ownership; remove temporary work afterward.

Do not merge, publish artifacts or deploy an installation unless the current task explicitly authorizes that action. Keep release-specific work notes outside the public product tree.

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.