ask-emil
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.