first-four-hours
CLAUDE.md1 starsChanged 4 days agoMITView on GitHub
Before creating, reviewing, or changing a skill, read SKILL_PHILOSOPHY.md and apply its Change Gate. Before changing skills, packaging, validators, dependencies, runtime requirements, release configuration, tests, fixtures, or verification commands, read REPO_VERSIONING.md and follow its guidance, including Adding or changing tests. Never merge a PR. Before changing tests, read Adding or changing tests and obey the suite limits: at most three collected cases per skill, 12 shared, 48 total, with a complete passing repository suite within 120 seconds. Skill-specific tests, including…
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 5
Before creating, reviewing, or changing a skill, read SKILL_PHILOSOPHY.md and apply its Change Gate.
- Very specific: line 9
Before changing skills, packaging, validators, dependencies, runtime requirements, release configuration, tests, fixtures, or verification …
≈ “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.
Files
CLAUDE.md
Skill Design
Before creating, reviewing, or changing a skill, read SKILL_PHILOSOPHY.md and apply its Change Gate.
Repository Changes
Before changing skills, packaging, validators, dependencies, runtime requirements, release configuration, tests, fixtures, or verification commands, read REPO_VERSIONING.md and follow its guidance, including Adding or changing tests. Never merge a PR.
Testing Rules
Before changing tests, read Adding or changing tests and obey the suite limits: at most three collected cases per skill, 12 shared, 48 total, with a complete passing repository suite within 120 seconds. Skill-specific tests, including integrations, belong under tests/skills/<skill>/. Three is a ceiling, not a quota; strengthen or replace coverage when slots are full. Add tests only for real defects or missing acceptance behavior, not mundane fixture/formatting bookkeeping or implementation-detail assertions. Testing and repairs proceed automatically without approval; incomplete verification never counts as a pass.
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.

