agentleFS
deanmikandeanmikan/ai-native-company-starter/company/AGENTS.md

ai-native-company-starter / company

AGENTS.md0 starsChanged 2 months agoMITView on GitHub

Durable foundations: mission, strategy, goals, principles, glossary. These pages change rarely and carry the most authority in the workspace. - Read README.md here, then only the page you need. - Never edit an approved page directly. Draft the change on a branch, keep status unchanged, and name the change in the pull request; the owner approves and sets reviewed_by. - Most changes here originate from a decision. Record it with record-decision and link it from the page you change. -…

The file

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

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read README.md here, then only the page you need.

    line 6
  2. Very specific:

    Never edit an approved page directly.

    line 7
  3. Distinctive:

    Keep the founder's wording.

    line 12

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

company/ rules

Durable foundations: mission, strategy, goals, principles, glossary. These pages change rarely and carry the most authority in the workspace.

  • Read README.md here, then only the page you need.
  • Never edit an approved page directly. Draft the change on a branch, keep status unchanged, and name the change in the pull request; the owner approves and sets reviewed_by.
  • Most changes here originate from a decision. Record it with record-decision and link it from the page you change.
  • Keep the founder's wording. Compress; do not embellish or add claims.
  • principles.md may stay a draft standard until the founder has real tradeoff rules. Do not invent principles.
  • Nothing about a specific customer, employee, or vendor belongs here.

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.