agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/amplifier-constellation/AGENTS.md

amplifier-constellation

AGENTS.md1 starsChanged yesterdayMITView on GitHub

This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Use Amplifier Converge as the collaboration method. Read docs/VISION.md and the contracts for the next outcome. Derive the gap by inspecting current source, capabilities and relevant behavior; do not maintain a parallel umbrella status or gap inventory. docs/working-together.md explains the local practice. Do not load every contract or historical conversation by default. - Use family.toml to find the Microsoft component…

  • 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.

The file

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

4 rules. About 1 is common, 1 is distinctive, and 2 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Use Amplifier Converge as the collaboration method.

    line 5
  2. Very specific:

    Use family.toml to find the Microsoft component that owns a behavior.

    line 12
  3. Distinctive:

    Keep current direction concise.

    line 28
  4. Common:

    Keep credentials, personal profiles, transcripts, deployment details and private experiments outside this publication checkout.

    line 31

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

Working in the Constellation umbrella

This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it.

Use Amplifier Converge as the collaboration method. Read docs/VISION.md and the contracts for the next outcome. Derive the gap by inspecting current source, capabilities and relevant behavior; do not maintain a parallel umbrella status or gap inventory. docs/working-together.md explains the local practice. Do not load every contract or historical conversation by default.

  • Use family.toml to find the Microsoft component that owns a behavior. This repository owns shared direction and composition, not every implementation.
  • Inspect current source and relevant evidence. Distinguish intended behavior, accepted commitments, implementation and verified outcomes. A draft does not silently replace an agreement.
  • Make ordinary decisions within delegated authority. Prepare a concrete choice when a shared promise or reserved decision must change; continue unaffected work. Do not add routine approval gates.
  • Give shared promises one home. Keep detailed schemas, protocol behavior and tests with their serving component; link them here. Guides and diagrams explain those promises and do not create a second API specification. Removing a guide must not remove a commitment. When changing a promise, review its linked examples in the same change; do not create a separate synchronization ledger.
  • Name an outcome owner, affected connections and a meaningful combined check in the existing work record. Carry changed direction into active work; a document edit alone is not completion.
  • Keep current direction concise. Do not append running release histories or summaries of gaps that future contributors must maintain. Link evidence only when it supports a current claim or decision.
  • Keep credentials, personal profiles, transcripts, deployment details and private experiments outside this publication checkout.
  • For documentation changes, inspect the full changed passages, check links and visuals, and walk through a newcomer and a changed-boundary scenario. A prose walkthrough is not proof of deployed behavior.

Existing repository permissions and assignment authority still govern publication and operations. This file grants neither access to installations nor authority to change another owner's commitments.

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