agentleFS
neeraj181-dotneeraj181-dot/ClaudeSkills/.claude/skills/motion-designer/SKILL.md

motion-designer

Skill0 starsChanged 3 months agoApache-2.0View on GitHub

Add professional, purposeful animation and interaction design to an EXISTING website — motion that makes the UI feel responsive, polished, and intentional, not animated everywhere. Establishes a coherent motion system (timing/easing), improves interactions/micro-interactions/loading/page transitions, respects prefers-reduced-motion, keeps animations performant (transform/opacity), preserves all existing functionality, and verifies by running the app. Works with React, Next.js, Vite, HTML/CSS/JS, Django templates, and similar web apps. Use when the user wants to add or improve animations, transitions, interactions, or micro-interactions / make a UI feel more polished. Distinct from ui-redesign (visual layout/type/color) — this is motion.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use awwwards-animations, explainer-video-guide and 7 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.
  • wendymardigian-progSkill

    awwwards-animations

    Professional React animation skill for creating Awwwards/FWA-level animations using GSAP (useGSAP), Motion (Framer Motion), Anime.js, and Lenis. Use when building premium scroll experiences, custom cursors, page transitions, text animations, parallax effects, micro-interactions, or any animation that needs to be 60fps and award-worthy. Triggers on requests for smooth scroll, ScrollTrigger, magnetic effects, reveal animations, horizontal scroll, pin sections, stagger effects, useScroll, useTransform, integration with Three.js/WebGL, algorithmic art, mathematical art, generative art, fractals, L-systems, flow fields, strange attractors, sacred geometry, geometric puzzles, Dudeney dissections, tangram, tessellations, Penrose tiles, kinetic typography, glitch effects, text explosion, morphing text, circular text, brutalist design, minimalist animation, neo-brutalism, or design philosophy mixing. React-first approach with proper cleanup and hooks.

    Also in 3 projects that use this

  • wendymardigian-progSkill

    explainer-video-guide

    Explainer video production guide: scripting, voiceover, visuals, and assembly. Covers script formulas, pacing rules, scene planning, and multi-tool pipelines. Use for: product demos, how-it-works videos, onboarding videos, social explainers. Triggers: explainer video, how to make explainer, product video, demo video, video production, video script, animated explainer, product demo video, tutorial video, onboarding video, walkthrough video, video pipeline

    Also in 3 projects that use this

  • brainbytes-devSkill

    brand-architecture

    Design brand architecture for multi-product or multi-brand organizations. Use when managing brand portfolios or launching sub-brands.

    Also in 3 projects that use this

  • freshtechbroSkill

    animated-component-libraries

    Pre-built animated React component collections combining Magic UI (150+ TypeScript/Tailwind/Motion components) and React Bits (90+ minimal-dependency animated components). Use this skill when building landing pages, marketing sites, dashboards, or interactive UIs requiring pre-made animated components instead of hand-crafting animations. Triggers on tasks involving animated UI components, Magic UI, React Bits, shadcn/ui integration, Tailwind CSS components, or component library selection. Alternative to manually implementing animations with Framer Motion or GSAP.

    Also in 3 projects that use this

  • david33137Skill

    logo-design

    Logo design with 55 styles, 30 color palettes, 25 industries. Generate logos with Gemini Nano Banana model. Actions: design, create, generate logo.

    Also in 3 projects that use this

  • JetBrainsSkill

    modern-web-guidance

    Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add professional, purposeful animation and interaction design to an existing website.

    line 9
  2. Distinctive:

    Core principle: animation must have a purpose: Every animation must improve at least one of: user feedback · navigation · hierarchy · …

    line 11
  3. Distinctive:

    Stay in scope: Only modify the exact project/folder the user specified (see Scope Safety).

    line 16
  4. Distinctive:

    Before changing anything: inspect project structure · framework · current styling system · existing animations/transitions · interactive …

    line 22
  5. Distinctive:

    Use scroll-triggered motion only where it adds meaning — important content revealing as it enters view, large visual sections, product …

    line 52
  6. Distinctive:

    Add subtle feedback for: button clicks · toggles · checkboxes · tabs · dropdowns · copy buttons · save · favorite · upload · progress · …

    line 58
  7. Distinctive:

    Not all motion is equal. Keep it aligned with visual hierarchy:

    line 66
  8. Very specific:

    Only modify the exact project/folder the user specified.

    line 108

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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

Motion Designer

Add professional, purposeful animation and interaction design to an existing website. The goal is not to add animation everywhere — it's to make the interface feel responsive, polished, intentional, and professionally designed.

Core principle: animation must have a purpose. Every animation must improve at least one of: user feedback · navigation · hierarchy · continuity · spatial understanding · perceived performance · delight. If it doesn't improve the experience, don't add it.

This is a motion skill, distinct from ui-redesign (which owns layout, type, and color). Two hard constraints, as in any redesign work:

  1. Preserve behavior. Motion is additive polish — functionality, data, state, routing, forms, auth, and business logic must work exactly as before.
  2. Stay in scope. Only modify the exact project/folder the user specified (see Scope Safety). Never touch sibling projects or global config without explicit permission.

Work through the phases in order. Do not skip inspection to jump to animating.

Phase 1 — Inspect first

Before changing anything: inspect project structure · framework · current styling system · existing animations/transitions · interactive components · pages in scope · reusable components. Do not add animation yet — know what's already there so you extend it rather than duplicate or fight it.

Phase 2 — Understand the interface

