agentleFS
maven-ammarmaven-ammar/svelte-stageshow/stageshow/SKILL.md

stageshow

Skill2 starsChanged 13 days agoMITView on GitHub

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". Svelte 5 and plain CSS.

  • Installs packages

8 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions8 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 8

    1. benjitaylor/skills★ 2.6ksame name
    2. boraoztunc/skills★ 454same name
    3. joemccann/radon★ 34same name
    4. satiricalguru/Agents-skills★ 9same name
    5. umararshad4/honey-stack★ 5same name
    6. foverse/seoverse★ 4same name
    7. sanmidable/skills★ 2same name
    8. hamzzaqureshi/gravidex★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Motion that is not load-bearing: If the animation stopped halfway, the picture must still make sense.

    line 73

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 recognises the screen and sees the thing happen.

This is the Svelte 5 port of Stageshow, Benji Taylor's MIT skill and kit. Same idea, same rules, same five failures; only the code is Svelte.

The one idea

It reads as a real product, simplified to what the viewer needs, framed with intent, and every motion has a cause.

Faux UI fails in five ways: a screenshot in a box, a composition with no idea, decoration standing in for meaning, fake chrome around a thing that is not a window, and motion that is load-bearing. The rules here exist to catch those five.

Install

pnpm add svelte-stageshow
<script lang="ts">
  import { Stage, Window, Text, Row } from 'svelte-stageshow'
  import 'svelte-stageshow/style.css'
</script>

<Stage width={720} height={340} theme="light" palette="accent">
  <Window url="acme - invoices">
    <!-- your product's real interface, built from the kit's parts -->
  </Window>
</Stage>

The whole kit is ported: Stage, Window, Phone (with LockScreen and Notification), Bar, Text, Row, Avatar, Chip, Cursor, Keyboard, Thread, Receipt, Stamp, the 13 motion primitives, the 10 parts, the 6 controls, the chart/code/messages/prompt modules, 35 brand marks and four looks.

If you have read the React skill

Same workflow, same framing rules, same failure modes. What changes:

ReactSvelteWhy
import { Stage } from './kit'import { Stage } from 'svelte-stageshow'the kit is a package here, not a folder to copy
onClick, onEnter propsonclick, onenter — callbacks are plain propsSvelte 5 uses callback props, not synthetic events
<Text size={9} mono>SERIAL</Text><Text style="font-family:var(--ss-mono);font-size:9px">SERIAL</Text>Text takes children; the look owns type scale, style owns exceptions
<Bar tone="faint"><Bar tone={2}>tone is 1–5, a number, all through the kit
children as props.childrenchildren as a snippet, implicit in markupSvelte 5
useEffect scene setup$effect, or script on Stagerunes
forwardRefbind:thisSvelte

The seven steps

  1. Pick the moment. One interaction, one state, one claim. Write it in a sentence before any markup: "a merchant marks an invoice paid and the total updates".
  2. Choose the frame. A window, a phone, a card or a satellite, and only one of them may be the hero. A card stays a card; faking browser chrome around a card is one of the five failures.
  3. Compose. One gutter, one inset, a crop that cuts something on purpose. references/framing.md has the rules per shape: overlap, stacked cards, opposite corners, bento.
  4. Build from the kit. Parts for the hard geometry (bars, rows, avatars, chips, keyboards), your own markup for the product's real content.
  5. Write real words where they carry meaning. Fidelity is honest: minimal is all bars, standard is words where they matter, realistic is real content everywhere. A card that says nothing but grey bars has said nothing.
  6. Motion that is not load-bearing. If the animation stopped halfway, the picture must still make sense. Honour reduced motion: Stage holds the poster and stops the script.
  7. Film it and look. The upstream film.mjs works unchanged against a capture route; this port's gallery serves /scenes/<slug> and ?capture=<scene> with a #example wrapper and an .ss-fit stage, so a still or a contact sheet is one command.

The parts that do the hard work

  • Stage — design size, scale to fit, look (theme, palette, fidelity), the scene state, and the script that drives it. The script receives an Act: set, wait, move, click, type, scroll, key, mark.
  • Window — title bar, lights, url pill, an edge fade for content that continues.
  • Phone — device frame, plus LockScreen and Notification for lock-screen studies.
  • Keyboard — a real key grid with modifiers; use it, never draw one by hand.
  • Text / Bar / Row / Avatar / Chip — the small parts that make a fake read as real.
  • Motion — Collapse, Roll, Swap, Count, Connector, Fly, Follow, Popover, Scroll, Camera, Expand, States, Stream. Each solves a specific transition; reach for the named one rather than animating raw CSS.

Small formats: a second composition, not a squeeze

At 358–390 the card is not the wide card scaled down. Redesign it: move the claim, change what is cropped, drop the satellite, let one element run off the edge.

The one hard rule: a crop has to still read as the thing it is. A keyboard cropped to two rows of keys stops being a keyboard and becomes a pattern of rectangles; a window cropped to its title bar stops being a window. Cut where the form is still unmistakable and let the cut fall on something the eye completes.

Verification, and the trap

Film the reference in the same run as your own capture. A reference filmed before a rebuild is not valid: stale captures produced three wrong verdicts in one night.

Score at a settled mark, not at the last mark in a script: a mid-transition frame compared between two runs measures timing, not fidelity.

House style

The kit gives geometry and behaviour, not a brand. Map the host product's tokens onto the kit's CSS custom properties (--ss-*) so the illustration sits beside the real product without looking borrowed.

Where to read next

  • references/framing.md — how a surface sits in its space, per shape.
  • references/craft.md — the judgement calls: contrast, weight, what earns its place.
  • references/kit.md — every part's props.
  • references/verify.md — how to film and what to look for.
  • Upstream, for anything this file does not restate: https://benji.org/stageshow

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.