agentleFS
sshahzaiibsshahzaiib/agy-bridge/CLAUDE.md

agy-bridge

CLAUDE.md61 starsChanged 5 months agoMITView on GitHub

You have agy-bridge MCP tools that delegate heavy work to the Antigravity CLI (Gemini). Delegation keeps large content OUT of your context — only answers come back. Prefer delegating over doing it yourself when: - Any file >200 lines you'd otherwise read → analyze_files - More than 3 files in one analysis/comparison → analyze_files - Git history or repo-wide searches (git log/diff/blame, broad greps) → deep_search - Web/documentation lookups → web_lookup - Plan critique or code review → adversarial_review (always…

  • In this repositoryOne other file it gives its agents.

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:

    Do NOT delegate: small single-file edits, questions you can answer from context already loaded, or tasks needing tools only you have.

    line 16

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

Delegation rules: agy-bridge

You have agy-bridge MCP tools that delegate heavy work to the Antigravity CLI (Gemini). Delegation keeps large content OUT of your context — only answers come back. Prefer delegating over doing it yourself when:

  • Any file >200 lines you'd otherwise read → analyze_files
  • More than 3 files in one analysis/comparison → analyze_files
  • Git history or repo-wide searches (git log/diff/blame, broad greps) → deep_search
  • Web/documentation lookups → web_lookup
  • Plan critique or code review → adversarial_review (always — a second model family catches what you miss)
  • Follow-up question on a prior delegation → follow_up with the returned session id (never resend the context)

Do NOT delegate: small single-file edits, questions you can answer from context already loaded, or tasks needing tools only you have.

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.