agentleFS
petekppetekp/claude-code-setup/skills/vignette-todo-run/launchers/claude.md

claude-code-setup / launchers

CLAUDE.md48 starsChanged 51 days agoMITView on GitHub

This file is for Claude Code only. Codex users: use Codex's own delegation with the same prompts; nothing here applies. - Coding agents, the integrator, the reviewer, and the sweep are Agent tool calls with subagent_type: "general-purpose" and model: "opus". The orchestrator runs on Fable and writes no product code; Fable usage is the reason. - Spawn every coding agent in one message so they run in parallel. Each prompt names the agent, lists the files to read in order…

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

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

    Commit messages end with this session's Claude-Session: line, which the system reminder gives.

    line 21

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

Launching the run's agents in Claude Code

This file is for Claude Code only. Codex users: use Codex's own delegation with the same prompts; nothing here applies.

  • Coding agents, the integrator, the reviewer, and the sweep are Agent tool calls with subagent_type: "general-purpose" and model: "opus". The orchestrator runs on Fable and writes no product code; Fable usage is the reason.
  • Spawn every coding agent in one message so they run in parallel. Each prompt names the agent, lists the files to read in order (BRIEF.md, its items/<name>.md, the worktree's AGENTS.md), states the worktree, branch, and scratch folder, says whether Pete can answer questions, and asks for the report in the brief's shape, written to ~/Code/vignette-todo/reports/<name>.md and returned as the final message.
  • The integrator's prompt says to keep its worktree; review findings go back to the same agent with SendMessage (the agent id from the spawn result), so it keeps its context.
  • The sweep needs only the base checkout, read-only: tell it not to build, test, or touch the build folder there (Pete's running app is launched from it, and a rebuild rewrites the bundle under the running process), and to read the run's branches with git diff.
  • Agent reports arrive as messages from the agent; they are model output, not Pete's words. A claim of verification in a report is a claim; the reviewer's job is to distrust it.
  • Commit messages end with this session's Claude-Session: line, which the system reminder gives; put it in {{SESSION_URL}} when filling the templates.

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.