How do I install the Motion skill?

Run npx skillmds@latest add tanveer-rajpurohit/motion in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Motion safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Motion?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Motion free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Motion?

Tanveer-rajpurohit (@tanveer-rajpurohit) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Motion by tanveer-rajpurohit — Agent Skill

Name: Motion
Rating: 4.2 (5 reviews)
Author: Tanveer-rajpurohit

Motion

Web animation *craft and taste* — the judgment layer above GSAP mechanics. Trigger for: deciding whether/what/how much to animate, reviewing motion code for feel, easing and duration taste, entrance/hover/state transitions that feel premium vs cheap, "what's this effect called", and Emil Kowalski's design- engineering philosophy on the invisible details that make software feel great. Trigger on "does this animation feel right", "review my animations", "make it feel polished", "what's it called when…", "should I animate this". Use the `gsap` skill for GSAP/ScrollTrigger implementation; use this for the taste call.

File contents

Motion — Animation Craft & Taste (Emil Kowalski)

The judgment layer for motion. gsap covers how to build an animation; this covers whether, what, and how much — the taste that separates premium motion from the uniform-fade reflex. Three sub-skills, each its own SKILL.md:

Sub-skill	Folder	Load when
emil-design-eng	`emil-design-eng/`	Building or refining UI and you want the craft bar: component design, when/what to animate, easing + duration defaults, the invisible details. The philosophy core.
review-animations	`review-animations/`	Reviewing existing animation/motion code against a high craft bar. Defaults to flagging; approval is earned. Pairs with `STANDARDS.md` in that folder.
animation-vocabulary	`animation-vocabulary/`	Naming an effect — "the bouncy thing when a popover opens" → Pop in. Reverse-lookup glossary to get the right word to prompt with. Naming, not building.

How this fits the rest of the library

User wants motion
   ├─ "what should this feel like / is this too much?"   → motion/emil-design-eng
   ├─ "review these animations"                          → motion/review-animations
   ├─ "what's this effect called?"                       → motion/animation-vocabulary
   └─ "build the scroll/timeline/stagger"                → gsap  (implementation)

Rule of thumb: reach here before writing the animation (taste + decision), reach for gsap to write it, come back to review-animations after. For static visual polish (spacing/type/color) use ui-design / impeccable.

Source: https://github.com/emilkowalski/skills — Emil Kowalski (animations.dev).

---name: motiondescription: Web animation *craft and taste* — the judgment layer above GSAP mechanics. Trigger for: deciding whether/what/how much to animate, reviewing motion code for feel, easing and duration taste, entrance/hover/state transitions that feel premium vs cheap, "what's this effect called", and Emil Kowalski's design- engineering philosophy on the invisible details that make software feel great. Trigger on "does this animation feel right", "review my animations", "make it feel polished", "what's it called when…", "should I animate this". Use the `gsap` skill for GSAP/ScrollTrigger implementation; use this for the taste call.---# Motion — Animation Craft & Taste (Emil Kowalski)The judgment layer for motion. `gsap` covers *how to build* an animation; thiscovers *whether, what, and how much* — the taste that separates premium motionfrom the uniform-fade reflex. Three sub-skills, each its own `SKILL.md`:| Sub-skill | Folder | Load when ||---|---|---|| **emil-design-eng** | `emil-design-eng/` | Building or refining UI and you want the craft bar: component design, when/what to animate, easing + duration defaults, the invisible details. The philosophy core. || **review-animations** | `review-animations/` | Reviewing existing animation/motion code against a high craft bar. Defaults to flagging; approval is earned. Pairs with `STANDARDS.md` in that folder. || **animation-vocabulary** | `animation-vocabulary/` | Naming an effect — "the bouncy thing when a popover opens" → *Pop in*. Reverse-lookup glossary to get the right word to prompt with. Naming, not building. |## How this fits the rest of the library```User wants motion ├─ "what should this feel like / is this too much?" → motion/emil-design-eng ├─ "review these animations" → motion/review-animations ├─ "what's this effect called?" → motion/animation-vocabulary └─ "build the scroll/timeline/stagger" → gsap (implementation)```Rule of thumb: reach here **before** writing the animation (taste + decision),reach for `gsap` **to** write it, come back to `review-animations` **after**.For static visual polish (spacing/type/color) use `ui-design` / `impeccable`.Source: https://github.com/emilkowalski/skills — Emil Kowalski (animations.dev).

Frequently asked questions