Skip to main content
← Skills
Skill · Code repo

Turn Product Actions into Smooth Demo Animations

Show how your product works with a smooth cursor demo. Stageshow builds simplified product interfaces in React, with coordinated typing, clicks and feedback, plus still illustrations and feature-card grids for your website.

@benjitaylor Stageshow
  • UI animation
  • Web design
  • Code animation
  • CSS

Works with Claude Code · Codex

Requirements

  • Node.js >= 22.20
  • React >= 18

Overview

What you get

  • A product illustration or scripted operation demo built with React and CSS.
  • A portable component kit, examples and a local viewer for adapting the interface, cursor and scene state.
  • Frame-capture and inspection scripts for checking desktop, phone and key states.

Good fit

  • Showing a short product operation in a website hero or feature card.
  • Creating still product illustrations and feature sections composed of cards in different sizes.

Tutorial

See what makes an operation demo work

A product page often needs to show what happens after someone enters a value or clicks a button. Asking AI to build this can produce heavy cards, abrupt state changes, or a cursor whose actions do not match the feedback.

Stageshow brings composition, cursor movement and scene state into one workflow. Start from an example, adapt it to your product, then inspect the frames. The result is a React animation you can embed in a page. You can also make still illustrations or a feature section composed of cards in different sizes.

Watch the second video above, the before-and-after comparison. Follow the cursor as text appears, the password-strength feedback as input changes, and the result after the button is pressed. Simplification should make the action and its outcome clear, rather than emptying the interface.

Clicks and typing here are scripted illustrations. They change the scene; they do not register an account or operate your application.

Choose the right approach

  • Stageshow: product illustrations and cursor demos for a hero or feature card, focused on one operation and your product’s visual identity.
  • Emil’s interface skills: motion, mobile interactions and edge cases in interfaces people actually use.
  • Product shot recipes: a product film delivered as an MP4 and an editable Remotion project.

Install the skill and explore an example

Installation and preview

  1. Prepare Node.js 22.20 or later. Run the official installation command in your computer’s terminal and choose your coding agent when prompted:

    npx skills add benjitaylor/skills --skill stageshow

    The skill includes design guidance, React components, examples and checking scripts. Keep these companion files; copying only SKILL.md leaves out the material used during production.

  2. To explore the examples, take a separate copy of the repository and start its preview from your terminal:

    git clone https://github.com/benjitaylor/skills.git stageshow-examples
    cd stageshow-examples/stageshow
    npm install
    npm run dev

    On macOS and Linux, open http://stageshow.localhost:1355. On Windows, open the local address printed in the terminal, normally http://127.0.0.1:5173. This is your preview and practice directory, separate from wherever the installer saved the skill.

  3. Find form-error in the viewer. Watch the email being entered, rejected, corrected and submitted. Try Pause, Replay, slow playback and frame stepping, then use Phone to see the narrow layout.

    A complete sequence that pauses and resumes confirms the preview is running. This bundled example teaches form feedback; you do not need to reproduce every detail of the comparison video.

Adapt the example to your product

Prepare your product name, a screenshot or design, brand colors and one operation to demonstrate. Choose a single outcome, such as correcting an email address and completing registration, before attempting an entire product journey.

The following practice request was prepared by this site. Open the cloned repository in your coding agent, attach your screenshot, replace the bracketed fields, and send:

Use stageshow to build a registration demo for [product name], for a feature section on its website.

Use the attached interface and brand colors as references. First explain which product details you will preserve, the sequence of actions, and what the viewer will see at the end. Wait for approval before coding.

Copy stageshow/examples/form-error as a starting point and leave the original example intact. Build in the same viewer first, then prepare it for my own React website.

Sequence: type an email without its domain ending → show the email error → complete the email → click Create → show completion on the button.
Use real words where they matter to the current action and simplify the surrounding content. Move the cursor onto each control before clicking. Feedback should follow the action that causes it. Clearing the error must not make nearby content jump.

Design desktop and narrow phone layouts separately, keeping the text readable. For reduced motion, show a still that communicates the completed result on its own.

Give me a first preview URL and key frames. Wait for my feedback before polishing it.

Open the preview and check cause and effect: an incomplete email produces the error, correcting it clears the error, and completion appears after the click. Compilation alone cannot verify the animation.

Make one focused change

If the sequence moves too quickly, describe the step to adjust and how later actions should follow it. For example:

The email error disappears before the viewer can read it.
Give that message about 0.8 seconds more reading time before completing the email, and shift the following actions accordingly.
Keep the interface, wording and other steps. Show this section at normal speed and in slow playback first.

Inspect the error arriving, holding and clearing. You changed reading time, so the cursor and later states should shift with it; delaying one text label is not enough.

Check the animation and embed it in your page

  1. Run the official checks from stageshow-examples/stageshow:

    npm run typecheck
    npm run check:css
  2. Capture inspection images with your installed Chrome. These commands use the official form-error example. Replace the URL with the preview you are running. After adapting the example, replace form-error in capture=form-error with your new example name. Set CHROME_PATH if Chrome is not installed in its default location.

    node scripts/film.mjs "http://stageshow.localhost:1355/?capture=form-error" --gate --out shots/form-wide.png
    node scripts/film.mjs "http://stageshow.localhost:1355/?capture=form-error" --width 390 --gate --out shots/form-phone.png
    node scripts/film.mjs "http://stageshow.localhost:1355/?capture=form-error" --states --gate --out shots/form-states.png

    ?capture= opens the example directly for capture. These commands produce PNG inspection images, not MP4 files. When blocking checks are clear, the script ends with rehearsal passed. Still watch the sequence at normal speed to check cursor placement, overlays and the end of the sequence.

  3. Once you approve the first version, ask your agent to move the new component, its assets and kit/ into your React 18 or later project, fix the imports, and install the dependencies it actually uses, such as lucide-react. Check desktop and phone layouts again in the destination page, beyond the standalone viewer.

Use this outline for a different scene:

Use stageshow to make a [still illustration / operation demo / feature-card grid] for [product name].
Placement: [page section], available widths [desktop / phone], background [color].
References: [screenshots, design, brand colors].
The viewer should understand: [the core feature; for an animation, name the action and its outcome].
Sequence (for animations only): [three to five actions].
Preserve: [recognizable product details and key text].
Playback (for animations only): [loop / once in view / on hover].
Propose the composition first; for an animation, include the sequence. After approval, build a first version and inspect key images before refining it.

Project source is MIT licensed. Third-party app icons and brand artwork have their own sources and terms in NOTICE.md; use your own product assets when adapting the examples.