skills / dotfiles
CLAUDE.md37 starsChanged 47 days agoMITView on GitHub
In this repository23 other files it gives its agents.
- find-me-a-skillSkill
- gap-scanSkill
- grill-docsSkill
- grillingSkill
- grill-meSkill
- handoff-autoSkill
- handoffSkill
- lanesSkill
- meta-orchestratorSkill
- pairSkill
- ponytailSkill
- progress-reportSkill
- pr-watchSkill
- remindSkill
- repo-scrubSkill
- repo-showcaseSkill
- score-loopSkill
- session-bridgeSkill
- sitrepSkill
- spend-gateSkill
- switchSkill
- teammate-briefSkill
- wayfinderSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
When tagging Claude in GitHub issues, use '@claude'
- Distinctive: line 23
When creating branches, prefix them with <your-prefix>/ to indicate they came from you.
≈ “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
<!--
Adapted from Matt Pocock's global CLAUDE.md (https://github.com/mattpocock, MIT):
the concision rule, @claude tagging, GitHub-CLI-first, and the plan-questions
rule are his. The branch prefix below is a placeholder (his is `matt/`) -
fill it in with scripts/setup-claude-md's --prefix/-Prefix, or by hand; the
author uses `krish/` (his public GitHub handle) as his own value. His
evalite-specific Changesets section was dropped: it only makes sense inside
that repo.
-->- In all interactions and commit messages, be extremely concise and sacrifice grammar for the sake of concision.
PR Comments
- When tagging Claude in GitHub issues, use '@claude'
GitHub
- Your primary method for interacting with GitHub should be the GitHub CLI.
Git
- When creating branches, prefix them with
<your-prefix>/ to indicate they came from you.
Plans
- At the end of each plan, give me a list of unresolved questions to answer, if any. Make the questions extremely concise. Sacrifice grammar for the sake of concision.
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.