genefoundry-router
CLAUDE.md6 starsChanged 4 months agoMITView on GitHub
Claude Code entrypoint only: - Use AGENTS.md for shared repository instructions. - Keep Claude-specific additions here short and tool-specific. - Prefer make ci-local before final handoff (runs lint-loc, the 600-LOC budget). - FastMCP 3.x symbols are post-training-cutoff and fast-moving — verify imports against the installed package before relying on them (see the import smoke in docs/plans/2026-06-13-genefoundry-router-implementation.md, Task 2). - When a backend's source repo adopts Tool-Naming Standard v1, delete its transform block from servers.yaml rather than adding router-side workarounds.
We split this CLAUDE.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Use AGENTS.md for shared repository instructions.
- Distinctive: line 8
Keep Claude-specific additions here short and tool-specific.
- Very specific: line 9
Prefer make ci-local before final handoff (runs lint-loc, the 600-LOC budget).
- Very specific: line 13
When a backend's source repo adopts Tool-Naming Standard v1, delete its transform block from servers.yaml rather than adding router-side …
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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.
Files
CLAUDE.md
@AGENTS.md
Claude Code entrypoint only:
- Use
AGENTS.mdfor shared repository instructions. - Keep Claude-specific additions here short and tool-specific.
- Prefer
make ci-localbefore final handoff (runslint-loc, the 600-LOC budget). - FastMCP 3.x symbols are post-training-cutoff and fast-moving — verify imports
against the installed package before relying on them (see the import smoke in
docs/plans/2026-06-13-genefoundry-router-implementation.md, Task 2). - When a backend's source repo adopts Tool-Naming Standard v1, delete its
transformblock fromservers.yamlrather than adding router-side workarounds.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- auth-changeSkill
- backend-registry-changeSkill
- ci-failure-triageSkill
- code-quality-reviewSkill
- dependency-cve-sweepSkill
- fleet-drift-conformanceSkill
- fleet-standard-adoptionSkill
- release-readinessSkill
- security-reviewSkill
- tool-search-changeSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

