stageshow
Build faux product UI that looks like a real product, as a still illustration or an animated demo with a cursor. Browser and app windows, dashboards, phones, notifications, terminals, bento grids and cursor walkthroughs, framed, masked and cropped the way a marketing page, feature card or docs hero…
Install / Use
npx skills add benjitaylor/skills --skill stageshowInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
CommunicationSupported Platforms
Tags
Our assessment of stageshow
stageshow scores 87/100 on our quality scale, 254th of 397 Communication skills we index.
Its SKILL.md is 19 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 3,248 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 12 days ago, so stageshow is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
stageshow compared with similar skills
All 4 of these similar skills score higher than stageshow; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| stageshow (this skill)by benjitaylor | 87 | 3.2k | 12d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install stageshow?
- Run
npx skills add benjitaylor/skills --skill stageshow. The install tabs above show the steps for each supported agent. - Which AI agents does stageshow work with?
- It is written for Cursor, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is stageshow safe to use?
- It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is stageshow still maintained?
- The repository was last updated 12 days ago, so stageshow is actively maintained.
Skill content
View source on GitHubname: stageshow description: Build faux product UI that looks like a real product, as a still illustration or an animated demo with a cursor. Browser and app windows, dashboards, phones, notifications, terminals, bento grids and cursor walkthroughs, framed, masked and cropped the way a marketing page, feature card or docs hero needs them. Use whenever someone wants a fake or mocked UI, a product demo or walkthrough animation, a hero or feature-card illustration of an app, a product shot in the style of a polished marketing site, or an animated cursor doing things in an interface, even if they never say "faux UI". React and plain CSS. metadata: version: 1.1.1
Stageshow
Miniature product UI: a believable interface, framed in its space, as one still or a short animation in which one thing happens. The viewer recognizes the screen and sees the thing happen.
The one idea
It reads as a real product, simplified to what the viewer needs, framed with intent, and every motion has a cause.
Five ways it fails:
- Too much. Real text in every row, numbers everywhere, everything packed. The more detail, the more it looks generated.
- Wireframe. Two gray blobs and a button. Built too small, or stripped of what made it recognizable.
- Boxed. A whole window shrunk into a card with even margins: a screenshot pasted in, not a product shot.
- Flat. Every object the same weight in the same bordered card. The eye has nowhere to land.
- Bland. A gray window with a cursor, whatever the brief said. The brief's look and energy (a blueprint, glass over color, a Dynamic Island, a mascot) are the point; take what it asks for and build it to the rules, as
examples/hero-demodoes with its typed popup and terminal satellite (a satellite is a smaller second object, a receipt, phone or detail card, straddling the hero's edge).
The fix: a full, structured screen in quiet grays, real words only on what the story is about, placeholder lines for the rest, room to breathe, a crop that puts the eye where the story is. Simplify the words, not the context. An empty corner, a void under a list, rows spread to fill a pane, a window floating on a plate (a backdrop or tinted field behind it): unfinished, not calm.
These are authored illustrations, not browser automation: a.click() draws the cursor pressing, a.set() changes the scene.
How hard to press
Build it the way a product designer builds a launch page they will be judged on. The gold examples in examples/ are the bar, not a reference: if yours is the emptier, flatter or smaller one beside the closest gold, that is the first fix. Then look at the frame the way the most exacting designer you know would, the one who screenshots the one wrong thing and sends it back with "what is this?": a dot off its avatar, a unit on its own line, a grabber under the island, copy touching a card. If you can picture that screenshot, you have found the next fix.
Workflow
Most of the quality is decided before any code. Write the plan first: where it sits, the focal object, the action, the payoff, what can be left out.
- Medium and place. Still or animation (loop, once in view, or hover). The page, its ground, its width. Design at the size it will be seen, about 720 × 340 for a hero beside copy (
hero-demo), 900 to 1100 wide for a full-width hero (linear), 400 × 300 for a card, shown at 1:1; never under about 320 wide for a demo, though a bento tile or a satellite card may be smaller. Every demo that can sit in a phone column ships acompactdesign at the column's width (358), a redesign not a squeeze (references/framing.md, Small formats and the page). A grid of tiles is one set: plan it withreferences/bento.md. - Look. With the product's code or site at hand, map its tokens to the kit's (
references/looks.md); if the developer asks for their own components, use them inside the stage instead of the kit's small parts. Otherwise a theme (light, dark, blueprint, glass), a palette (accent, mono) and a fidelity:minimalis all bars,standardis words where they carry meaning and bars elsewhere,realisticis real content everywhere. Default light, accent, standard; go realistic at hero scale, for a named real product, or a still whose subject is a list or page. Write filler once withText fillerand the fidelity decides. The product's own icons, its real chrome, the content that makes it recognizable. A brief with a style (kawaii, paper, a poster color) gets that style in full, still built to these rules. - The story. Its shape (
references/motion.md, Story): how it feels to use, a flow, or what the system does. Three to five beats and a payoff, 10 to 16 seconds. No cursor move you can't explain. Data never rewinds in view without a cause. Between a richer story and a calmer frame, choose the frame. - Start from an example. Find the closest gold example (the Gold table below) and film it (
node scripts/film.mjs "<preview>/?capture=<gold>" --select '#example' --still --out gold.png;npm run devserves the preview). Copy its folder into your project as the starting point; don't rewrite it from a glance. The quickest loop: copy it toexamples/<yours>/here, where the preview picks it up and?capture=<yours>films it, then move it into the host when it passes and fix its kit import path. Keep its structure: the stage size, the crop and bleed, row and type sizes, spacing, the script's beats, the kit parts. Now readreferences/craft.mdin full: it is short, and it holds the still-frame rules the gold can't show you, the cases your gold doesn't happen to contain. Then replace its look and content with the brief's product: the tokens from step 2, the product's own icons, chrome and words. A copy that only changes the name is not done: it should read as the brief's product, not the gold's. If no gold tells your story, choose in two parts: the layout first (pick it from the table inreferences/framing.md; each layout names its example), and copy that example even though its story differs; then borrow the motion for your beats from the example whose story is closest, and build what neither has in the same style. Then frame it: crop to the panel the story happens in, judged in the final visible crop (references/framing.mdhas the rules and the layout table). The short form: one gutter, a full one or well past; only filler bleeds; what opens stays in; windows keep their shape; the page is the ground, so no plate under a hero on a white or dark page and no window whole with air on four sides;unframedonly when the developer asks; no dead corners. Film one still at both widths beside the gold's; if yours is emptier, flatter or more boxed, fix the frame before any motion. - The screen. Count the real strings, usually 3 to 7 (
references/craft.md, Restraint): a budget for words, not elements. Build with the kit's tokens,Bar,TextandRow. Fit every control's text before it moves. Mark what the cursor touches withdata-targetanddata-cursor; measure withrect(), never hard-code. - Choreograph. The
ActAPI. Keep what appears mounted and toggle it so exits animate (BubbleandFlyhand off explicitly). Animate the relationship, not just the object: a new row carries the rows below it, a surface that resizes never stretches its text. Beats overlap, groups stagger, the payoff holds, the loop ends where it began or resets with a visible cause. - Rehearse. Set
posterfirst: most people see only that frame (a thumbnail, reduced motion, a screenshot), so it is the beat that tells the story on its own, never one caught mid-change, with the result left on screen rather than tidied away (references/motion.md, Story). Then film the loop, not just a still, and always with--gate: it is the same contact sheet plus the verdict, so it costs nothing extra. Film the contact sheet at the shown width and at 390, and step through every press, menu, morph and the loop seam (references/rehearse.md). A still can't show a pop. Read every frame, fix the largest visible fault first (framing, then hierarchy, then motion, then polish), re-film. Then hold it next to the closest gold and answer the whole-composition and style pairs inreferences/teaching.mdas questions about your still (what does the eye land on first, and is it the result? is one window, tile or device clearly leading?); any no is the largest fault. Don't hand over until the loop's--gateendsrehearsal passed: every line it prints is a fault a viewer will see, even when the contact sheet looks smooth. Short on time or tool calls, fixing its lines comes before more stills, the review and the notes. Passing is necessary, not sufficient. Then run the last pass inreferences/rehearse.md: a fresh-eye review (references/review.md) andREHEARSAL.mdbeside the component (template inreferences/verify.md, Hand over): the gold you copied, what you changed, what you did not check.
Faults that come back every round, each with its rule; check them before handing over:
- Content that swaps instead of moving (
references/motion.md, Changing text and values). - Gray bars where the eye lands; filler belongs at the edges (
references/craft.md, Restraint). - A plate behind the window, or a window floating with air on four sides; the window or phone fills at least two thirds of the stage and runs off an edge (
references/framing.md, rule 5 and Small formats and the page). - Empty bands, cut controls and shadows (
references/craft.md, Restraint;references/framing.md, rule 4). - Stock AI and made-up logos: sparkles, purple, a letter in a colored square (
references/craft.md, Icons and logos). - Busy rows and uneven insets (
references/craft.md, Restraint and Spacing and alignment). - Long holds and a reset with no cause (
references/motion.md, Loops). - A selection that isn't under the I-beam (
references/motion.md, Drags and selection). - A status bar or home indicator drawn by hand; the Phone draws both (
references/craft.md, Chrome and devices). - A centered amount centered with its sign (
references/craft.md, Spacing and alignment).
Examples
Film the closest one before you start (step 4). The gold examples are the quality bar; product studies are for borrowing an interaction, never another product's identity; specimen sheets are catalogs, not compositions. Run everything with npm install and npm run dev. teaching/ holds bad/good pairs (references/teaching.md) for diagnosing a problem; the bad halves are never starting points.
Gold
| Need | Example | What to learn |
|---|---|---|
| Still or feature card | static-card | Quiet hierarchy, a hard crop, one satellite, real words only on the selected customer, its neighbors and the total |
| Dark still | dark-bento | One signal said once; album art keeps it a music app |
| Animated hero, a gesture | hero-demo | Five beats, named targets, an annotation, a terminal coming forward |
| Choreography, no cursor | payout-flow | Slow overlapping arrivals, reading time, a payoff that holds |
| Content changing in place | choreography | Retained tracks, soft masks, dependent timing |
| AI answer | ai-chat | The question sent, Thinking, the answer streaming in with its height, sources last; no sparkles, no purple |
| AI with cards | ai-cards | A multiple-choice card answered and kept as the record, a card of options opening in the thread, booked from its own button |
| Form validation | form-error | An error on the field that caused it, cleared by fixing it, then the button confirms on itself |
| Drag to reorder | reorder | A row lifted by its grip, the others making room, dropped into place |
| Chart scrub | chart-scrub | A hairline and dot that follow the pointer, the headline value rolling to the day under it |
| Edit in a table | table-edit | A cell edited in place, then the to
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
