Design motion
Use when building, styling, or animating any user interface, when auditing existing UI quality, or when refactoring legacy UI — components, pages, dialogs, forms, tables, lists, loading/empty/error states, hover/entrance/exit animations, transitions, CSS/Tailwind styling, dark mode, status chips — or when UI "feels off", janky, cheap, or inconsistent.From its SKILL.md
npx -y skills add klimofey/design-motion --skill design-motionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.5 KB, as published. Nobody here has run it
design-motion — UI craft rules
Distilled from designmotionhq.com's 63 free pattern breakdowns. Value = concrete numbers and anatomy, not taste words.
Step 0 — Palette first: the host design system WINS
Before styling anything, discover the host project's design system. Look for: a UI-kit
package (packages/ui, components/ui, shadcn), design tokens / theme CSS variables,
tailwind.config theme extensions, a components-palette or Storybook page, UI rules in
CLAUDE.md/AGENTS.md. If any exist: its colors, primitives, typography, radii, shadows,
and spacing override every generic value in this skill. Use its Badge/Button/Dialog — not
raw HTML + utility colors. These references then contribute only what the system leaves
unspecified: timing, easing, state completeness, interaction anatomy, accessibility.
Project instruction files always outrank this skill.
Mode dispatch
| Doing what | Read |
|---|---|
| Building new UI | the matching chapters below, before writing code |
| Auditing existing UI | references/audit-checklist.md |
| Refactoring legacy UI | references/refactor-playbook.md |
Chapters: references/motion.md (timing, easing, hover, scroll) · visual-foundations.md (hierarchy, grids, perception laws, honest charts) · surfaces-depth.md (shadows, layers, z-index, radius, dark mode, gradients) · color-tokens.md (tokens, systems, contrast, icons) · forms.md (field states, validation timing, pickers, steppers, OTP/password/file inputs) · feedback.md (loading/skeleton/optimistic, errors, empty states, toasts, undo, psych thresholds) · interaction.md (drag, dropdowns, search, tooltips, sheets, command palette, chips, accordions, data tables, modals) · navigation-content.md (nav, tabs, focus, pagination, microcopy, landing structure).
Non-negotiables (numbers that survive every project)
- Entrances 200–300ms ease-out, never linear, never past ~300ms.
- Every entrance has an exit — ~40% faster (250ms in → ~150ms out), ease-in. Unmounting instantly is a defect.
- Press feedback <100ms · list stagger ~50ms · attention motion only 500–800ms with overshoot.
prefers-reduced-motionhandled — near-zero durations, notanimation: none(keep animationend firing).- Content-shaped loading = skeleton with shimmer matching final layout (no skeleton under 300ms loads; partial content by ~2s). Spinner only for non-content waits; never both in one view.
- Every data surface designs all four: loading / empty / error / loaded. Empty is an invitation; error names what happened + a retry.
- Colors only from the system's tokens/variants — a raw
bg-blue-100-style literal next to a design system is a defect (breaks theming + dark mode). - Validate on blur; after a field errors, go live so the error clears instantly; confirm success (check), don't only flag failure.
- A toast advertising undo lives ≥5s; destructive actions get undo or confirm — never bare.
- No z-index arms race:
position+isolation: isolate, system scale only. - Focus always visible — removing an outline without a replacement is a defect.
When any rule conflicts with the host system or project instructions, the host wins (Step 0).