agentleFS
Sign inStart free
jhy0285jhy0285/monofield/skills/emilkowalski-motion/SKILL.md

emilkowalski-motion

Skill6 starsChanged 5 months agoApache-2.0View on GitHub

Motion-design follow-up skill inspired by Emil Kowalski's animation guidance. Use after an interface exists to add tasteful micro-interactions, state transitions, and page motion with product-grade restraint.

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill after a design artifact already exists.

    line 32
  2. Very specific:

    Prefer transform and opacity.

    line 42
  3. Distinctive:

    Use one motion language across the artifact.

    line 43
  4. Very specific:

    Add prefers-reduced-motion fallbacks for any automatic or scroll-linked motion.

    line 44
  5. Distinctive:

    Keep copy, data, and layout intent intact unless the user explicitly asks for a redesign.

    line 45
  6. Distinctive:

    Default UI transitions should feel quick and useful: 140-220ms for most controls.

    line 49
  7. Distinctive:

    Avoid endless decorative loops unless they communicate status or progress.

    line 51
  8. Distinctive:

    Do not add custom cursors, noisy particle effects, or motion that competes with content.

    line 52
  9. Very specific:

    If GSAP is available and the motion needs sequencing, pair this with gsap-core, gsap-timeline, or gsap-scrolltrigger.

    line 59
  10. Distinctive:

    Always clean up observers, timers, and animation instances.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

Emil Kowalski Motion Follow-Up

Use this skill after a design artifact already exists. The goal is to make the interface feel alive without turning it into a motion demo.

Workflow

  1. Inspect the current HTML, component, or selected page element before adding animation.
  2. Pick the smallest set of motion moments that clarify state or hierarchy:
    • entry reveal for the primary content
    • hover / active feedback for important controls
    • transition between UI states
    • scroll reveal only when it helps the story
  3. Prefer transform and opacity. Avoid animating layout properties such as top, left, width, or height.
  4. Use one motion language across the artifact. Do not mix unrelated easings, durations, or physics.
  5. Add prefers-reduced-motion fallbacks for any automatic or scroll-linked motion.
  6. Keep copy, data, and layout intent intact unless the user explicitly asks for a redesign.

Motion Rules

  • Default UI transitions should feel quick and useful: 140-220ms for most controls.
  • Larger page reveals can be slower, but must not block reading.
  • Avoid endless decorative loops unless they communicate status or progress.
  • Do not add custom cursors, noisy particle effects, or motion that competes with content.
  • Stagger only small groups. Long staggered lists make interfaces feel slow.

Implementation Notes

  • For plain HTML, CSS keyframes and small JavaScript observers are enough.
  • For React or framework code, use the local stack already present in the repo.
  • If GSAP is available and the motion needs sequencing, pair this with gsap-core, gsap-timeline, or gsap-scrolltrigger.
  • Always clean up observers, timers, and animation instances.

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