agentleFS
kabeierkabeier/SPAs-and-Claude/.claude/skills/design-motion-principles/SKILL.md

design-motion-principles

Skill0 starsChanged 33 days agoNo licenceView on GitHub

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.

15 other projects use a version of this, 8 of them edited; 4 of 8 edited versions we compared changed its rules; 1 new project in the last 4 weeks, against 1 the 4 before.

How people change it

4 of 8 edited versions changed its rules, and some changes recur.

Of the 8 edited versions we compared: 4 keep every rule, 4 made changes of their own.

Rules people drop

  1. Before adding or approving any animation, ask how often the user triggers it:dropped by 4 of 4
  2. Do not universally flag or cap durations. Check the context weighting first.dropped by 4 of 4
  3. Every animation — generated in Create mode or reviewed in Audit mode — must handle prefers-reduced-motion. No exceptions. See references/accessibility.md.dropped by 4 of 4

Rules people add

  1. Before auditing any code, understand the project context. Never apply rules blindly.added by 4 of 4
  2. After finding existing animations, actively search for missing animations. These are UI changes that happen without any transition:added by 4 of 4
  3. If NO to both → this is a motion gap that needs fixingadded by 4 of 4
  4. After gathering context, tell the user what you found and propose a weighting:added by 4 of 4
  5. STOP and wait for the user to confirm or adjust. Do not proceed to the full audit until they respond.added by 4 of 4
  6. If they adjust (e.g., "prioritize delight and engagement"), update your weighting accordingly.added by 4 of 4
  7. Read references/emil-kowalski.md if Emil is primary/secondary — Restraint philosophy, frequency rules, Sonner/Vaul patternsadded by 4 of 4
  8. Read references/jakub-krehel.md if Jakub is primary/secondary — Production polish, enter/exit recipes, shadows, optical alignmentadded by 4 of 4

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Steady: 1 new project took it in the last 4 weeks, 1× the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 1 new projectWeek of Oct 18: 0 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 2 in all, so this is a hint, not a trend.

Most recently taken up by

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 12 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.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 12 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.

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.