agentleFS
BlockKnown publisherblock/agent-task-queue/examples/claude-code/CLAUDE.md

agent-task-queue / claude-code

CLAUDE.md68 starsChanged 10 months agoApache-2.0View on GitHub

For expensive build commands, ALWAYS use the run_task MCP tool instead of Bash. **Commands that MUST use run_task:** - gradle, bazel, make, cmake, mvn, cargo build, go build - docker build, docker-compose, kubectl, helm - npm/yarn/pnpm build, pytest, jest, mocha Usage: - command: The full shell command - working_directory: Absolute path to project root - env_vars: Optional like "KEY=value,KEY2=value2" NEVER run these via Bash. Always use run_task MCP tool.

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:

    NEVER run these via Bash. Always use run_task MCP tool.

    line 15

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

Build Queue

For expensive build commands, ALWAYS use the run_task MCP tool instead of Bash.

Commands that MUST use run_task:

  • gradle, bazel, make, cmake, mvn, cargo build, go build
  • docker build, docker-compose, kubectl, helm
  • npm/yarn/pnpm build, pytest, jest, mocha

Usage:

  • command: The full shell command
  • working_directory: Absolute path to project root
  • env_vars: Optional like "KEY=value,KEY2=value2"

NEVER run these via Bash. Always use run_task MCP tool.

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.