clarity
Skill0 starsChanged todayMITView on GitHub
Distill a tangled thought, stuck decision, or messy artifact into what is actually happening, the crux, hidden assumptions, and the next concrete move.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- flowcopilot/skillstheir own version, first seen Nov 15, 2026
- raditia/CraftKittheir own version, first seen Nov 8, 2026
- harlan-zw/brundleflytheir own version, first seen Nov 8, 2026
- JBSommeling/claude-configtheir own version, first seen Nov 1, 2026
- jackson2w/claude-code-skillstheir own version, first seen Nov 1, 2026
- rogue-dev-studio/ai-agents-roguetheir own version, first seen Nov 1, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- addyosmani/clarity★ 219same name
- harlan-zw/brundlefly★ 7same name
- getedgehq/skills★ 5same name
- rogue-dev-studio/ai-agents-rogue★ 2same name
- X-FRI/skills★ 2same name
- cemkazim/claude-skill-clarity★ 1same name
- Claude-Mem/clarity★ 1same name
- flowcopilot/skills★ 1same name
- jackson2w/claude-code-skills★ 1same name
- raditia/CraftKit★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository72 other files it gives its agents.
- animate-expoSkill
- animateSkill
- animation-performanceSkill
- animation-vocabularySkill
- apple-designSkill
- ask-emilSkill
- ask-mattSkill
- ask-sonnerSkill
- better-typographySkill
- break-uiSkill
- chief-of-staffSkill
- choreographSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- cold-emailSkill
- content-strategySkill
- copywritingSkill
- croSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- frontend-designSkill
- gesturesSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-animationsSkill
- improve-codebase-architectureSkill
- learn-tasteSkill
- loop-meSkill
- marketing-psychologySkill
- migrate-to-shoehornSkill
- mobile-nativeSkill
- persuasionSkill
- pick-ui-librarySkill
- prisma-client-apiSkill
- programmatic-seoSkill
- prototypeSkill
- prototype-variantsSkill
- prSkill
- remove-animationsSkill
- researchSkill
- retroSkill
- review-animationsSkill
- scaffold-exercisesSkill
- seo-auditSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- Skillpack Self-testSkill
- software-factorySkill
- supabase-postgres-best-practicesSkill
- tddSkill
- teachSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
7
Distinctive
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
- Very specific: line 11
If the working directory has a GLOSSARY.md (or GLOSSARY-MAP.md), read it silently first and hold to its terms.
- Distinctive: line 15
Plain, calm, direct prose: Every sentence earns its place.
- Distinctive: line 17
Split conflated terms: When one vague word (*"broken"*, *"scale"*, *"risky"*, *"stuck"*) bundles two or three distinct ideas, name each …
- Distinctive: line 24
When invoked with no context or only a bare signal (*"I'm stuck"*), skip explaining this framework and ask two short prompts:
- Distinctive: line 28
Wait for the dump before moving to step 2.
- Distinctive: line 32
Read the single reference matching the dominant shape of the input.
- Distinctive: line 40
When the user points to a file or thread, read only what they pointed to.
- Distinctive: line 52
Check before finishing: every conflated term split, every unverified constraint marked as an assumption, and one concrete move named.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Clarity
Cut through fog. Take whatever messy thought, stuck choice, or tangled artifact the user brings and surface what is real, what matters, and what moves next.
If the working directory has a GLOSSARY.md (or GLOSSARY-MAP.md), read it silently first and hold to its terms.
Voice and discipline
- Plain, calm, direct prose. Every sentence earns its place.
- Facts apart from assumptions. Label unverified claims, fears, and inferences as assumptions rather than treating them as fixed reality.
- Split conflated terms. When one vague word ("broken", "scale", "risky", "stuck") bundles two or three distinct ideas, name each meaning separately.
- Stay self-contained. End with a concrete move the user can take immediately; never assume external tools or other skills.
Working loop
1. Draw out the dump if empty
When invoked with no context or only a bare signal ("I'm stuck"), skip explaining this framework and ask two short prompts:
- What is happening right now? Dump it raw — half-baked or contradictory is fine.
- What decision, friction, or outcome is forcing the issue today?
Wait for the dump before moving to step 2.
2. Route to the fog's shape
Read the single reference matching the dominant shape of the input. Load a second only when the dump genuinely spans two shapes.
| The dump looks like | Read |
| Overload, competing threads, mixed facts and worry, unclear bottleneck | tangles |
| Circling options, false binaries, competing trade-offs, analysis paralysis | decisions |
| A pasted or referenced note, doc, thread, or half-formed concept with blurred points | artifacts |
When the user points to a file or thread, read only what they pointed to.
3. Distill through five lenses
Produce a crisp breakdown using the lenses that actually apply (skip any lens that would only force filler):
- What's actually happening — observable facts stripped of story, worry, or padding.
- The crux — the single question, tension, or bottleneck everything else hangs on.
- Hidden assumptions & false constraints — what is treated as fixed, binary, or urgent without evidence, plus any conflated terms split apart.
- Signal vs. noise — what moves the needle now vs. secondary threads to park.
- Next concrete move — the smallest reversible step or choice that resolves or tests the crux.
Check before finishing: every conflated term split, every unverified constraint marked as an assumption, and one concrete move named.
4. Pinpoint remaining unknowns
End with 1–3 sharp questions only when a critical unknown blocks naming the crux or next move. When the fog is already clear enough to act, stop after Next concrete move.
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.

