webapp-capture — Claude Code command: what it does, how to install
webapp-capture captures a running web app: a narrated screen recording, route-by-route screenshots, a component library with tokens, and a UI inconsistency audit. Each mode runs as its own pass.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install browser-and-app-testing-tools@wasp-nestWhat webapp-capture does
The command acts as an orchestrator. It reads the first argument (demo, screenshots, library, audit, shadcn, all or doctor) and walks through a single round of setup questions covering environment, theme, route list and output folder. It never touches credentials or MFA codes itself: a person logs into the app manually in a visible browser window launched by the save-session.mjs script, and sensitive screen regions get masked before any screenshot is reported.
Before capture starts, it loads the webapp-capture-stinger skill through Core's component resolver (pest-controller-suit); version 3 of that resolver needs wasp-nest-core to be present. A doctor.mjs check then verifies Chromium and other dependencies and must print Ready. before the orchestrator applies the recommended browser shard count.
The shadcn mode maps captured components and theme tokens onto shadcn/ui or shadcn-svelte, while all chains library building, the audit, the shadcn map and the demo, ending with a handoff package for Claude Design. Regular page crawls only click tabs and scroll same-origin routes; changing app state is off-limits except for an onboarding plan that the user approves in advance for a local or seeded environment.
What it helps with
- record a narrated demo video of a live app
- capture route-by-route screenshots including tabs
- pull a component library with design tokens
- flag visual and code inconsistencies in the UI
- map app components onto shadcn/ui
Example prompts for the agent
- Run /webapp-capture demo against the app at localhost:3000
- Build the component library with /webapp-capture library
- Check for UI inconsistencies using /webapp-capture audit
How to install webapp-capture
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install browser-and-app-testing-tools@wasp-nest2Manually: put the files in place
.claude/commands/webapp-capture.mdCall it with /webapp-capture. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/webapp-capture.mdCall it with /prompts:webapp-capture. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/webapp-capture.prompt.mdManually: put the files in place
.gemini/commands/webapp-capture.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about webapp-capture
How do I install webapp-capture in Claude Code?
Add the marketplace with /plugin marketplace add legioncodeinc/vibe-coding-tools, then install the plugin with /plugin install browser-and-app-testing-tools@wasp-nest.
What does the webapp-capture command do?
Depending on the mode you pick, it captures a running web app as a demo recording, a set of route screenshots, a component library with tokens, a UI audit, or a shadcn/ui mapping.
What does webapp-capture need to run?
It loads the webapp-capture-stinger skill through Core's component resolver and runs a doctor.mjs check for Chromium and other dependencies before any capture starts.