设计与多媒体

emilkowalski-motion

nexu-io/open-design

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.

  • 2325 次安装
  • 10.5万 星标
  • 收录于

安装命令

npx skills add https://github.com/nexu-io/open-design --skill emilkowalski-motion

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