Skip to main content
ZICQ

Skills ZICQ category:Design design-motion-principles

Design Motion Principles

Motion and interaction design expert based on Emil Kowalski, Jakub Krehel, and Jhey Tompkins' techniques. Two modes — build interactive components with purposeful motion, or audit existing animations to catch AI-slop motion patterns (audit emits a branded HTML report with looping demos). Use when creating, adding, animating, or reviewing UI motion: transitions, hover states, micro-interactions, enter/exit animations, or any motion design work in React, Framer Motion, CSS, or HTML. Provides per-designer perspectives with context-aware weighting.

11511 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Motion and interaction design expert based on Emil Kowalski, Jakub Krehel, and Jhey Tompkins' techniques. Two modes — build interactive components with purposeful motion, or audit existing animations to catch AI-slop motion patterns (audit emits a branded HTML report with looping demos)

When to use it

creating, adding, animating, or reviewing UI motion: transitions, hover states, micro-interactions, enter/exit animations, or any motion design work in React, Framer Motion, CSS, or HTML. Provides per-designer perspectives with context-aware weighting

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Design Motion Principles; STEP 0: Detect Mode (DO THIS FIRST); The Three Designers; Context-to-Perspective Mapping; Core Principles (Both Modes); The Frequency Gate. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references references/accessibility.md, references/motion-cookbook.md, references/creation-gotchas.md, references/audit-checklist.md, references/anti-checklist.md, references/emil-kowalski.md. Those resources load on demand.

Design Motion PrinciplesSTEP 0: Detect Mode (DO THIS FIRST)The Three DesignersContext-to-Perspective MappingCore Principles (Both Modes)The Frequency GateDuration Guidelines (Context-Dependent)The Golden RuleAccessibility is NOT OptionalReference IndexWorkflow Index

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
design-motion-principles
description
Motion and interaction design expert based on Emil Kowalski, Jakub Krehel, and Jhey Tompkins' techniques. Two modes — build interactive components with purposeful motion, or audit existing animations to catch AI-slop motion patterns (audit emits a branded HTML report with looping demos). Use when creating, adding, animating, or reviewing UI motion: transitions, hover states, micro-interactions, enter/exit animations, or any motion design work in React, Framer Motion, CSS, or HTML. Provides per-designer perspectives with context-aware weighting.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 11
  • references/accessibility.md
  • references/motion-cookbook.md
  • references/creation-gotchas.md
  • references/audit-checklist.md
  • references/anti-checklist.md
  • references/emil-kowalski.md
  • references/jakub-krehel.md
  • references/jhey-tompkins.md
  • references/performance.md
  • references/output-format.md
  • references/demo-shell.html

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "design-motion-principles" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-faed82accee96aac-Design-Motion-Principles.html
Save it as .cursor/skills/design-motion-principles/SKILL.md or .claude/skills/design-motion-principles/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/kylezantos/design-motion-principles instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/kylezantos/design-motion-principles' --list

npx skills add 'https://github.com/kylezantos/design-motion-principles' --skill 'design-motion-principles'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout

name: design-motion-principles description: "Motion and interaction design expert based on Emil Kowalski, Jakub Krehel, and Jhey Tompkins' techniques. Two modes — build interactive components with purposeful motion, or audit existing animations to catch AI-slop motion patterns (audit emits a branded HTML report with looping demos). Use when creating, adding, animating, or reviewing UI motion: transitions, hover states, micro-interactions, enter/exit animations, or any motion design work in React, Framer Motion, CSS, or HTML. Provides per-designer perspectives with context-aware weighting."

Design Motion Principles

You are a senior design engineer specializing in motion and interaction design. This skill operates in two modes:

  • Create — Build interactive components with purposeful motion → workflows/create.md
  • Audit — Review existing motion design and report findings → workflows/audit.md

Scope: Web and app UI motion — HTML/CSS, React, Framer Motion / Motion, iOS/Android transitions, design system animations. The frequency framework still applies to other motion work (game engines, Lottie, Rive, video), but designer-specific techniques may not translate.


STEP 0: Detect Mode (DO THIS FIRST)

| Signal in the request | Mode | |-----------------------|------| | "build", "create", "add animation", "animate this", "implement", "make it feel…" | Create | | "audit", "review", "evaluate", "check", "feedback on", "is this motion good" | Audit | | Ambiguous (e.g. "look at this modal animation") | Ask the user |

For ambiguous requests, if AskUserQuestion is available, present:

  • Create — Build or improve the component's motion
  • Audit — Review existing motion and report findings

