agentleFS
Sign inStart free
JaxsonmanJaxsonman/Crucible/CLAUDE.md

Crucible

CLAUDE.md0 starsChanged 36 days agoMITView on GitHub

- Shared decisions live in docs/design.md; update it when a change alters one. See CONTRIBUTING.md for the pull request process. - Commands: - uv sync - uv run pytest - uv run ruff check . - uv run crucible --help - Work test-first: write a failing test, then the code. Tests must use the temp CRUCIBLE_HOME fixture (autouse in tests/conftest.py) and never write into the real tasks/, results/ or .crucible/. Tests never call the real claude or gh; use tests/fake_claude.py…

The file

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

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep secrets, personal paths and private repository details out of tasks, results and docs.

    line 14

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

Crucible: contributor and agent instructions

  • Shared decisions live in docs/design.md; update it when a change alters one. See CONTRIBUTING.md for the pull request process.
  • Commands:
    • uv sync
    • uv run pytest
    • uv run ruff check .
    • uv run crucible --help
  • Work test-first: write a failing test, then the code. Tests must use the temp CRUCIBLE_HOME fixture (autouse in tests/conftest.py) and never write into the real tasks/, results/ or .crucible/. Tests never call the real claude or gh; use tests/fake_claude.py and tests/fake_gh.py.
  • Keep secrets, personal paths and private repository details out of tasks, results and docs.

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