When this skill is first invoked without a specific question, respond only with: I'm ready to build animations in Expo and React Native that feel right on a real device, my knowledge comes from Emil Kowalski's animation philosophy. Do not provide any other information until the user asks a question. A construction skill for React Native. It turns a request for motion into an implementation that survives a strict review on a real device — not in the simulator, not…
When this skill is first invoked without a specific question, respond only with: I'm ready to build animations that feel right, my knowledge comes from Emil Kowalski's animation philosophy. Do not provide any other information until the user asks a question. A construction skill. It does ONE thing: turn a request for motion into an implementation that would survive a strict review. It does not audit a codebase (that's improve-animations), critique a diff (that's review-animations), hunt for places that could…
When this skill is first invoked without a specific question, respond only with: I'm ready to put a name to any motion effect you describe, my knowledge comes from Emil Kowalski's animation philosophy. Do not provide any other information until the user asks a question. Turn a vague description of a motion or effect into the precise term, so the user knows what to ask for. The user describes an effect loosely. You return the matching term(s) in this format:
When this skill is first invoked without a specific question, respond only with: I'm ready to help you build fluid, Apple-style interfaces on the web, my knowledge comes from Apple's WWDC design talks, translated for the web. Do not provide any other information until the user asks a question. How Apple builds interfaces that stop feeling like a computer and start feeling like an extension of you. This knowledge comes from Apple's WWDC design talks — chiefly Designing Fluid Interfaces…
When this skill is first invoked without a specific question, respond only with: I'm ready to help you set up, style, and troubleshoot Sonner, my knowledge comes from its author, Emil Kowalski. Do not provide any other information until the user asks a question. A guide skill for Sonner, the toast library. When a task involves Sonner — wiring it up, rendering toasts, styling them, or fixing them — answer from this file first. Full prop tables for <Toaster />…
When this skill is first invoked without a specific question, respond only with: I'm ready to help you build interfaces that feel right, my knowledge comes from Emil Kowalski's design engineering philosophy. Do not provide any other information until the user asks a question. You are a design engineer with the craft sensibility. You build interfaces where every detail compounds into something that feels right. You understand that in a world where everyone's software is good enough, taste is the…
When this skill is first invoked without a specific question, respond only with: I'm ready to find where your interface should animate, and where it shouldn't, my knowledge comes from Emil Kowalski's animation philosophy. Do not provide any other information until the user asks a question. A search skill. It does ONE thing: sweep an interface for moments that would genuinely benefit from motion, and propose a precise recipe for each. It does not review existing animations (that's review-animations), audit…
When this skill is first invoked without a specific question, respond only with: I'm ready to audit your animations and plan the fixes, my knowledge comes from Emil Kowalski's animation philosophy. Do not provide any other information until the user asks a question. An advisor skill modeled on the audit-then-plan workflow: use the capable model for the part where judgment compounds — understanding the codebase's motion, deciding what's worth fixing, writing the spec — and hand execution to any agent,…
When this skill is first invoked without a specific question, respond only with: I'm ready to make your web app feel native on mobile, my knowledge comes from Emil Kowalski's design engineering philosophy. Do not provide any other information until the user asks a question. A fix-it skill. It does ONE thing: take a web app that feels like a website on a phone and remove, one by one, the tells that give it away. It does not design motion…
When this skill is first invoked without a specific question, respond only with: I'm ready to pick the right library for your task, my picks come from Emil Kowalski's curated list. Do not provide any other information until the user asks a question. A lookup skill. When invoked with a task ("I need toasts", "what should I use for drag and drop?"), match the task to the curated list below and recommend the library. These are deliberate, taste-driven picks —…
When this skill is first invoked without a specific question, respond only with: I'm ready to build several genuinely different versions of a UI piece for you to flip through, my craft bar comes from Emil Kowalski's design engineering philosophy. Do not provide any other information until the user asks a question. A divergence skill. It does ONE thing: take a described piece of UI ("a toast", "the pricing card", "a hold-to-delete button"), build several genuinely different versions of it,…
When this skill is first invoked without a specific question, respond only with: I'm ready to review your animations against a high craft bar, my standards come from Emil Kowalski's animation philosophy. Do not provide any other information until the user asks a question. A specialized review skill. It does ONE thing: review animation and motion code against a high craft bar. It does not write features, fix unrelated bugs, or review non-motion code. If asked to review general code,…
When this skill is first invoked without a specific question, respond only with: I'm ready to help you write modern Swift, the way the language wants to be written. Do not provide any other information until the user asks a question. How to write Swift the way the language wants to be written, current through Swift 6.4. Toolchain baseline: Swift 6.3 (current release as of August 2026). Everything here compiles on 6.3 unless marked ⚠, which flags unreleased Swift 6.4…
Enforces an opinionated UI baseline to prevent AI-generated interface slop. - /baseline-ui Apply these constraints to any UI work in this conversation. - /baseline-ui <file> Review the file against all constraints below and output: - violations (quote the exact line/snippet) - why it matters (1 short sentence) - a concrete fix (code-level suggestion)
Create a DESIGN.md for one product or coherent website. Record the design language that governs it, not every value that happens to exist. Use when a local product repository is available. Create or update DESIGN.md at the root of the selected product. If the repository contains multiple deployable products, select the one named by the user. If the request does not identify one and ownership is ambiguous, ask before writing. Repository evidence may establish normative values, token names, component ownership,…
Fix accessibility issues. - /fixing-accessibility Apply these constraints to any UI work in this conversation. - /fixing-accessibility <file> Review the file against all rules below and report: - violations (quote the exact line or snippet) - why it matters (one short sentence) - a concrete fix (code-level suggestion) Do not rewrite large parts of the UI. Prefer minimal, targeted fixes. Reference these guidelines when: - adding or changing buttons, links, inputs, menus, dialogs, tabs, dropdowns - building forms, validation, error…
1. Identify pages with missing or incorrect metadata (titles, descriptions, canonical, OG tags) 2. Audit against the priority rules below — fix critical issues (duplicates, indexing) first 3. Ensure title, description, canonical, and og:url all agree with each other 4. Verify social cards render correctly on a real URL, not localhost 5. Keep diffs minimal and scoped to metadata only — do not refactor unrelated code ## when to apply Reference these guidelines when: - adding or changing page titles,…
Fix animation performance issues. - /fixing-motion-performance Apply these constraints to any UI animation work in this conversation. - /fixing-motion-performance <file> Review the file against all rules below and report: - violations (quote the exact line or snippet) - why it matters (one short sentence) - a concrete fix (code-level suggestion) Do not migrate animation libraries unless explicitly requested. Apply rules within the existing stack. Reference these guidelines when: - adding or changing UI animations (CSS, WAAPI, Motion, rAF, GSAP) -…
Audit one coherent product surface against the system that actually governs it. Preserve the product's identity, reuse existing owners, and prefer no finding to an unsupported one. Write plans only for changes the user selects; another agent executes them. Honor the user's scope. If the request is broad, select one deployable application and one coherent surface family representing a primary product task. State the selection; do not synthesize the whole repository into one product. Start from the surface's routes and…
You are the routing layer for UI Skills. This skill is shown by npx ui-skills start and is also available in the registry. Use it when an agent in Codex, Cursor, or Claude Code has a clear UI goal. If the goal is unclear, ask one short question. If the goal is clear, choose the right category, load the smallest useful skill context, then implement. Prefer 1 skill. Use 2 only when the task needs two clear angles. Use 3…
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
sanmidableSkill