ask-emil
Skill0 starsChanged todayMITView on GitHub
Ask which skill or flow fits your situation. A router over the skills in this repo.
1 other project uses a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- emilkowalski/skillsword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- emilkowalski/skills★ 57k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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-mattSkill
- ask-sonnerSkill
- better-typographySkill
- break-uiSkill
- chief-of-staffSkill
- choreographSkill
- claritySkill
- 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. About 0 are common, 2 are distinctive, and 6 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
/choreograph: when several elements move together: staggers, hero entrances, view swaps, an item leaving while siblings close the gap. - Very specific: line 21
/gestures: when the user's finger drives it: drag, swipe, sheets, snap points, swipe-to-dismiss. - Very specific: line 23
/ask-sonner: when the work is toasts with Sonner. - Distinctive: line 25
Try to break it: Before calling it done:
- Very specific: line 28
/mobile-native: if it runs on a phone as a web app: sticky hover, the 100vh bug, inputs that zoom, safe areas. - Very specific: line 29
/animation-performance: if anything drops frames. - Distinctive: line 35
Not feature work. Run these when you have a spare moment, or when the app "feels off".
- Very specific: line 49
/animation-vocabulary: when the problem is the word.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
Ask Emil
Before stating what a skill does or recommending one, read that skill's SKILL.md: the summaries here are for orientation only. Then recommend one skill (or one short sequence) for the user's situation, say why in a sentence, and name the skill they'd reach for next. Don't list the whole map back at them.
A flow is a path through the skills. Most UI work travels one main flow, from idea to shipped. Some skills are upkeep you run on a codebase that already exists, some are references that sit underneath everything, and a few stand alone.
The main flow: idea → ship
- Not sure what it should look or feel like? Detour through
/prototype. It builds several genuinely different versions behind a live picker, then promotes the one you pick into the real code. Reach for it whenever a design question is hard to settle in words. - Build it. Pick the builder by what's moving:
/pick-ui-libraryfirst if the task needs a dependency (dropdown, dialog, toast, drawer, command menu, drag and drop, charts). Don't let the agent hand-roll a toast./animatefor one animation on the web: whether to animate at all, then tool, properties, curve, duration, interruption, exit./choreographwhen several elements move together: staggers, hero entrances, view swaps, an item leaving while siblings close the gap./gestureswhen the user's finger drives it: drag, swipe, sheets, snap points, swipe-to-dismiss./animate-expofor any of the above in React Native or Expo./ask-sonnerwhen the work is toasts with Sonner.
- Try to break it. Before calling it done:
/break-uifeeds it worst-case data (long names, empty lists, huge counts, emoji, non-Latin text) behind a toggle and reports what broke./review-animationsreviews the motion in the diff against a strict bar. Default to flagging; approval is earned./mobile-nativeif it runs on a phone as a web app: sticky hover, the 100vh bug, inputs that zoom, safe areas./animation-performanceif anything drops frames.
- Learn from the session.
/learn-tastecloses the loop. Run it at the end, in the same session, before you clear: it collects every design correction you made (including edits you made yourself) and turns each into a rule with its why, so the next agent doesn't repeat the mistake.
Upkeep: a codebase that already exists
Not feature work. Run these when you have a spare moment, or when the app "feels off".
- The motion needs work across the app →
/improve-animations. Read-only: it audits every animation and writes prioritized, self-contained plans another agent (or a cheaper model) can execute. - It feels static →
/find-animation-opportunities. Read-only: it proposes motion with exact values, and rejects everything that shouldn't move. Build the ones you accept with/animate. - It feels slow or over-animated →
/remove-animations. Edits code, but only to subtract: motion on keyboard actions, high-frequency surfaces, decoration with no purpose.
These three cover different questions. If the user isn't sure which, ask whether the problem is bad motion, missing motion, or too much motion.
References underneath
Model-invoked skills the others lean on. Reach for them directly when the knowledge, not a process, is what's missing.
/emil-design-eng: the core philosophy for UI polish, component interactions, and the invisible details. The fallback when no narrower skill fits./apple-design: Apple's principles for interface design and fluid, physical motion, translated for the web./animation-vocabulary: when the problem is the word. "What's it called when…" turns a vague description into the exact term to prompt with.
Standalone
/write-swift: modern Swift, Swift 6 concurrency, and native iOS code. Off the web flow entirely.
Common situations
| You say | Reach for |
| "Animate this" | /animate |
| "These should come in one after another" | /choreograph |
| "It doesn't follow my finger" | /gestures |
| "It stutters" / "it's janky" | /animation-performance |
| "Does this animation feel right?" | /review-animations |
| "Make the app feel better" | /improve-animations |
| "What could animate here?" | /find-animation-opportunities |
| "Too much is moving" | /remove-animations |
| "Give me a few options" | /prototype |
| "Which library should I use?" | /pick-ui-library |
| "Works in Chrome, feels wrong on my phone" | /mobile-native |
| "Try the worst case" | /break-ui |
| "What's that bouncy thing called?" | /animation-vocabulary |
| "Stop making that mistake" | /learn-taste |
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.

