bullseye
CLAUDE.md4 starsChanged 24 days agoMITView on GitHub
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brief-decoderSkill
- build-sprintSkill
- bullseyeSkill
- demo-videoSkill
- finale-pitchSkill
- hackathon-trackerSkill
- idea-roundSkill
- judge-panelSkill
- missileSkill
- pitch-deckSkill
- prove-itSkill
- submission-packSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Use the Browser pane (or skills/missile/scripts/sense.mjs) to verify any visual change at 390 and 1440 against the production build.
- Very specific: line 8
When working on this repository, check plugin manifests with claude plugin validate .
≈ “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.
Files
@AGENTS.md
Claude Code notes
- Installed as a plugin, the skills are namespaced
/bullseye:<skill>(the flight director is/bullseye:bullseye) and the subagents arebullseye:missile-recon,bullseye:missile-critic,bullseye:missile-builder,bullseye:hackathon-judgeandbullseye:claims-auditor. - In skill files,
${CLAUDE_SKILL_DIR}resolves to the skill's own folder; use it to run bundled scripts. - Use the Browser pane (or
skills/missile/scripts/sense.mjs) to verify any visual change at 390 and 1440 against the production build. - When working on this repository, check plugin manifests with
claude plugin validate .in addition to the validator and tests.
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
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.

