oops-skills
CLAUDE.md4 starsChanged 3 months agoMITView on GitHub
@.ai/workflows/onboarding.md @.ai/workflows/task-flow.md @.ai/commands.md
In this repository12 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- clarify-scopeSkill
- create-pr-descriptionSkill
- debugSkill
- implement-tddSkill
- plan-tasksSkill
- review-prSkill
- setup-ai-contextSkill
- shipSkill
- sync-ai-contextSkill
- write-specSkill
- write-test-scenariosSkill
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 9
Follow .ai/workflows/onboarding.md — read in order, do not skip.
- Very specific: line 12
Follow .ai/workflows/task-flow.md — do not merge until self-check is complete.
- Distinctive: line 16
Do not edit migration files that have already run in production
- Distinctive: line 17
Do not push to the main branch
- Very specific: line 18
Do not add new dependencies without recording them in .ai/decisions/
≈ “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
<!-- Claude Code adapter — points to .ai/ as source of truth -->@.ai/workflows/onboarding.md @.ai/workflows/task-flow.md @.ai/commands.md
When starting a new session
Follow .ai/workflows/onboarding.md — read in order, do not skip.
When assigned a task
Follow .ai/workflows/task-flow.md — do not merge until self-check is complete.
NEVER
<!-- TODO: add hard constraints for this project here -->- Do not edit migration files that have already run in production
- Do not push to the main branch
- Do not add new dependencies without recording them in
.ai/decisions/
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.

