- Home
- Skills
- Frontend & Web Apps
- Motion Animations: Next.js and React Motion
More screenshots
Works with the AI Agents you already use
Motion Animations: Next.js and React Motion
Choreograph React and Next.js motion with intent: a shared easing/duration token system, the four motion jobs, gesture and scroll patterns, reduced-motion support, and a frame budget.
$5
Motion Animations: Next.js and React Motion
Example session with this skill installed
Our Next.js marketing site has animations everywhere but it feels chaotic — every section eases differently, the hero elements all fly in at once, and nobody has checked reduced motion. Give me a system and choreograph the hero properly.
- Read your context and instructions
- Compiled the motion animations
MOTION SYSTEM + HERO CHOREOGRAPHY — produced by applying the skill.
The system, defined once and referenced everywhere: eases — out [0.22, 1, 0.36, 1] for entrances, a snap curve for micro-interactions, linear reserved for progress only. Durations — 150ms micro, 300ms standard, 500ms hero-only. Distances — 4/12/24px paired with fades. Stagger — 60ms steps, capped at about 8 children. Gesture spring — stiffness 320, damping 30. Every existing one-off curve in components is a review finding to migrate onto these tokens; that migration, not any single animation, is what makes the site stop feeling chaotic.
Job audit of the current hero: the floating decorative shapes have no job — they communicate nothing about origin, change, or importance — so they are cut, on paper, free. The headline, subcopy, CTAs, and product visual are all entrance. The CTA hover lift is emphasis and stays, because it reverses cleanly.
Choreography, sequenced by information priority instead of everything at once: headline fades up first (the message, 300ms standard ease, 12px rise), then subcopy at +60ms, then the CTAs as a pair at +120ms, then the product visual last with a slightly longer 450ms ease — the payoff. Total choreography: under 1.2 seconds. Nothing below the fold animates on load; the feature grid uses whileInView with once: true and a 3-item stagger cap, and the metrics band gets a scroll progress bar instead of per-number animation.
Reduced motion, built as part of the deliverable: a single useReducedMotion check at the system level. With it on, every hero element renders instantly in final position — same information, zero travel — and no signal on the page is carried by motion alone.
Frame budget: only transform and opacity are animated anywhere in the plan, so motion stays on the compositor thread. Concurrent animated elements stay in single digits.
Rubric score for the plan: job clarity 2, system consistency 2 (after token migration), sequencing 2, gesture 2 (no gesture elements on this surface), reduced motion 2, frame budget 1 — verified with CPU throttling, not yet on a real mid-range Android. 11/12: ship, with the on-device check scheduled rather than skipped.
Connects securely to your tools. The creator never sees your data.
About this skill
Most interface animation feels off for one reason: every component invented its own easing, duration, and distance, so the product moves like five different products. This skill fixes that by building the motion system before touching a component — a token set with two or three easing curves (a standard ease-out for entrances, a snap for micro-interactions, linear reserved for progress), a 150/250–350/500ms duration scale, and distance discipline (small elements travel 8–16px, not 200). Every animation then gets organized by job, not by component: entrance ("here I am"), emphasis ("look at this," and always reversible), transition ("this became that" — if the eye has to re-find the element, it failed), and gesture ("you're driving" — springs fed by release velocity, never timed easings on anything a finger controls). Scroll behavior is covered without the jank: animate on view once, parallax as seasoning at 0.2–0.5x, transform and opacity only, because layout properties on scroll are a jank guarantee. Accessibility is part of the deliverable, not a pass at the end: a global prefers-reduced-motion state where changes happen instantly with the same information, and no essential signal carried by motion alone. The engineering guardrails name the bugs that actually bite — hydration mismatches from browser-only state, exits that need presence tracking, index keys sliding elements to wrong positions, shadows clipped by overflow. A token template, a seven-step choreography protocol, and a six-line review rubric (ship at 10+ of 12, zero on job clarity or reduced motion blocks) make it repeatable, and the worked example choreographs a landing hero in priority order under 1.2 seconds.
- Examples target React/Next.js with Motion; the method transfers to Vue, Svelte, or vanilla CSS, but the presence-tracking, hydration, and key guidance is written for React's rendering model.
- Frame-budget figures (60fps, ~10 concurrent animations on a mid-range phone) are planning heuristics — your target devices set the real budget, and the skill's gate requires an on-device check for that reason.
- It covers UI motion choreography, not video editing, motion graphics authoring, or brand animation systems for broadcast.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
No special permissions declared or detected