agentleFS
waldo1001waldo1001/waldo.BCObservatory/CLAUDE.md

waldo.BCObservatory

CLAUDE.md13 starsChanged 24 days agoMITView on GitHub

Read AGENTS.md first. It is the entry point for both humans and agents working in this repository. Applies ONLY when the environment variable JARVIS_OPERATOR=1 is set. Human sessions ignore this section entirely. Everything else in this repository's rules still applies. - Approval happened upstream. The spec you are given is approved (status approved or label spec-approved). That approval also covers the PLAN phase for a plan rated safe or low-risk: write the plan, set it approved, continue. A plan rated…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Read AGENTS.md first. It is the entry point for both humans and agents working in this repository.

    line 1
  2. Distinctive:

    The operator holds git: Commit on your branch as the workflow says.

    line 16
  3. Very specific:

    Ambiguity is an answer, not a guess: If the spec is unclear, end with NEEDS-ANSWER: <question>.

    line 18

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

Read AGENTS.md first. It is the entry point for both humans and agents working in this repository.

<!-- waldo.Jarvis operator mode -->

Operator mode (waldo.Jarvis)

Applies ONLY when the environment variable JARVIS_OPERATOR=1 is set. Human sessions ignore this section entirely. Everything else in this repository's rules still applies.

  • Approval happened upstream. The spec you are given is approved (status approved or label spec-approved). That approval also covers the PLAN phase for a plan rated safe or low-risk: write the plan, set it approved, continue. A plan rated risky or breaking stops here: write it and end with PLAN-WAITING.
  • Use the repository's two entry points. To build a spec run /sdd-build {spec}; to draft a spec from an issue run /sdd-draft {issue}. Follow the skill exactly; do not substitute your own workflow.
  • The operator holds git. Commit on your branch as the workflow says; never push, never open or merge a PR, never touch the default branch.
  • Ambiguity is an answer, not a guess. If the spec is unclear, end with NEEDS-ANSWER: <question>.
  • End with the report the operator handed you.

Taking over from the League

A branch league/<issue>-<topic> with an open PR labelled league-building is being built by waldo.Jarvis. To take over: stop the build (HUD, phone, or the Jarvis MCP tool stop_league_build), then git fetch && git switch league/<issue>-<topic>. The PR body section ## League state tells you the phase, the last test run, what is done and what is next. Continue as a normal human session; merge when satisfied. The League will not touch the branch again unless you hand it back.

<!-- /waldo.Jarvis operator mode -->

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.