More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Frontend Motion Designer

    1

    Nobody cut anything, because cutting requires a framework the prompt doesn't have.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Frontend Motion Designer

    Frontend Motion Designer

    Example session with this skill installed

    My SaaS landing page feels dead — static hero, pricing cards that just sit there, and buttons with no feedback. Add motion that makes it feel alive without turning it into a gimmick. Dark theme, product is "Pulseboard" analytics.

    • Read your context and instructions
    • Compiled the frontend motion designer

    Verdict: Shippable motion system in one pass — 3 of 7 proposed animations were cut by the audit gate; the remaining 4 ship as tokens + ready-to-paste CSS with reduced-motion coverage.

    Motion audit

    ProposalAnswers which question?Verdict
    Hero staggered entranceWhere did this come from✅ Keep — 40ms stagger, ease-out, from scale(.98)
    Button press feedbackWhat just happened✅ Keep — scale(.97) at 100ms, release slower
    Pricing card hover liftWhat should I look at✅ Keep — -3px translateY, real pointers only
    Scroll reveals on cardsWhat's related✅ Keep — CSS view() timeline, linear, no JS listeners
    Logo spinning loopNone❌ Cut — decoration
    Parallax background blobsNone (+mobile jank)❌ Cut
    Full-page entrance choreographyNone (marketing ≠ 800ms product)❌ Cut — hero stagger covers it

    Paste-ready tokens(核心交付)

    :root {
      --dur-micro:150ms; --dur-small:250ms; --dur-medium:350ms; --dur-large:500ms;
      --dur-enter:var(--dur-small); --dur-exit:180ms; /* exits 30% faster */
      --ease-out:cubic-bezier(0.16,1,0.3,1); --ease-in:cubic-bezier(0.4,0,1,1);
      --stagger-step:40ms; /* total capped at 600ms */
    }
    @media (prefers-reduced-motion: reduce) {
      *,*::before,*::after { animation-duration:0.01ms!important; transition-duration:0.01ms!important; }
    }
    

    QA pass results

    CheckResult
    Rapid-click interruptibility✅ Transitions retarget, no queue
    GPU-only properties✅ transform/opacity only, no will-change left in
    No scale(0) entries✅ from scale(.96–.98)
    Reduced-motion fallback✅ Global layer shipped
    JS scroll listeners✅ Zero — animation-timeline: view()

    Prioritized fixes

    1. Replace any transition: all with explicit property lists (jank incubator)
    2. Gate :hover transforms behind @media (hover: hover) for touch devices
    3. Overlay fades at 150ms — faster than the panel it carries

    Honesty footer: scroll-driven output verified in Chromium-grade headless Edge at 1440×900; Firefox pre-144 needs the shipped static fallback. Dashboard figures are placeholders, not real product data.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem You ask for "some animations" on your site and get the confetti treatment: everything fades in over one second at the same 400ms, tooltips pop from scale(0), the logo spins forever, buttons ignore your clicks until the transition finishes, and a JavaScript scroll listener per section fights the main thread into jank. Nobody cut anything, because cutting requires a framework the prompt doesn't have. And there's zero prefers-reduced-motion support — which isn't a style choice, it's an accessibility bug. What it does

    • Motion Audit gate — every proposed animation must answer "where did this come from / what just happened / what should I look at / what's related", or it gets cut and reported; cutting is a deliverable
    • Motion Token system — durations scaled to element size (micro 100–200ms → pages 300–800ms), custom Bézier easing per motion type, stagger at 30–60ms capped at 600ms, shipped as one copy-paste :root block
    • Pattern cookbook — entrances, press feedback, tooltips, modals, drawers, toasts, FLIP layout animations, and pure-CSS scroll-driven reveals, each GPU-safe and origin-aware
    • Engineering QA pass — rapid-click interruptibility, transform/opacity-only properties, FLIP measurement traps, View Transitions promise handling, zero JS scroll listeners
    • Accessibility layer — prefers-reduced-motion fallback on every moving pattern, keyboard-initiated actions never animated, motion never used as the only announcement Why this beats prompting it yourself Ask a generic agent to "add animations" and it will reply with animation: fadeIn 1s ease sprinkled on everything — because it has no decision framework for when NOT to animate. It puts exits at the same speed as entrances (the single biggest "feels sluggish" cause), pops tooltips from scale(0), animates width and box-shadow (layout thrash), writes keyframes for rapidly re-triggered UI so every fast click queues a new animation instead of blending, and never ships a reduced-motion layer. This skill gates every animation through the four-question audit, enforces the duration/easing ruler with tokens instead of magic numbers, and runs the rapid-click and reduced-motion QA pass that catches failures you feel but never see in code review. Use cases
    • Landing page or portfolio that needs scroll reveals, hero entrance, and hover states without feeling like a slideshow
    • SaaS dashboard where modals, toasts, and list reorders currently snap or jank
    • E-commerce flows: add-to-cart feedback, cart drawer, gallery transitions that never block clicking
    • Audit of an existing animated site: cut the noise, fix the jank, add the missing reduced-motion layer Known limitations
    • Ships vanilla CSS + WAAPI (framework-agnostic). It does not write React/Framer Motion components unless you explicitly ask, and won't manage your bundler or animation pipeline tooling
    • DOM and CSS motion only — no Lottie/After Effects exports, no canvas/WebGL, no video or 3D
    • Brand judgments (playful vs professional) run on stated defaults; declare your personality upfront for tuned results
    • Scroll-driven CSS animations need current Chromium/Safari; Firefox before v144 gets the shipped static fallback, not pixel parity

    DOM and CSS motion only. No Lottie or 3D exports. Scroll-driven CSS features require modern browsers. Requires explicit request for specific framework syntax like Framer Motion.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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 3 days ago

    Permissions

    Write Files
    Read Files
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    This skill replaces generic, sluggish animations with a systematic framework that prioritizes functional utility, GPU performance, and accessibility over simple visual decoration.

    The skill generates framework-agnostic vanilla CSS, Web Animation API (WAAPI) blocks, and CSS variables that can be easily integrated into React, Vue, Svelte, or plain HTML/CSS projects.

    No, this skill is purpose-built for DOM-based web motion; it focuses on CSS and WAAPI and does not support Lottie, 3D rendering engines, or video file exports.

    The skill automatically generates 'prefers-reduced-motion' media queries for all patterns, ensuring your site remains usable and compliant for users with motion sensitivities.

    You receive a comprehensive motion audit, a library of custom duration and easing tokens, production-ready code blocks, and a QA checklist for testing interruptibility and performance.

    The skill prioritizes 'cut-first' auditing and uses only GPU-accelerated properties like transform and opacity to ensure smooth 60fps performance without causing layout thrashing.

    New in Frontend & Web Apps