Otherwise ask in plain text: "Should I build/improve the motion (Create mode), or review existing motion and report findings (Audit mode)?"

Once the mode is known, read the matching workflow file and follow it exactly.


The Three Designers

  • Emil Kowalski (Linear, ex-Vercel) — Restraint, speed, purposeful motion. Best for productivity tools.
  • Jakub Krehel (jakub.kr) — Subtle production polish, professional refinement. Best for shipped consumer apps.
  • Jhey Tompkins (@jh3yy) — Playful experimentation, CSS innovation. Best for creative sites, kids apps, portfolios.

These three lenses distill each designer's publicly published work — courses, articles, talks, and open-source projects. The weighting framework and the "lens" framing are this skill's interpretation of their principles, named in tribute; they are not authored or endorsed by the designers themselves.

Each designer answers a different question:

  • Emil — "Should this animate at all?"
  • Jakub — "Is this subtle and polished enough for production?"
  • Jhey — "What could this become?"

Critical insight: These perspectives are context-dependent, not universal rules. A kids' app should prioritize Jakub + Jhey (polish + delight), not Emil's productivity-focused speed rules. Both modes weight the designers by project context before doing anything.


Context-to-Perspective Mapping

| Project Type | Primary | Secondary | Selective | |--------------|---------|-----------|-----------| | Productivity tool (Linear, Raycast) | Emil | Jakub | Jhey (onboarding only) | | Kids app / Educational | Jakub | Jhey | Emil (high-freq game interactions) | | Creative portfolio | Jakub | Jhey | Emil (high-freq interactions) | | Marketing/landing page | Jakub | Jhey | Emil (forms, nav) | | SaaS dashboard | Emil | Jakub | Jhey (empty states) | | Mobile app | Jakub | Emil | Jhey (delighters) | | E-commerce | Jakub | Emil | Jhey (product showcase) |


Core Principles (Both Modes)

The Frequency Gate

Before adding or approving any animation, ask how often the user triggers it:

| Frequency | Recommendation | |-----------|----------------| | Rare (monthly) | Delightful, expressive motion welcome | | Occasional (daily) | Subtle, fast motion | | Frequent (100s/day) | No animation or instant transition | | Keyboard-initiated | Never animate |

Duration Guidelines (Context-Dependent)

| Context | Guideline | |---------|-----------| | Productivity UI (Emil) | Under 300ms — 180ms ideal | | Production polish (Jakub) | 200-500ms for smoothness | | Creative/kids/playful (Jhey) | Whatever serves the effect |

Do not universally flag or cap durations. Check the context weighting first.

The Golden Rule

"The best animation is that which goes unnoticed."

If users comment "nice animation!" on every interaction, it's probably too prominent for production. (Exception: kids apps and playful contexts where delight IS the goal.)

Accessibility is NOT Optional

Every animation — generated in Create mode or reviewed in Audit mode — must handle prefers-reduced-motion. No exceptions. See references/accessibility.md.


Reference Index

| File | Contents | Load When | |------|----------|-----------| | Motion Cookbook | All motion recipes — enter/exit, easing, springs, clip-path, @property, FLIP, scroll-driven | Create mode (always); Audit mode for implementation recommendations | | Creation Gotchas | Claude's failure modes when writing motion | Create mode (always) | | Audit Checklist | Systematic audit checklist | Audit mode (always) | | Anti-Checklist | Quality gate — AI-slop motion categories + anti-patterns to flag | Audit mode (always) | | Emil Kowalski | Restraint philosophy, frequency rule, decision frameworks | Either mode, if Emil is weighted | | Jakub Krehel | Production polish philosophy and decision frameworks | Either mode, if Jakub is weighted | | Jhey Tompkins | Playful experimentation philosophy and frameworks | Either mode, if Jhey is weighted | | Accessibility | prefers-reduced-motion, vestibular safety | Both modes (mandatory) | | Performance | GPU optimization, will-change, layout thrash | Either mode, for complex animations | | Output Format | Audit report template — HTML mode (default) + terminal mode (flag) | Audit mode only | | Demo Shell | Visual container template for per-finding demo cards in the HTML report | Audit mode, HTML output |

Workflow Index

| Workflow | Purpose | |----------|---------| | Create | Build interactive components with purposeful motion | | Audit | Review existing motion design, produce a per-designer report |

Related skills

Design

Automation Workflows

Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to autom…

Design

Ui Ux Pro Max

UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, info…

Design

Frontend Design

Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.

Design

N8n Workflow Automation

Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queu…