645 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
83386
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
npx skills add https://github.com/nexu-io/open-design --skill emilkowalski-motionCopy
The instruction itself
4 sections, as written by the author
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
Inspect the current HTML, component, or selected page element before adding animation.
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
Prefer transform and opacity. Avoid animating layout properties such as top, left, width, or height.
Use one motion language across the artifact. Do not mix unrelated easings, durations, or physics.
Add prefers-reduced-motion fallbacks for any automatic or scroll-linked motion.
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.