SponsoredSkillry: Agent Skills with taste. Designed and tested in-house, so one prompt gives you polished slides, web pages and launch videos.Skillry: Agent Skills with taste Try free Skills
Agent Skills
  • Skills
  • Picks
  • ShopSoon
  • Solutions
  • Specification
  • Submit
Agent Skills
Agent Skills

Discover and share powerful Agent Skills for AI assistants

GitHubX (Twitter)
Skills
  • View All
  • Install Guide
  • Documentation
  • Solutions
  • Product Launch Video
  • Submit
Tools
  • Claude Code
  • Cursor
  • OpenCode
  • Codex CLI
  • Gemini CLI
Resources
  • anthropics/skills
  • awesome-claude-skills
  • vercel-labs/agent-skills
  • kepano/obsidian-skills
Company
  • About
  • Changelog
  • Privacy Policy
  • Terms of Service

Sponsored by Vectrust @ OpenDev Org & NextRouter Alliance

© 2026 EvergreenAI. Built with JimmyLv
design-motion-principles - Agent Skill - Agent Skills
Home/Skills/design-motion-principles

design-motion-principles

87

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.

Download FolderView on GitHub

CLI Install

Recommended

Use the skills CLI to install this skill with one command. Auto-detects all installed AI assistants.

Method 1 - skills CLI

npx skills i kylezantos/design-engineer-auditor-package/skills/design-motion-principles

Method 2 - openskills (supports sync & update)

npx openskills install kylezantos/design-engineer-auditor-package

Auto-detects Claude Code, Cursor, Codex CLI, Gemini CLI, and more. One install, works everywhere.

Installation Path

Download and extract to one of the following locations:

~/.claude/skills/design-motion-principles/
SKILL.md

Skill Instructions

Back

Run with Cloud Agent

No setup needed. Let our cloud agents run this skill for you.

Select Provider

Select Model

ClaudeClaude Sonnet 5.5
$0.20/task

Best for coding tasks

Join Cloud Agent Waitlist

No setup required

Before you install

Read from this skill's files on GitHub on 2026-11-09. These are facts about the files, not a review of how well the skill works.

Files
15 files, 0 scripts, SKILL.md is 877 words
Needs on your machine
Nothing beyond the agent: no scripts or install commands found
Web addresses in its scripts
No URLs in its scripts
Worth a look before running
No sudo, rm -rf, curl | sh or shell=True in its scripts
Agent Skills spec
name and description present, name matches the folder
Last upstream change
2026-05-30

Where this skill sits

  • Make a UI hold up

    Third, and only to audit motion you already shipped. It is an auditor, not a generator.

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 requestMode
"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 TypePrimarySecondarySelective
Productivity tool (Linear, Raycast)EmilJakubJhey (onboarding only)
Kids app / EducationalJakubJheyEmil (high-freq game interactions)
Creative portfolioJakubJheyEmil (high-freq interactions)
Marketing/landing pageJakubJheyEmil (forms, nav)
SaaS dashboardEmil

Core Principles (Both Modes)
The Frequency Gate

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

FrequencyRecommendation
Rare (monthly)Delightful, expressive motion welcome
Occasional (daily)Subtle, fast motion
Frequent (100s/day)No animation or instant transition
Keyboard-initiatedNever animate
Duration Guidelines (Context-Dependent)
ContextGuideline
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
FileContentsLoad When
Motion CookbookAll motion recipes — enter/exit, easing, springs, clip-path, @property, FLIP, scroll-drivenCreate mode (always); Audit mode for implementation recommendations
Creation GotchasClaude's failure modes when writing motionCreate mode (always)
Audit ChecklistSystematic audit checklistAudit mode (always)
Anti-ChecklistQuality gate — AI-slop motion categories + anti-patterns to flagAudit mode (always)
Workflow Index
WorkflowPurpose
CreateBuild interactive components with purposeful motion
AuditReview existing motion design, produce a per-designer report
Jakub
Jhey (empty states)
Mobile appJakubEmilJhey (delighters)
E-commerceJakubEmilJhey (product showcase)
Emil Kowalski
Restraint philosophy, frequency rule, decision frameworks
Either mode, if Emil is weighted
Jakub KrehelProduction polish philosophy and decision frameworksEither mode, if Jakub is weighted
Jhey TompkinsPlayful experimentation philosophy and frameworksEither mode, if Jhey is weighted
Accessibilityprefers-reduced-motion, vestibular safetyBoth modes (mandatory)
PerformanceGPU optimization, will-change, layout thrashEither mode, for complex animations
Output FormatAudit report template — HTML mode (default) + terminal mode (flag)Audit mode only
Demo ShellVisual container template for per-finding demo cards in the HTML reportAudit mode, HTML output