agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/design-motion-principles/SKILL.md

design-motion-principles

Skill136 starsChanged 5 months agoMITView on GitHub

Motion through Kowalski, Krehel and Jhey lenses.

15 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use design-taste-frontend.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnasX7Skill

    design-taste-frontend

    Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 1 is common, 2 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 15 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 64
  2. Distinctive:

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

    line 81
  3. Common:

    If users comment "nice animation!" on every interaction, it's probably too prominent for production.

    line 87
  4. Very specific:

    Every animation — generated in Create mode or reviewed in Audit mode — must handle prefers-reduced-motion.

    line 91

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.


Select the requested mode

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")Infer from active context; otherwise begin read-only review

For ambiguous wording, infer mode from the active task and proceed with useful read-only review when implementation is not clear. Ask only if the requested deliverable remains materially unresolved. Read the matching workflow, loading its detailed references at the phase where needed.


Public Reference Lenses

  • Emil Kowalski — 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 lenses are this skill's interpretation of publicly available work, including courses, articles, talks, and open-source projects. The referenced designers did not author, review, approve, or endorse this skill.

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 dashboardEmilJakubJhey (empty states)
Mobile appJakubEmilJhey (delighters)
E-commerceJakubEmilJhey (product showcase)

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)Immediate or minimal feedback; retain useful brief motion without delay
Keyboard-initiatedImmediate response, stable focus; brief preference-respecting feedback if useful

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-drivenLoad the sections for the selected effect; audit only for concrete repair recommendations
Creation GotchasCommon implementation failure modes when writing motionCreate mode; apply relevant checks
Audit ChecklistSystematic audit checklistAudit mode; inspect applicable categories
Anti-ChecklistQuality gate — AI-generated motion anti-pattern categories and motion issues to flagAudit mode; inspect applicable categories
Emil KowalskiRestraint philosophy, frequency rule, decision frameworksEither 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 — inline default + optional rich HTMLOptional rich audit output
Demo ShellVisual container template for per-finding demo cards in the HTML reportAudit mode, HTML output

Workflow Index

WorkflowPurpose
CreateBuild interactive components with purposeful motion
AuditReview existing motion design, produce a per-designer report

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.