storyboard-shot-to-html
Turns a storyboard shot (video prompt + narration) into a self-contained fullscreen HTML CSS animation for the browser. Analyzes VO/narration, searches related facts and usage cues, then builds a rich layered stage (camera, subject, secondary UI, light, micro-detail) with Fullscreen API and Space-to-play. Use when the user wants storyboard-shot-to-html, HTML animation preview, prompt-to-HTML, storyboard to HTML, prompt animation demo, narration visualization, fullscreen preview, Space to play, or a web demo of a video prompt / shot.
godot-fun · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add godot-fun/godot-agent --skill storyboard-shot-to-htmlAbout this skill
name: storyboard-shot-to-html description: >- Turns a storyboard shot (video prompt + narration) into a self-contained fullscreen HTML CSS animation for the browser. Analyzes VO/narration, searches related facts and usage cues, then builds a rich layered stage (camera, subject, secondary UI, light, micro-detail) with Fullscreen API and Space-to-play. Use when the user wants storyboard-shot-to-html, HTML animation preview, prompt-to-HTML, storyboard to HTML, prompt animation demo, narration visualization, fullscreen preview, Space to play, or a web demo of a video prompt / shot.
Storyboard Shot → HTML
Turn one shot (video prompt + narration) into a single-file HTML animation you can open in a browser — a motion sketch of the intended frame, not a real video render.
Companion to storyboard. Does not call video/image generation APIs.
Inputs
Accept any of:
| Input | How to use |
|---|---|
Storyboard .md + shot id (01, Shot 02, …) | Parse that shot’s Video prompt, Chinese / English, Visual, Camera, Duration, Visual Style |
| Pasted shot block | Same fields if present |
| Raw video prompt (± narration) | Prompt = visual source; narration = meaning layer to research |
If multiple shots and no id → ask once, or do Shot 01 only when the user clearly wants a quick sample.
Delivery
| Mode | Behavior |
|---|---|
User gives an .html path | Write there |
| User gives a directory | Write <dir>/shot-<id>-preview.html (shot-01-preview.html if no id) |
| Storyboard path known, no output path | Write next to the .md: <stem>-shot-<id>-preview.html |
| Raw prompt only | Write test/manual/<slug>-preview.html (or user-named file) |
Rules:
- Always write the full HTML file (UTF-8). Chat: short confirm only (path, shot id, research notes, how to open).
- Prefer one self-contained
.html(inline CSS/JS). No build step, no CDN frameworks required. Google Fonts OK if useful. - Fullscreen by default (see below) — first paint is the stage filling the browser; no document scroll of title/meta under the frame.
- After write: open in the system browser (
Start-Process/open/xdg-open). Iffile://is flaky, serve the parent dir with a tiny static server and openhttp://127.0.0.1:<port>/<file>. - Never overwrite the storyboard
.md.
Fullscreen (required)
The preview must play as a full-viewport cinematic stage, not a letterboxed card on a scrolling page.
| Requirement | Detail |
|---|---|
| Viewport fill | html, body { height:100%; overflow:hidden }; stage covers 100vw × 100vh |
| Aspect | Keep storyboard aspect (default 16:9) with cover (crop) or letterbox on black — prefer cover so the frame fills the screen |
| No below-fold chrome | Title, tags, original prompt must not sit under the stage in normal flow |
| Overlay meta | Put prompt / research in a hidden overlay (I or ? to toggle; Esc closes). Do not burn VO/narration onto the stage — narration is for analysis only, not on-screen text |
| Space to play | Animations stay paused on load (first frame / idle pose). Space starts playback once. Do not autoplay on open. Hint text: Space to play · Click / F fullscreen · I prompt (may also mention Space to start) |
| Play once | Shot timeline is one-shot — no infinite / alternate loop on the main beat. When duration ends, hold the final frame (animation-fill-mode: forwards or equivalent). Do not restart on a second Space, and do not auto-replay |
| Browser Fullscreen API | On click (or F), call element.requestFullscreen() on the stage root. Show a brief hint until entered (Click / F fullscreen · Space to play). Esc exits native fullscreen |
| Open behavior | After writing the file, open it so the user lands on the fullscreen-ready paused page; wait for Space to play |
Workflow
Task Progress:
- [ ] Parse shot (prompt + VO + camera/duration/style)
- [ ] Analyze narration → concepts to ground
- [ ] Search related info / usage (when needed)
- [ ] Plan motion layers (camera / subject / secondary / light / micro) + timing beats
- [ ] Design rich stage from prompt + research (depth planes, staggers, payoff hold)
- [ ] Write HTML; open in browser
- [ ] Chat: path + what the demo shows
1. Parse the shot
Extract:
- Video prompt (primary visual / motion spec)
- Chinese / English VO (meaning, pacing;
(no VO)= skip that language) - Visual, Camera, Duration, piece-level Visual Style when available
Map duration to animation timing when sensible (~5s → ~5s one-shot timeline, then hold). Playback starts only on Space (paused until then); never loop or auto-replay.
2. Analyze narration (required)
From VO, list concrete concepts that affect what the viewer should understand:
- Product / feature / API / workflow names
- Places, eras, UI metaphors, audience takeaway
- Claims that need accurate depiction (do not invent)
If VO only restates mood already in the prompt, research may be light — still state that explicitly in chat.
3. Search related info / usage
When concepts are factual, technical, or product-specific:
- Use WebSearch / WebFetch (or project docs) for short, trustworthy cues: what it is, how it’s used, typical UI/visual metaphors.
- Fold only what helps the HTML stage (labels, layout metaphors, correct terminology, iconic shapes).
- Do not invent logos, prices, legal claims, or competitor branding.
- If search fails or materials already suffice, proceed with prompt-only visuals; note gaps briefly.
Skip heavy research for pure mood/atmosphere shots with no domain claims.
4. Build the HTML animation
Goal: one composition that reads as the shot at first viewport — animated stand-in for the video prompt. Aim for a *rich motion sketch
Read the complete source ↗