Identify the interactions and elements: primary vs secondary interactions · navigation · buttons · forms · cards · modals · dropdowns · tabs · menus · page transitions · loading states · success/error states. Decide where motion genuinely helps — and, just as important, where it doesn't.

Phase 3 — Create a motion system

Establish one coherent motion language, used consistently:

  • Durations: fast / standard / slow (a small fixed set, e.g. ~120ms / ~200ms / ~320ms — adapt to the project).
  • Easing: a standard ease for most moves, plus entrance/exit curves.
  • Named behaviors: entrance · exit · hover · focus · press · modal · page transition.

Use consistent timing and easing — don't invent a random duration for every element. Prefer tokens/variables (CSS custom properties, a config object) so motion stays uniform.

Phase 4 — Interaction animation

  • Buttons — subtle hover, press feedback, focus states, loading states. Avoid exaggerated button animation.
  • Navigation — subtle active-state transitions, menu open/close, indicator movement.
  • Cards — restrained hover elevation, gentle image movement, border/accent transitions. Don't make cards constantly float.
  • Forms — animate focus, validation, error, success, loading. Motion should communicate state, not decorate.
  • Modals — opacity, small movement, scale where appropriate. Avoid dramatic zoom.

Phase 5 — Page animations

Where appropriate: page entrance · section reveals · content transitions · route transitions. Do not animate every section independently, and avoid excessive staggering. A page should feel smooth, not like every element is walking onto a stage.

Phase 6 — Scroll animations

Use scroll-triggered motion only where it adds meaning — important content revealing as it enters view, large visual sections, product demos, meaningful stats.

Avoid: animating every paragraph or card · excessive parallax · long scroll sequences · animation that delays access to content. Content must remain fully usable without animation (and readable if JS/animation never fires).

Phase 7 — Micro-interactions

Add subtle feedback for: button clicks · toggles · checkboxes · tabs · dropdowns · copy buttons · save · favorite · upload · progress · success. Micro-interactions make the interface feel responsive and alive — keep them quick and quiet.

Phase 8 — Loading states

Improve loading with the right device: skeletons · progress indicators · spinners · content placeholders · a smooth transition from loading → loaded. Prefer a skeleton or immediate feedback over a spinner when it better reflects the real layout; avoid unnecessary spinners.

Phase 9 — Motion hierarchy

Not all motion is equal. Keep it aligned with visual hierarchy:

  • Primary motion — important actions and major transitions.
  • Secondary motion — supporting interactions.
  • Tertiary motion — small feedback details.

The most important actions get the most noticeable (still restrained) motion; everything else recedes.

Phase 10 — Performance

Animations must be performant. Prefer transform and opacity (compositor-friendly). Be careful with anything that triggers layout/paint: animating width/height/top/left, large shadows, filters, blur, complex paint. Avoid motion that forces unnecessary layout recalculation or jank. Don't add a heavy animation library when CSS or the project's existing tools suffice.

Phase 11 — Accessibility

Always support prefers-reduced-motion. When reduced motion is requested: reduce movement, remove non-essential transitions, avoid large transforms, but preserve functional state changes and keep all content accessible. Never make essential information depend on animation — a state must be perceivable without motion (and with a visible focus indicator preserved).

Phase 12 — Mobile behavior

Motion must behave across desktop, tablet, mobile. Consider touch interaction, smaller screens, weaker hardware, and that hover doesn't exist on touch devices — so never rely on hover for essential functionality. Provide tap/press feedback where hover would be the cue on desktop.

Phase 13 — Implementation

Actually implement the motion system. Reuse existing animation utilities where possible; avoid unnecessary dependencies — if a library is genuinely warranted, inspect the project first and justify it. Don't rewrite unrelated components.

Preserve throughout: existing functionality · API calls · state · routing · forms · authentication · business logic. Keep the hooks/selectors those depend on intact when you touch their markup.

Phase 14 — Test (actually run it)

After implementing: run the app · check console errors · test interactions, navigation, forms, modals, loading states · test mobile layout · test reduced-motion behavior · check for animation glitches, excessive motion, and performance/jank. If a browser-automation/verify/run skill is available, use it to load the app and observe real behavior. Fix every issue found before reporting.

Phase 15 — Final motion review

Review critically and ask of each animation: "Does this help the user?" If no → remove it.

Hunt specifically for: too many animations · repetitive movement · excessive bouncing · long delays · distracting effects · generic AI-style motion · unnecessary parallax · excessive blur · animation on every card · animation that blocks interaction.

The result should feel smooth, responsive, premium, intentional, fast, human-designed — not flashy, distracting, overanimated, AI-generated, or gimmicky.


Scope Safety

Only modify the exact project/folder the user specified. If the user says D:\website33, only modify D:\website33\*. Never modify sibling projects, global configuration, or another folder without explicit permission. (Pairs with the safe-scope skill.)

Final report

## Animation Added
(the main animations)

## Interaction Improvements
(improved interactions)

## Motion System
(timing/easing decisions)

## Accessibility
(reduced-motion support)

## Performance
(performance considerations)

## Components Changed
(modified/created files, with paths)

## Remaining Issues
(anything unresolved)

Never claim an animation was tested if it wasn't actually tested.


Guardrails, always: animation needs a purpose — if it doesn't help, don't add it; keep motion restrained, consistent, and aligned to visual hierarchy; prefer transform/opacity and keep it performant; always honor prefers-reduced-motion and never gate essential info behind motion; don't rely on hover for essential functionality on touch; reuse before adding dependencies; preserve all existing behavior; only modify the specified project; and never claim something was tested when it wasn't.

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.