agentleFS
on-paron-par/software-factory/CLAUDE.md

software-factory

CLAUDE.md6 starsChanged 2 days agoMITView on GitHub

Read AGENTS.md first. It holds the project rules and the list of repo skills. Before committing, run bash scripts/verify.sh --no-e2e from the repo root and make sure it is green. The verify skill explains each step and how to fix failures. main must always be green. Never bypass a required check that is genuinely FAILURE. The merge-policy skill covers the two narrow exceptions.

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read AGENTS.md first. It holds the project rules and the list of repo skills.

    line 3
  2. Very specific:

    Before committing, run bash scripts/verify.sh --no-e2e from the repo root and make sure it is green.

    line 5

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.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
CLAUDE.md

CLAUDE.md

Read AGENTS.md first. It holds the project rules and the list of repo skills.

Before committing, run bash scripts/verify.sh --no-e2e from the repo root and make sure it is green. The verify skill explains each step and how to fix failures.

main must always be green. Never bypass a required check that is genuinely FAILURE. The merge-policy skill covers the two narrow exceptions.

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.