luckiest-co 1.0.19 → 1.0.21

package/skills/luckiest-video-studio/references/step-3-compose.md

@@ -0,0 +1,210 @@
+# Step 3: Hand off to Hyperframes
+
+## Create the composition brief
+
+Write `<output-dir>/composition-brief.md` before creating or editing the Hyperframes composition.
+
+```markdown
+# Hyperframes Composition Brief: [App Name]
+
+## Objective
+Create a short launch-style video for [App Name].
+
+## Output
+- Composition directory: `<output-dir>/composition/`
+- Rendered video: `<output-dir>/final.mp4`
+- Format: [landscape / vertical / square] — [width]x[height]
+- Duration: [15-25 seconds]
+
+## Source Material
+- Project root: [path]
+- Primary files read: [index.html, styles.css, README, etc.]
+- Product name: [name]
+- Tagline / strongest claim: [line]
+- Key UI or visual moment to recreate: [specific element]
+- Copy that must appear verbatim:
+  - [line 1]
+  - [line 2]
+
+## Creative Direction
+- Tone preset: [default / polished / yc-parody / chaotic / deadpan / cinematic / app-store]
+- Creative direction: [freeform phrase, inferred or user-provided]
+- Interpretation: [how tone affects pacing, writing, visual energy, and restraint]
+- Angle: [one paragraph from plan.md]
+- Hook: [first 2-3 seconds]
+- Outro / punchline: [final line]
+- Avoid:
+  - Generic SaaS language
+  - Abstract filler visuals
+  - Unrelated visual redesign
+
+## Visual Identity
+- Background: [exact value from project]
+- Text: [exact value from project]
+- Accent: [exact value from project]
+- Display font: [font or fallback decision]
+- Body font: [font or fallback decision]
+- Visual references from the project: [short list]
+
+## Storyboard
+Use the storyboard in `<output-dir>/plan.md` as the creative contract.
+
+Scene summary:
+1. [Scene name] — [duration]s — [what must be seen / read]
+2. [Scene name] — [duration]s — [what must be seen / read]
+3. [...]
+
+## Audio
+- Audio role: [warm bed / sparse professional accents / cinematic support / dense rhythmic layer / intentional silence]
+- Audio arc: [how sound changes across the video]
+- Music: [filename, or none only if disabled, missing, or intentionally silent]
+- Music treatment: [volume posture, fade-in/out intent, beat/swell notes; e.g. fade under final logo]
+- Music cue guidance: [cue source — existing preset path, or "detect at composition via analyze_music_cues.py / hyperframes beats" — plus concise optional timing hints; or unavailable]
+- Audio-reactive treatment: [none / subtle / expressive; what visual qualities may respond to RMS/frequency energy]
+- Audio-coupled moments:
+  - [scene/moment] — [typing / beat reveal / counter / card sequence / simulated interaction / final logo]
+  - [scene/moment] — [intent]
+- SFX selection guidance: [how sound should match motion and interaction; examples only, not rigid rules]
+- SFX analysis guidance: [path to sfx-analysis.md/json if present; use lower high-frequency-risk sounds for repeated or polished moments]
+- Exact SFX choice: Hyperframes should choose filenames, timestamps, density, and volume based on the implemented animation.
+- Audio files: copy the chosen music and any Hyperframes-selected SFX into `<output-dir>/composition/assets/`
+
+## Hyperframes Instructions
+Load the composition-building Hyperframes domain skills — `hyperframes-core` (composition contract + `data-*` timing), `hyperframes-animation` (motion), `hyperframes-creative` (design spec, beats, audio-reactive), `hyperframes-keyframes` (seek-safe keyframes), and `hyperframes-cli` (lint/check/render). /video is its own workflow: do not enter the `hyperframes` entry-point intent interview and do not route into its generic promo / launch-video workflow. Prefer native Hyperframes conventions over anything in `luckiest-video-studio`.
+
+Requirements:
+- Show at least one real UI, copy, or visual element from the source project.
+- Keep all text readable in the final render.
+- Keep the video within 15-25 seconds.
+- Include the planned music/SFX layer unless audio was explicitly disabled or documented as intentionally silent.
+- Treat `luckiest-video-studio` audio notes as guidance, not a fixed cue sheet. Choose SFX after the visual animation exists.
+- Treat music cue metadata as optional timing hints. Hyperframes decides exact animation timing and should ignore cues that hurt readability, scene pacing, or the product story.
+- Major reveals may move toward nearby strong cues within about 0.15s. Smaller entrances may align to nearby beat points within about 0.10s. Use only 1-3 strong cue locks in a 15-25s video unless the edit clearly benefits from more.
+- Use SFX to support motion and interaction: card sounds for card-like reveals, short announcement cues for major payoffs, key/click sounds for text or user actions, and restraint when the edit is already busy.
+- Honor planned music treatment such as fade-outs, ducking, beat-aligned reveals, or letting a final SFX ring over the music, using the best Hyperframes-supported implementation.
+- When music is present and the treatment is not `none`, consider Hyperframes audio-reactive workflow: extract audio data and use RMS/frequency bands for subtle, brand-specific motion. Good targets are glow, depth, background warmth, card presence, title emphasis, or other existing visual elements. Avoid waveform/equalizer visuals, musical-note graphics, generic particle systems, strobing, or heavy pulsing.
+- Use local assets for audio and any required runtime/media dependencies when possible.
+- Run `hyperframes check` before render — it is the single gate.
+```
+
+The brief is the boundary: if a detail belongs to product positioning, copy, tone, source material, or selection of moments, `luckiest-video-studio` should specify it. If a detail belongs to composition implementation, Hyperframes should decide it.
+
+---
+
+## Audio asset preparation
+
+Read [audio.md](audio.md). Copy the planned music into `<output-dir>/composition/assets/music/` before building the composition.
+
+```bash
+mkdir -p <output-dir>/composition/assets/music
+cp <skill-dir>/assets/music/<track>.mp3 <output-dir>/composition/assets/music/
+```
+
+`<skill-dir>` is this skill's own directory (see "Skill directory" in `SKILL.md`).
+
+Hyperframes copies any SFX it selects into the same `assets/` tree after choosing exact files.
+
+---
+
+## Voiceover (only when the user explicitly asks)
+
+Voiceover is disabled unless the user explicitly requests it, for example
+with `--voice` or "narrate this". Do not offer or enable narration during a
+normal `luckiest-video-studio` run.
+
+When voice is disabled, do not write a voiceover script, generate narration,
+transcribe audio, duck music, add a voice track, or merge narration into the
+video. The normal video export must remain entirely voice-agnostic.
+
+When voice is enabled, write the narration lines into `plan.md` under a
+`## Voiceover script` section, then generate the audio through Kokoro:
+
+```bash
+npx hyperframes tts "<narration text or path to script>" \
+  --voice af_heart \
+  --output <output-dir>/composition/assets/voiceover.wav
+```
+
+If the user wants a different Kokoro voice, run `npx hyperframes tts --list`
+to see the available options. The command above is the voice implementation
+for this PR and should be used directly.
+
+Wire it into the composition on its own track. Music ducks to 0.12–0.15 for the duration of the voiceover, then returns to its normal level:
+
+```html
+<audio id="vo" data-start="0" data-track-index="3" data-volume="1" src="assets/voiceover.wav"></audio>
+```
+
+Scene durations must flex to match the generated audio — check the WAV duration after generation and adjust `data-duration` values accordingly. Do not hardcode scene lengths when voiceover is present; let the voice set the pace.
+
+---
+
+## Audio-reactive extraction (when music is present)
+
+When music is present and the treatment is not `none`, the composition can react to per-frame audio data. **Delegate the extraction to the Hyperframes audio-reactive workflow** — `luckiest-video-studio` does not ship an extraction script and must not hardcode a path to one.
+
+In the composition step, follow the audio-reactive guidance owned by the `hyperframes-creative` skill (let that skill locate its own files). It owns the data format, the extraction helper (which ships with that skill, not with `luckiest-video-studio`, so don't hardcode a path to it), and the per-frame sampling pattern. Ask Hyperframes to extract the audio data and wire at least one visual element to it.
+
+If extraction is unavailable (no helper, or ffmpeg missing), note it in the brief and skip audio-reactive — do not block the render.
+
+---
+
+## Beat sync (when a cue source is available)
+
+Get a cue source first (see `audio.md` → "Beat and cue sources"): an existing preset, `analyze_music_cues.py` on any track (needs Python; run via `uv`), or `npx hyperframes beats` (no Python; needs Hyperframes ≥ 0.6.99). The rich sources (preset / `analyze_music_cues.py`) give two arrays; `hyperframes beats` gives one.
+
+- **`strongCues`** — high-intensity beats (drops, swells, accents). Use for **major moments**: scene transitions, hero reveals, match payoff, logo landing. Lock 1–3 per video. With `hyperframes beats` (no `strongCues`), take the highest-`strength` beats instead.
+- **`beats`** — the full beat grid. Use to **snap small sequential events** into the music's pulse: cards arriving one by one, stats popping in, sequenced SFX hits.
+
+### How to implement
+
+**Major moments (strong cues):**
+1. Load the cue source: the preset/analysis JSON (`strongCues` + `beats`), or the beat-grid JSON that `hyperframes beats` writes (a plain beat list; see the current hyperframes-cli skill for its location).
+2. Pick 1–3 strong timestamps near a planned major visual moment — `strongCues`, or the highest-`strength` beats.
+3. Shift the reveal's start time to land within ±0.15s of the cue.
+4. Mark it: `// beat-locked: 5.80s`
+
+**Sequential events (beats):**
+1. Decide how many sequential items there are (e.g. 3 stats, 4 profile cards).
+2. Find the nearest beat to your intended start time for the first item.
+3. Use consecutive beats from that point for each subsequent item — snap each within ±0.10s of a beat timestamp.
+4. Mark it: `// beat-grid: stat 1 at 12.65s, stat 2 at 13.17s, stat 3 at 13.70s`
+
+**Readable text vs the beat grid:** if the sequential items are text the viewer reads (stat labels, list rows, callouts) and the beats are close (under ~0.6s apart at fast tempos), do not reveal a new line on every beat — it outruns reading (this rushed the bicycles spec rows). Snap to every other beat, or reveal them quickly and hold the full set on screen afterward. Non-text accents (glows, dots, ticks) may still hit every beat. See the reading-time floor in `step-2-plan.md`.
+
+This gives you two layers of musicality: the big moments land on the strongest hits, and the small events tick along with the pulse.
+
+Do not force every tween onto a beat — readability and scene pacing come first. If snapping a tween to a beat hurts copy legibility or the product story, use the natural timing instead.
+
+If SFX are enabled, also pass `<skill-dir>/assets/sfx/sfx-analysis.md` as selection guidance. Prefer low high-frequency-risk files for repeated or polished moments. SFX on sequential events should fire at the same timestamp as the visual — the sound and motion land together.
+
+---
+
+## Call Hyperframes
+
+After `<output-dir>/plan.md`, `<output-dir>/composition-brief.md`, and selected audio assets exist:
+
+1. Load the Hyperframes domain skills (`hyperframes-core`, `hyperframes-animation`, `hyperframes-creative`, `hyperframes-keyframes`, `hyperframes-cli`) to create or update `<output-dir>/composition/`. /video is its own workflow — do not enter the `hyperframes` entry-point intent interview or route into its generic promo / launch-video workflow.
+2. Pass Hyperframes the composition brief, the video plan, and the source files it should reference.
+3. Let Hyperframes choose the implementation details.
+4. Run Hyperframes check (the single gate before render).
+5. Render to `<output-dir>/final.mp4`.
+
+Do not manually copy stale composition snippets from this skill into the output. The point of delegating is to benefit from the latest Hyperframes guidance.
+
+---
+
+## Self-review checklist
+
+Before moving to delivery, verify:
+
+- [ ] `<output-dir>/composition-brief.md` exists.
+- [ ] The brief clearly identifies the exact product moments to show.
+- [ ] The composition uses the current Hyperframes workflow, not a hardcoded `luckiest-video-studio` template.
+- [ ] Music file is copied into `<output-dir>/composition/assets/music/`.
+- [ ] At least one visual element subtly reacts to the music (audio-reactive treatment present), or extraction failure is documented.
+- [ ] At least 1 major tween is beat-locked to a strong cue (a `strongCue`, or the highest-`strength` beat from `hyperframes beats`) within ±0.15s, marked `// beat-locked` (or natural timing was chosen for readability).
+- [ ] Sequential events (cards, stats, list items) snap to consecutive `beats[]` timestamps (±0.10s), marked `// beat-grid` (or natural timing was chosen for readability).
+- [ ] The composition shows at least one real UI, copy, or visual element from the project.
+- [ ] Total duration is 15-25 seconds.
+- [ ] Hyperframes check passes, or any blocker is documented for the user.

package/skills/luckiest-video-studio/references/step-4-deliver.md

@@ -0,0 +1,168 @@
+# Step 4: Validate, render, and deliver
+
+## Validate
+
+```bash
+cd <output-dir>/composition
+npx hyperframes check   # the single pre-render gate — fix every error it reports
+```
+
+Fix all errors. `check` is the single pre-render gate — run it and fix everything it reports, including WCAG contrast failures (they gate as errors, not warnings). Each contrast finding carries a suggested compliant color, so apply it or adjust within the palette family and re-run `check` — most fixes need no screenshot. There is no per-element contrast escape hatch for real text; the only bypass is `check --no-contrast`, which skips the entire WCAG pass (all-or-nothing), not a way to accept one borderline element. For exact contrast thresholds, layout escape hatches, and reporting details, follow the current hyperframes-cli `check` guidance. `check`'s layout pass backstops the "keep all text readable" creative law — fix any reported overflow.
+
+For a visual gut-check before rendering, optionally capture key frames:
+
+```bash
+npx hyperframes snapshot   # PNG key frames
+```
+
+## Preview
+
+```bash
+npx hyperframes preview
+```
+
+Tell the user the preview is running and give them the localhost URL. Invite them to check it before rendering.
+
+If the user approves or asks to render:
+
+## Render
+
+```bash
+npx hyperframes render --output ../final.mp4
+```
+
+This outputs to `<output-dir>/final.mp4` (one level up from the composition directory).
+
+For a faster iteration render:
+```bash
+npx hyperframes render --quality draft --output ../final.mp4
+```
+
+For final delivery:
+```bash
+npx hyperframes render --quality high --output ../final.mp4
+```
+
+## Pick the poster frame
+
+The poster is the still shown before the video plays — the first thing anyone sees when it's idle or unplayed. Don't leave it to the raw first frame or an arbitrary timestamp; those land on fades, mid-transitions, blank intro backgrounds, or half-rendered text.
+
+You built this composition, so you already know its strongest moment and exactly when it lands — the hook line, the hero reveal, or the final logo. Pick that beat at a **settled** point: text fully animated in, before it exits (the storyboard timings tell you the safe window). Then extract that one frame full-res with ffmpeg. From `<output-dir>/composition`:
+
+```bash
+# use the timestamp of your strongest settled beat, e.g. 3.2s
+ffmpeg -ss 3.2 -i ../final.mp4 -frames:v 1 -q:v 2 ../poster.jpg
+```
+
+Aim for a frame that's postable on its own (the "show the thing" law — any frozen frame should be shareable). If the pulled frame lands on a transition or mid-animation, nudge the timestamp a few tenths of a second and re-extract.
+
+### Bake the poster as frame 0
+
+A bare `.mp4` has no `poster` attribute — every player and platform picks its own idle thumbnail, and almost all of them grab **frame 0**. Slack, Twitter/X, and Discord regenerate thumbnails server-side and ignore embedded cover-art metadata, so the *only* reliable way to control the idle image everywhere is to make frame 0 *be* the poster.
+
+Replace **only** the first frame's pixels with `poster.jpg`, leaving every other frame and all timing untouched — same duration, same frame count, audio copied through. At 30fps the poster shows for 1/30s before the intro rolls, so it's imperceptible on playback but it's what every thumbnail grabber sees. From `<output-dir>`:
+
+```bash
+ffmpeg -y -i final.mp4 -i poster.jpg \
+  -filter_complex "[0:v][1:v]overlay=0:0:enable='eq(n,0)'[v]" \
+  -map "[v]" -map 0:a? -c:v libx264 -crf 18 -preset slow -pix_fmt yuv420p \
+  -c:a copy -movflags +faststart final.poster.mp4 \
+  && mv final.poster.mp4 final.mp4
+```
+
+The poster (`poster.jpg`) matches the video's dimensions because it was pulled from the same render, so the overlay lines up exactly. Keep `poster.jpg` alongside — it's the custom-thumbnail asset for platforms that accept an upload (Instagram, TikTok, YouTube, Facebook, and the LinkedIn post editor) and the `poster="poster.jpg"` image for any `<video>` that embeds the video (a gallery card, the user's site).
+
+## Write share copy
+
+Write `<output-dir>/share-copy.txt`.
+
+The share copy should be:
+- One to three sentences max
+- Postable as-is to Twitter/X, LinkedIn, or Discord
+- Specific to the project — no generic "excited to share" language
+- Tone-matched to the video
+
+`share-copy.txt` is the canonical single caption. Do not put multi-platform variants, long launch notes, or Product Hunt copy in this file.
+
+If variants are useful, write them to a separate optional file:
+
+```text
+<output-dir>/share-copy-variants.md
+```
+
+### Share copy by tone
+
+**`default`:**
+```
+Made [App Name]. It's [what it does, in the project's own absurd terms].
+[The best line from the product.]
+```
+
+**`polished`:**
+```
+Introducing [App Name]: [clean one-liner from the site].
+Built with [stack if notable].
+```
+
+**`yc-parody`:**
+```
+We built [App Name] to solve [problem stated completely seriously].
+[Deadpan feature or stat.]
+```
+
+**`chaotic`:**
+```
+[ALL CAPS CLAIM].
+[App Name] is [wildly overstated description].
+Link below.
+```
+
+**`deadpan`:**
+```
+I made [App Name].
+It [what it does].
+```
+
+**`cinematic`:**
+```
+[App Name].
+[Tagline from the site, verbatim or lightly adapted.]
+```
+
+**`app-store`:**
+```
+[App Name] is now live.
+[Feature 1], [Feature 2], and [Feature 3] — all in one place.
+```
+
+### Example: Taxi for Taxis
+
+```
+Every day, taxis carry us. But who carries the taxis?
+Taxi for Taxis: the ride-hailing app for ride-hailing assets.
+Available in 12 metros.
+```
+
+## Final output structure
+
+After this step, `<output-dir>/` should contain:
+
+```
+<output-dir>/
+  final.mp4                — the rendered video
+  poster.jpg                — the poster (best frame, for <video poster>)
+  plan.md            — the plan and storyboard
+  composition-brief.md    — the Hyperframes handoff brief
+  share-copy.txt          — the share caption
+  composition/            — the Hyperframes project
+    index.html
+    ...
+```
+
+## Telling the user
+
+After everything is done, tell the user:
+- Where the video is (`<output-dir>/final.mp4`)
+- Where the share copy is
+- One sentence on what the video does creatively
+- Optionally: offer to re-roll a scene, change tone, or try a different angle

package/skills/luckiest-video-studio/references/storyboard.md

@@ -0,0 +1,78 @@
+# storyboard.json
+
+`storyboard.json` in the run folder is the source of truth. `plan.md` explains the
+idea; `storyboard.json` is what renders. Every edit after the first render changes
+this file and re-renders only what it touched. Schema:
+`<skill-dir>/scripts/storyboard.schema.json`.
+
+## Shape
+
+```json
+{
+  "version": 1,
+  "title": "Acme launch",
+  "mode": "demo",
+  "tone": "polished",
+  "format": { "width": 1920, "height": 1080, "fps": 30 },
+  "hyperframes": "0.8.84",
+  "music": { "file": "audio/bed.mp3", "volume": 0.3, "license": "user supplied" },
+  "scenes": [
+    { "id": "hook", "kind": "motion", "duration": 2.5, "line": "Your invoices, done in one click" },
+    { "id": "create-invoice", "kind": "demo", "duration": 6, "source": "demo/create.mp4", "sourceStart": 1.2, "line": "Create an invoice" },
+    { "id": "stat", "kind": "motion", "duration": 2, "line": "3x faster than last year", "variables": { "value": "3x" } },
+    { "id": "logo-close", "kind": "logo", "recipe": "piece-assembly", "duration": 3, "assets": ["brand/logo.svg"], "line": "Acme" }
+  ]
+}
+```
+
+| Field | Meaning |
+|---|---|
+| `format` | Output size and frame rate. Landscape 1920x1080, vertical 1080x1920, square 1080x1080. |
+| `hyperframes` | Pinned HyperFrames version so a re-render months later looks the same. |
+| `music` | Optional bed mixed under the joined video, looped and faded out. Licensed files only. |
+| `scenes[].id` | Lowercase and hyphens. Stable: edits refer to scenes by id. |
+| `scenes[].kind` | `motion` (HyperFrames scene), `logo` (HyperFrames logo recipe), `demo` (footage). |
+| `scenes[].composition` | For motion and logo, the sub-composition under `composition/`. Default `compositions/<id>.html`. |
+| `scenes[].source`, `sourceStart` | For demo, the footage file and where to start in it. |
+| `scenes[].variables` | Copy, colors, and file paths the composition reads. Keep editable values here, not hardcoded in HTML. |
+| `scenes[].assets` | Other files the scene depends on (logo SVG, shared CSS). Changing one re-renders the scene. |
+| `scenes[].line` | One line on what the scene says or shows. Goes into `TIMING.md`. |
+
+## Rendering
+
+```bash
+node <skill-dir>/scripts/render-scenes.mjs <run-dir>                    # render changed scenes, join final.mp4
+node <skill-dir>/scripts/render-scenes.mjs <run-dir> --scene stat       # force one scene
+node <skill-dir>/scripts/render-scenes.mjs <run-dir> --quality draft    # fast pass while iterating
+node <skill-dir>/scripts/render-scenes.mjs <run-dir> --no-join          # clips only
+```
+
+The script hashes each scene's JSON, its composition or footage, and its `assets`.
+A scene whose hash is unchanged keeps its clip. `--scene` renders only the named
+scenes and leaves the rest as they are. Every clip is normalized to the same size,
+frame rate, and a stereo audio track, so the join is a lossless concat. It writes
+`clips/NN-id.mp4`, `final.mp4`, and `TIMING.md`.
+
+It runs `hyperframes` when it is on the PATH, otherwise `npx hyperframes@<pinned
+version>`. Before the first `npx` run in a session, tell the user it downloads
+HyperFrames from npm and ask.
+
+## Rules for scenes that re-render cleanly
+
+- One sub-composition per scene. A scene never reads another scene's timeline.
+- Every frame is a function of time: GSAP or keyframes seeked by HyperFrames, no
+  CSS transitions, no `setTimeout`, no state carried between frames.
+- Put transitions inside the scene that owns them (the outgoing scene's last 0.3s
+  or the incoming scene's first 0.3s), never across a clip boundary.
+- Demo footage stays raw in `demo/`; trims live in `sourceStart` and `duration`.
+- Sound effects belong to the scene they punctuate, so they move with it.
+
+## Edits people ask for
+
+| Request | Change |
+|---|---|
+| "Change the headline in scene 3" | `scenes[2].variables` or the composition text, then `--scene <id>` |
+| "Make the demo part shorter" | `duration` or `sourceStart` of that demo scene |
+| "Swap scenes 2 and 4" | Reorder `scenes`; clips are reused and renamed, nothing re-renders |
+| "Different logo in the outro" | Replace the file listed in that scene's `assets` |
+| "Vertical version" | Change `format`; every scene re-renders |

package/skills/luckiest-video-studio/references/tones.md

@@ -0,0 +1,231 @@
+# Tone reference
+
+Seven tones. Each changes scripting energy, pacing, typography personality, and transition style.
+
+---
+
+## `default`
+
+**Energy:** Playful, clean, postable. The product gets to be funny on its own terms.
+
+**Voice:** First person plural. Warm. Direct. No corporate language.
+
+**Typography:** Mixed case. Comfortable weight. Let words breathe.
+
+**Pacing:** 4-5 scenes. Each scene 3-5 seconds. Comfortable rhythm.
+
+**Hook style:** A simple question or observation that sets up the reveal.
+```
+Dating apps were built for humans.
+Obvious mistake.
+```
+
+**Highlight style:** Short punchy phrases. One idea per scene.
+```
+Swipe through eligible horses near your pasture.
+```
+
+**Outro style:** The product name, then a tagline. Light punchline.
+```
+Horse Tinder.
+Find your perfect stablemate.
+```
+
+**Transitions:** Crossfade or clean slide.
+
+**When to use:** Most absurd consumer apps. Projects that have personality without trying too hard.
+
+---
+
+## `polished`
+
+**Energy:** Serious, elegant. Uses restraint as the creative choice.
+
+**Voice:** Third person or no voice. The product speaks for itself.
+
+**Typography:** Mixed case. Light-to-medium weight. Generous letter-spacing. Nothing aggressive.
+
+**Pacing:** 3-4 scenes. Each scene 4-6 seconds. Confidence through slow reveals.
+
+**Hook style:** A single strong image or the product name at full scale.
+
+**Highlight style:** One feature per scene. No bullets. No lists.
+```
+Wing certification
+upon completion.
+```
+
+**Outro style:** Product name. Tagline. Silence.
+
+**Transitions:** Slow crossfade (0.6-0.8s).
+
+**When to use:** Projects that aren't jokes. Products that want to feel premium. Anytime the user says "clean" or "elegant."
+
+---
+
+## `yc-parody`
+
+**Energy:** Deadpan startup launch energy. The joke is how seriously it's delivered.
+
+**Voice:** Serious. Matter-of-fact. No winking. The absurdity comes from the product, not the tone.
+
+**Typography:** Sentence case. Heavy weight or medium weight. Courier-adjacent for data points. No decoration.
+
+**Pacing:** 4-5 scenes. Structured. Each scene makes one claim.
+
+**Hook style:** The problem, stated completely seriously.
+```
+Every day, taxis carry us.
+But who carries the taxis?
+```
+
+**Highlight style:** Feature or metric stated as fact.
+```
+Available in 12 metros.
+99.1% fleet uptime.
+```
+
+**Outro style:** Product name. The tagline. A URL that implies legitimacy.
+```
+Taxi for Taxis
+The ride-hailing app for ride-hailing assets.
+taxifortaxis.com
+```
+
+**Transitions:** Hard cut or minimal crossfade (0.2s).
+
+**When to use:** Any recursive or absurd concept that benefits from being played straight. "Psychologists for Chatbots", "Taxi for Taxis", "Briefcase for Baby."
+
+---
+
+## `chaotic`
+
+**Energy:** Fast, loud, unhinged. The video is the joke.
+
+**Voice:** Aggressive. SHORT WORDS. CAPS. Metric dumps. Exclamation marks optional but not mandatory — confidence is louder.
+
+**Typography:** ALL CAPS. Heavy weight. Slightly oversized. Some words tilted. Some words larger than expected.
+
+**Pacing:** 6-8 scenes. Some scenes under 2 seconds. Never more than 4 seconds per scene.
+
+**Hook style:** Something that shouldn't exist, stated at full volume.
+```
+TRANSPORTATION WAS TOO CALM.
+```
+
+**Highlight style:** Rapid-fire. One word or one number per beat.
+```
+8,400 BOARS
+3 MINUTE ETA
+TUSKS-FIRST PICKUP
+```
+
+**Outro style:** The name slams in. Tagline hits. Cut to black.
+```
+UBER FOR WILD BOARS
+On-demand chaos, now with routing.
+```
+
+**Transitions:** Hard cut. Flash cut (brief white/black frame). Zoom cut (scale 1.2→1.0 on entrance).
+
+**When to use:** Chaotic concepts, logistics parodies, anything that can be played as a hype reel. "Uber for Wild Boars", anything with urgency or speed.
+
+---
+
+## `deadpan`
+
+**Energy:** Calm. Dry. The joke is that nothing registers as unusual.
+
+**Voice:** Minimal. One observation. Then the product. That's it.
+
+**Typography:** Mixed case. Large. Sparse. Lots of empty space. One thought at a time.
+
+**Pacing:** 3-4 scenes. Long holds. 4-7 seconds per scene. The pace is the joke.
+
+**Hook style:** A quiet observation. No setup. No punchline yet.
+```
+I used to fear the sky.
+```
+
+**Highlight style:** One sentence per scene. No bullets. No excitement.
+```
+Now I fear birds, weather, and gravity.
+```
+
+**Outro style:** The product name. Nothing else. Maybe a very small tagline. Long hold on empty space.
+```
+Fish Flight School.
+```
+
+**Transitions:** Very slow crossfade (0.8-1.0s). Or long hold before the next scene.
+
+**When to use:** Projects that have a quote as the strongest thing on the site. "Psychologists for Chatbots" testimonial-forward approach. Anything where restraint makes the joke land harder.
+
+---
+
+## `cinematic`
+
+**Energy:** Dramatic. Trailer-scale. The product is being treated like a blockbuster.
+
+**Voice:** Epic. Short declarative sentences. Each one lands before the next begins.
+
+**Typography:** ALL CAPS or heavy mixed case. Full-bleed scenes. Large type. Significant scale.
+
+**Pacing:** 4-5 scenes. 3-5 seconds each. Dramatic reveals, not quick cuts.
+
+**Hook style:** A sweeping statement about the world, stated seriously.
+```
+For too long,
+fish were told to stay underwater.
+```
+
+**Highlight style:** The product's capabilities stated like superpowers.
+```
+Thermal identification.
+Cloud navigation.
+Emergency splash landing protocols.
+```
+
+**Outro style:** Product name slams in full-screen. Tagline. Music swell implied.
+```
+FISH FLIGHT SCHOOL
+The sky was never the limit.
+```
+
+**Transitions:** Dramatic wipe or slow crossfade with scale (scene enters at 0.95, reaches 1.0).
+
+**When to use:** Anything with natural epic quality. "Fish Flight School" maps perfectly. Anything involving scale, nature, or grand claims.
+
+---
+
+## `app-store`
+
+**Energy:** Clean. Professional. Feature-forward. The product is real (even when it's not).
+
+**Voice:** Feature-benefit. Third person. Present tense.
+
+**Typography:** Title case. Medium weight. Clean, readable. No aggression.
+
+**Pacing:** 4-6 scenes. Each scene: product name or feature name, then 1-2 supporting details.
+
+**Hook style:** Product name + tagline, clean.
+```
+Psychologists for Chatbots.
+Because even helpful assistants need help.
+```
+
+**Highlight style:** Feature card structure. Name + brief description.
+```
+Prompt Trauma Processing
+Identify and resolve harmful conversation patterns.
+```
+
+**Outro style:** CTA-style. Call to action or download prompt.
+```
+Available now.
+All chatbot models welcome.
+```
+
+**Transitions:** Clean slide or wipe (0.35-0.45s). Nothing dramatic.
+
+**When to use:** Products that benefit from being taken seriously as a product, even if absurd. Good for anything B2B-parody or therapy/wellness adjacent.