agentleFS
Sign inStart free
kostja94kostja94/bricks/AGENTS.md

bricks

AGENTS.md192 starsChanged 6 days agoMITView on GitHub

  • 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,774 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 repository4 other files it gives its agents.

The file

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

9 rules. About 1 is common, 5 are distinctive, and 3 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Very specific:

    Keep component-builder as the default entry point for constructing new components.

    line 3
  2. Distinctive:

    Create a separate skill only when a topic has an independent workflow, inputs, outputs, or tools.

    line 4
  3. Distinctive:

    Treat visual variants as choices within a component reference, not as separate skills.

    line 6
  4. Distinctive:

    Keep guidance stack-aware and project-adaptive.

    line 7
  5. Distinctive:

    Keep component-builder focused on new construction.

    line 9
  6. Very specific:

    Update catalog/components.json whenever a component reference is added, renamed, or removed.

    line 12
  7. Very specific:

    Run npm test before completing structural changes.

    line 13
  8. Distinctive:

    Keep detailed workflow rules with their owning skill reference.

    line 14
  9. Common:

    Keep public guidance self-contained and generic.

    line 15

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

Repository instructions

  • Keep component-builder as the default entry point for constructing new components.
  • Create a separate skill only when a topic has an independent workflow, inputs, outputs, or tools.
  • Maintain each component concept in one file under references/components/.
  • Treat visual variants as choices within a component reference, not as separate skills.
  • Keep guidance stack-aware and project-adaptive. Do not assume React, Tailwind, or shadcn unless the target project already uses them or the user selects them.
  • Route complete new-page requests to Pagina. Pagina owns generic page-type recommendations; actual project component-to-page relationships belong in the target project component system document.
  • Keep component-builder focused on new construction. Use component-inventory for discovery and its required project document, component-auditor for existing-component analysis and authorized reconstruction, and component-cleanup for verified unused components and migration leftovers.
  • Reuse existing project primitives and tokens; preserve project-specific decisions. Do not treat missing imports alone as permission to delete components.
  • Maintain each target project component system document at its existing location; Bricks stores generic workflows and templates, not client inventories.
  • Update catalog/components.json whenever a component reference is added, renamed, or removed.
  • Run npm test before completing structural changes.
  • Keep detailed workflow rules with their owning skill reference; entry points and indexes summarize and link instead of duplicating full procedures.
  • Keep public guidance self-contained and generic. Exclude client identities, internal URLs, workstation paths, credentials and project-specific design decisions; public repository identity is intentional.

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