design-motion-principles

Create and audit UI motion using designer-weighted principles for React, Framer Motion, and CSS.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/dylinmat/design-skills-plugin --skill design-motion-principles-dylinmat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-motion-principles
Source: https://github.com/dylinmat/design-skills-plugin/tree/main/plugins/design/skills/design-motion-principles
Command: npx skills add https://github.com/dylinmat/design-skills-plugin --skill design-motion-principles-dylinmat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? UI animation work often suffers from two failure modes: motion added without purpose (AI-slop patterns like pulsing indicators and hover-scale-on-everything) and existing animations that lack systematic review. This Skill provides a structured, expert-grounded framework for both building purposeful motion and auditing existing animations against the published techniques of Emil Kowalski, Jakub Krehel, and Jhey Tompkins. ## Core Features & Use Cases - Create Mode: Build interactive components with purposeful motion, applying a frequency gate, context-weighted designer perspectives, and recipes from a motion cookbook covering enter/exit animations, springs, clip-path, and scroll-driven effects. - Audit Mode: Systematically review existing animation code, detect motion gaps (conditional renders without transitions), flag AI-slop patterns, and emit a branded self-contained HTML report with looping per-finding demo cards. - Context-Aware Weighting: Maps project types (SaaS dashboard, kids app, portfolio, e-commerce) to primary/secondary designer perspectives so rules like sub-300ms durations are applied only where appropriate. - Use Case: Ask it to audit a React app's Framer Motion code; it performs reconnaissance, proposes a designer weighting, checks the anti-checklist and accessibility requirements, then writes an HTML report to motion-audits/ and opens it in your browser. ## Quick Start Ask the agent to audit the animations in this project and produce a motion report, or ask it to build an animated component such as a toast notification with purposeful motion.

Frequently Asked Questions about design-motion-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit existing animations in a React project?

Ask for a motion audit of your project. The skill runs reconnaissance on your codebase, detects conditional renders missing AnimatePresence, proposes a designer weighting for your project type, then produces an HTML report with per-finding looping demos saved to a motion-audits directory.

How do I add purposeful animations to a Framer Motion component?

Describe the component and interaction you want to build. The skill applies a frequency gate to decide if motion is warranted, selects recipes from its motion cookbook (opacity plus translateY plus blur enters, subtler exits, spring configs), and includes prefers-reduced-motion handling in the generated code.

What AI-slop motion patterns does the audit detect?

The audit flags pulsing indicators, blur-everywhere entrances, hover-scale applied uniformly, stagger on every list, bouncy springs on utility actions like dropdowns, uniform fade-ins across components, and entrance motion on static text content. Each category has a frequency heuristic so single intentional uses are not flagged.

Does this work with plain CSS animations or only Framer Motion?

It covers CSS, HTML, React, Framer Motion, and iOS/Android transition concepts. The cookbook includes pure-CSS techniques like the linear() easing function, @property typed custom properties, clip-path reveals, and scroll-driven animations alongside Framer Motion patterns.

How does the skill handle prefers-reduced-motion accessibility?

Accessibility handling is mandatory in both modes. Every generated animation ships with a prefers-reduced-motion path in the same code, and every audit verifies reduced-motion support, vestibular triggers, and pausable looping animations as a non-negotiable checklist item.

When should UI animations be avoided entirely?

Avoid animation on high-frequency interactions triggered hundreds of times daily and on keyboard-initiated actions, per Emil Kowalski's frequency rule. Productivity tools favor instant or sub-300ms transitions, while rare interactions like onboarding can support more expressive motion.