frontend-motion

Generates a motion.json spec selecting animation libraries, scroll triggers, and key animations from a design brief.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill frontend-motion-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-motion
Source: https://github.com/jokerman89/lintel/tree/main/skills/frontend-motion
Command: npx skills add https://github.com/jokerman89/lintel --skill frontend-motion-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing and configuring frontend animation libraries (GSAP, Lenis, Theatre.js, Rive, Motion One, Framer Motion) for a page or feature is time-consuming and inconsistent across a team. This Skill turns a written design brief into a validated motion.json specification covering library picks, scroll-trigger configuration, smooth-scroll settings, key animations, and performance budgets. ## Core Features & Use Cases - Motion language selection: Picks the right animation stack (GSAP + ScrollTrigger, Lenis smooth scroll, Theatre.js timelines, Rive state animation, Motion One, Framer Motion, or CSS-only) based on the brief's energy level and target device. - Structured motion.json output: Produces a schema-validated JSON spec with library install instructions, scroll-trigger config, key animation specs, and a performance budget including prefers-reduced-motion fallbacks. - License awareness: Flags commercial-license tiers (e.g., GSAP Club plugins) and can route through a compliance gate before customer sharing. - Use Case: Given a brief like "feature page for a hardware product with kinetic scroll choreography", the Skill returns a motion.json specifying GSAP + Lenis, scrub-tied hero reveals, parallax sections, and npm install instructions. ## Quick Start Ask the agent to generate a motion specification for your page by providing a brief, for example: create a motion plan for a hardware product landing page with kinetic scroll-driven animation targeting both desktop and mobile.

Frequently Asked Questions about frontend-motion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between GSAP, Lenis, and Motion One for scroll animations?▼

GSAP with ScrollTrigger suits kinetic scroll-choreographed reveals and scrub-tied keyframes, Lenis provides a smooth-scroll baseline often paired with GSAP, and Motion One is a lightweight WAAPI wrapper for subtle-energy briefs. The Skill picks based on your brief's energy level and target device.

How do I generate a motion specification from a design brief?▼

Provide a brief describing the page and desired energy level (subtle, moderate, or kinetic). The Skill queries the design corpus, dispatches a motion-director agent, and emits a schema-validated motion.json with libraries, scroll-trigger config, key animations, and a performance budget.

Does GSAP require a commercial license for scroll animations?▼

Core GSAP and ScrollTrigger are free, but Club GreenSock plugins like SplitText and MorphSVG require a commercial license. The Skill flags commercial-tier picks as DONE_WITH_CONCERNS and can run a compliance-gate license check before customer sharing.

Does the motion spec support prefers-reduced-motion accessibility?▼

Yes, the perf_budget section requires a fallback_for_prefers_reduced_motion field, typically disabling all scroll animations. The reduced-motion floor cannot be overridden by the brief's energy level.

When should I not use a motion library for frontend animation?▼

Skip motion libraries for static pages without scroll-driven interaction and for simple CSS-only transitions like button hovers or modal slide-ins. Performance troubleshooting of existing animations is profiling work, not motion direction.