agentleFS
Sign inStart free
bharathgnanabharathgnana/archdiagram/CLAUDE.md

archdiagram

CLAUDE.md3 starsChanged 5 months agoMITView on GitHub

Guidance for Claude Code when working in this repository. A reviewer running in Cursor watches the executing agent (Claude, in the terminal) and steers it without interrupting the chat, via bridge files. This convention works in every repo (a user-scope hook activates it automatically). - Bridge files are named suggestions_*.md — e.g. plans/suggestions_NN_<slug>.md beside a plan, or a top-level suggestions_<topic>.md. The Cursor reviewer owns them (creates / rewrites / erases). The executor never deletes a reviewer's directives. - Claude polls…

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:

    When you are the Cursor reviewer: write suggestions_*.md with a ## Open Directives list of short, testable - [ ] items plus a ## Claude …

    line 26

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

CLAUDE.md

Guidance for Claude Code when working in this repository.

Cursor↔Claude live-review bridge

A reviewer running in Cursor watches the executing agent (Claude, in the terminal) and steers it without interrupting the chat, via bridge files. This convention works in every repo (a user-scope hook activates it automatically).

  • Bridge files are named suggestions_*.md — e.g. plans/suggestions_NN_<slug>.md beside a plan, or a top-level suggestions_<topic>.md. The Cursor reviewer owns them (creates / rewrites / erases). The executor never deletes a reviewer's directives.
  • Claude polls the relevant suggestions_*.md before starting a task and after every task/checkbox.
  • ## Open Directives (- [ ]) are binding. On conflict with the plan/spec body, the directive wins (the reviewer has fresher context).
  • Claude acknowledges under ## Claude Acknowledgements, ticking - [ ] → - [x] and referencing the code/tests that close each one. Blockers are surfaced there.
  • Automated — no manual nudge. A user-scope Stop hook (~/.claude/hooks/suggestions_watch.py, wired in ~/.claude/settings.json) runs at the end of every turn: if a suggestions_*.md changed and still has unchecked directives, it blocks the stop and re-injects them. It baselines on first sight, guards against loops, and fails open. Hooks load at session start, so restart an in-flight session (or run /hooks) if the bridge does not fire.
  • When you are the Cursor reviewer: write suggestions_*.md with a ## Open Directives list of short, testable - [ ] items plus a ## Claude Acknowledgements heading, and reference the bridge file from the plan/spec.

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