agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/design-motion-principles/SKILL.md

design-motion-principles

Skill32 starsChanged 6 months agoMITView on GitHub

Motion and interaction design expert with two modes: build interactive components with purposeful motion, or audit existing animations for AI-slop patterns. Audit emits a branded HTML report with looping CSS demos per finding. Based on Emil Kowalski (restraint), Jakub Krehel (production polish), and Jhey Tompkins (creative experimentation), with lenses weighted to project context. Works with React, Framer Motion, CSS, and HTML.

15 other projects use a version of this.

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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    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. Very specific:

    Only Emil Kowalski's single-lens guidance (use emilkowalski-skill)

    line 95

“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

Catalogue stub — full skill: kylezantos/design-motion-principles

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed?
    • Global: f=~/.agents/skills/design-motion-principles/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/design-motion-principles/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as design-motion-principles, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/design-motion-principles ] && echo "global" || echo "project"

    Global:

    npx skills add kylezantos/design-motion-principles --skill design-motion-principles -g -y

    Project:

    npx skills add kylezantos/design-motion-principles --skill design-motion-principles -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Heads-up

  • License: MIT
<!-- das:install:end -->

Invoke after install

  • Skill name: design-motion-principles
  • Trigger phrases: "add animation", "audit animation", "hover state", "enter exit animation", "motion review", "AI slop motion"

The skill detects its mode from your request:

You sayMode
"animate this", "add motion", "make it feel alive"Create
"audit my animations", "review motion", "check for AI slop"Audit
AmbiguousSkill asks which mode

What it does

Two modes, three lenses weighted to project context:

ModeOutput
CreateContext discovery, lens weighting, then a component with motion baked in (React / Framer Motion / CSS / HTML)
AuditMotion-gap analysis plus an anti-AI-slop checklist, delivered as a branded HTML report with auto-looping CSS demos, or --terminal for inline markdown

Three lenses:

  • Emil Kowalski — Restraint and speed. "Should this animate at all?"
  • Jakub Krehel — Production polish. "Is this subtle enough?"
  • Jhey Tompkins — Creative experimentation. "What could this become?"

The productive tension between these three lenses, not one applied universally, is the point. The skill reads its own workflows/ and references/ folders, so it must be installed through the skills CLI rather than by copying SKILL.md alone.

When NOT to use

  • Static layout, color or typography work (use a design-systems skill such as ui-ux-pro-max)
  • Only Emil Kowalski's single-lens guidance (use emilkowalski-skill)
  • Interactive gesture-driven animation requiring JavaScript state (use framer-motion-skills)

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.

Check your setup, free