agentleFS
podopodo/design-agent-skills/skills/fixing-motion-performance/SKILL.md

fixing-motion-performance

Skill32 starsChanged 6 months agoMITView on GitHub

Audits and fixes animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Guides developers to smooth, GPU-accelerated animations that avoid jank.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ui-skills-root, improve-ui and 2 more.

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.
  • Discriminative-shoji607Skill

    ui-skills-root

    Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.

    Also in 3 projects that use this

  • Discriminative-shoji607Skill

    improve-ui

    Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.

    Also in 3 projects that use this

  • VercelSkill

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Also in 3 projects that use this

  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 3 projects that use this

The file

Files
SKILL.md

fixing-motion-performance

Catalogue stub — full skill: ibelick/ui-skills

<!-- 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/fixing-motion-performance/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/fixing-motion-performance/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as fixing-motion-performance, invoke it and proceed
    • pointer → go to step 2
  2. Detect scope, then install:

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

    Global:

    npx skills add ibelick/ui-skills --skill fixing-motion-performance -g -y

    Project:

    npx skills add ibelick/ui-skills --skill fixing-motion-performance -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: fixing-motion-performance
  • Trigger phrases: "motion performance", "animation performance", "layout thrashing", "compositor properties"

What it does

Audits animations for layout thrashing, incorrect compositor property usage, scroll-linked motion anti-patterns, and expensive blur effects. Provides concrete fixes to move animations onto the GPU and eliminate frame drops for smooth, production-grade motion.

When NOT to use

  • Choosing easing, timing, or motion design principles (not performance) → use design-motion-principles
  • Library-specific GSAP work (ScrollTrigger, timelines, useGSAP) → use gsap-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.