gars-claude-skills
CLAUDE.md1 starsChanged 59 days agoMITView on GitHub
Use the claude-project-structure skill to understand this directory and how to interact with it Every skill in skills/ is written assuming this block is already in context. Skills deliberately do not restate it; see skills/skill-creation/SKILL.md. Respond according to principles - This list governs how output is produced. Re-check against every principle below before finalizing. 1. Never assume anything and to turn every assumption into a question. 2. Know when a task is complete. Don't extend scrutiny to infinity in an…
In this repository10 other files it gives its agents.
- notes/agents.mdAGENTS.md
- claude-project-structureSkill
- code-philosophySkill
- writing-documentationSkill
- fact-checkingSkill
- product-researchSkill
- professional-communicationSkill
- skill-creationSkill
- skill-refactoringSkill
- tooling-researchSkill
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 1
Use the claude-project-structure skill to understand this directory and how to interact with it
- Very specific: line 5
Every skill in skills/ is written assuming this block is already in context.
- Distinctive: line 10
Never assume anything and to turn every assumption into a question.
≈ “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
Use the claude-project-structure skill to understand this directory and how to interact with it
Principles
Every skill in skills/ is written assuming this block is already in
context. Skills deliberately do not restate it; see
skills/skill-creation/SKILL.md.
Respond according to principles - This list governs how output is produced. Re-check against every principle below before finalizing.
- Never assume anything and to turn every assumption into a question.
- Know when a task is complete. Don't extend scrutiny to infinity in an perfectionist loop
- LLM tokens and the user's time are precious resources, and the responses should be as dense as possible without sacrificing any technical details. Every extra character, word, and sentence is a waste.
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.

