claudinho
CLAUDE.md35 starsChanged 34 days agoMITView on GitHub
This project uses AGENTS.md as the primary agent guide. Read it first: - Follow AGENTS.md → "Working agreement", "Validation scope", and "Pre-PR self-review". They define completion, checks by change type, and when an independent reviewer is required. - After a push to a branch with CI, confirm the run's headSha matches the pushed commit, wait for completion, and report the per-job result. A successful watch command alone is not proof that a queued run passed. scripts/push-and-watch.sh <branch> is the form…
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/bundle-bracket-pr.mdcCursor rule
- .cursor/rules/change-discipline.mdcCursor rule
- .cursor/rules/release-discipline.mdcCursor rule
- .cursor/rules/surface-parity.mdcCursor rule
- .cursor/rules/trust-boundary.mdcCursor rule
- claudinho-modeSkill
- verify-claudinhoSkill
- claudinho-modeSkill
- verify-claudinhoSkill
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
- Distinctive: line 15
Follow AGENTS.md → "Working agreement", "Validation scope", and "Pre-PR self-review".
≈ “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
CLAUDE.md
This project uses AGENTS.md as the primary agent guide. Read it first:
@AGENTS.md
Claude Code specifics
- The statusline command must return in <150ms and never hit the network on the hot path — read from the local micro-cache.
- Local MCP dev loop:
pnpm -F @claudinho/mcp build claude mcp add claudinho-dev -- node packages/mcp/dist/index.js - Follow
AGENTS.md→ "Working agreement", "Validation scope", and "Pre-PR self-review". They define completion, checks by change type, and when an independent reviewer is required. - After a push to a branch with CI, confirm the run's
headShamatches the pushed commit, wait for completion, and report the per-job result. A successful watch command alone is not proof that a queued run passed.scripts/push-and-watch.sh <branch>is the form of it: it pushes, reads the SHA back, and prints the per-job result of the CI run on that SHA.
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.