Index of every page on this site: llms.txt
All skills
vercel avatar

/ui-demo

@86694bd
by vercelvercel/board147 stars
13
Run it yourself

Show a visible change working, in a narrated, captioned video of the browser (or a screenshot when one frame shows it), attached to the reply that links its PR. Use whenever a change touches what people see.

  • 2 files
  • 9.7 KB
  • Updated 3 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel/board/ui-demo

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈638 when used: this file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈217 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Show a change working

When a change touches what people see, show it instead of describing it: a video for a flow people click through, a screenshot when one still frame shows it, or nothing when there's nothing to see (say so in the PR instead).

The video records the browser you drive with the browser__* tools. Before each action you call narrate with one line, which is said out loud and captioned from that moment, and the action follows once it's been said. scripts/ui-demo in this skill records the tab, cuts the time you spend thinking, burns the captions in and mixes the voice, as an mp4 under 4 MB.

1. Pick where to try it

  • A dev server in the sandbox, almost always: start it in the background (pnpm dev > /tmp/dev.log 2>&1 &, after pnpm install) and poll it with curl until it answers. Read the repo's AGENTS.md or README for how it runs and what it needs. When it doesn't run yet, the try-it skill says what you can get, and what you can't.
  • A deployment, when the change needs real data or the deployed setup and the deployment is open to the public. A protected preview asks for Vercel login, which the browser can't do.

2. Rehearse, then record

Do the flow once without recording, so the take has no dead ends: browser__open the page, browser__snapshot, act on its refs. Then go back to where the flow starts, and:

  1. scripts/ui-demo start, with the page already open in the browser.
  2. For each step: narrate its line, then do it with the browser tools. Lines are short, first-person sentences people can hear in about 2 seconds, written to be said (words, not symbols or paths): "Opening the settings page", "Turning on dark mode", "The page switches to dark: it works".
  3. scripts/ui-demo stop /tmp/<thread>-<flow>.mp4
  • Only narrate a result ("it works", "the message is posted") once a snapshot or screenshot shows it. If the flow fails, record the failure and say so. Don't attach a video that claims something the screen doesn't show.
  • The take keeps each line and a few seconds after it, and cuts the rest, so take your time.
  • scripts/ui-demo start --mute records captions only, when sound adds nothing.
  • If stop says the video is over 4 MB, record a shorter take.

3. Attach it

Attach it to the reply that links the PR: vb reply <id> "<the PR link, and a line on what the video shows>" --attach /tmp/<thread>-<flow>.mp4. A screenshot works the same way (browser__screenshot, then --attach). Never attach test logs: the tests are in the PR.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 86694bd. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 12 hours ago.

Activeupdated 3 days ago

README badge

README badge for vercel/board/ui-demo