You built it. Now brag. Turn the project you just created into a short, shareable launch video with one command.
Generalize hyperframes references for forward-compatibility
shunithaviv5170d0c8e64a
diff --git a/skills/brag/SKILL.md b/skills/brag/SKILL.mdindex d0cb3ee..905d277 100644--- a/skills/brag/SKILL.md+++ b/skills/brag/SKILL.md@@ -85,7 +85,7 @@ When music is selected, include a compact `Music cue guidance` section: read the## Step 3: Hand off to Hyperframes-**Read:** The Hyperframes domain skills — `hyperframes-core`, `hyperframes-animation`, `hyperframes-creative`, `hyperframes-keyframes`, `hyperframes-cli`. /brag is its own workflow: do not enter the `hyperframes` entry-point intent interview or route to `/product-launch-video`.+**Read:** The Hyperframes domain skills — `hyperframes-core`, `hyperframes-animation`, `hyperframes-creative`, `hyperframes-keyframes`, `hyperframes-cli`. /brag is its own workflow: do not enter the `hyperframes` entry-point intent interview or route into its generic promo / launch-video workflow.**Read:** [references/step-3-compose.md](references/step-3-compose.md)**Read:** [references/audio.md](references/audio.md)@@ -93,7 +93,7 @@ Write the composition brief and use Hyperframes to create the video implementati`/brag` owns the product angle, source material, storyboard, tone, format, audio selection, music cue guidance, and delivery expectations. Hyperframes owns the concrete composition structure, exact animation timing, animation mechanics, runtime choices, linting rules, and render workflow.-**Gate:** `npx hyperframes check` passes with zero errors inside `<output-dir>/composition/` (the browser gate reruns lint and audits runtime, layout, motion, and contrast).+**Gate:** `npx hyperframes check` passes with zero errors inside `<output-dir>/composition/` (the single browser gate before render — see hyperframes-cli for what it audits).---diff --git a/skills/brag/references/audio.md b/skills/brag/references/audio.mdindex e49097c..c7a504a 100644--- a/skills/brag/references/audio.md+++ b/skills/brag/references/audio.md@@ -27,7 +27,7 @@ Suggested plan notation:Audio-reactive treatment: subtle; use music RMS/bass to make the hero glow and product card presence breathe. No waveform/equalizer visuals.```-Hyperframes implementation note: follow the Hyperframes audio-reactive workflow, owned by the `hyperframes-creative` skill (`references/audio-reactive.md` and `scripts/extract-audio-data.py`), to extract per-frame audio data and sample it synchronously inside the composition timeline. The extraction helper ships with that skill — `/brag` does not provide it, so don't hardcode a path to it.+Hyperframes implementation note: follow the audio-reactive guidance owned by the `hyperframes-creative` skill (let that skill locate its own files), to extract per-frame audio data and sample it synchronously inside the composition timeline. The extraction helper ships with that skill — `/brag` does not provide it, so don't hardcode a path to it.---@@ -273,7 +273,7 @@ This is the fallback when `hyperframes beats` (option 3) is unavailable — e.g.npx hyperframes beats <output-dir>/composition```-It writes `beats/<audio>.json` = `{ version, audio, beats: [{ time, strength }] }` — a beat grid with a per-beat `strength` (0-1). There is no `strongCues` array; derive "strong" beats by taking the highest-`strength` ones. `beats` was added in Hyperframes 0.6.99; on an older pinned install it won't exist — fall back to option 2 (the script), or to the `unavailable` note below.+It writes a per-track beat file: a beat grid with per-beat timing and a normalized `strength` (0-1), but no separate `strongCues` array — so derive "strong" beats by taking the highest-`strength` ones. (See the current hyperframes-cli `beats` guidance for the exact output path.) `beats` was added in Hyperframes 0.6.99; on an older pinned install it won't exist — fall back to option 2 (the script), or to the `unavailable` note below.The preset and `analyze_music_cues.py` share the rich schema:@@ -282,7 +282,7 @@ The preset and `analyze_music_cues.py` share the rich schema:- `strongCues`: highest-value landing moments with `time`, `intensity`, and `kind` (`strong_beat` / `onset_peak`)- `scoring`: feature and normalization metadata-`hyperframes beats` is the simpler floor: `beats[]` with `{ time, strength }` only.+`hyperframes beats` is the simpler floor: a plain beat grid with a per-beat strength, no strong-cue array.Planning rules (apply to whichever source you have):diff --git a/skills/brag/references/step-1-inspect.md b/skills/brag/references/step-1-inspect.mdindex 4bcf25f..5d948de 100644--- a/skills/brag/references/step-1-inspect.md+++ b/skills/brag/references/step-1-inspect.md@@ -104,7 +104,7 @@ Write down:- Accent/brand color- Any gradient or special treatment-These colors are recorded in `composition-brief.md` and carry into the Hyperframes design spec (`frame.md`).+These colors are recorded in `composition-brief.md` and carry into the design spec the current hyperframes-creative workflow scaffolds.## Font extractiondiff --git a/skills/brag/references/step-3-compose.md b/skills/brag/references/step-3-compose.mdindex f559506..3bcac47 100644--- a/skills/brag/references/step-3-compose.md+++ b/skills/brag/references/step-3-compose.md@@ -70,7 +70,7 @@ Scene summary:- Audio files: copy the chosen music and any Hyperframes-selected SFX into `brag-output/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). /brag is its own workflow: do not enter the `hyperframes` entry-point intent interview and do not route to `/product-launch-video`. Prefer native Hyperframes conventions over anything in `/brag`.+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). /brag 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 `/brag`.Requirements:- Show at least one real UI, copy, or visual element from the source project.@@ -84,7 +84,7 @@ Requirements:- 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 — check is the single gate and reruns lint.+- Run `hyperframes check` before render — it is brag's single gate.```The brief is the boundary: if a detail belongs to product positioning, copy, tone, source material, or selection of moments, `/brag` should specify it. If a detail belongs to composition implementation, Hyperframes should decide it.@@ -132,7 +132,7 @@ Scene durations must flex to match the generated audio — check the WAV duratioWhen 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** — `/brag` does not ship an extraction script and must not hardcode a path to one.-In the composition step, follow the Hyperframes audio-reactive workflow, owned by the `hyperframes-creative` skill (`references/audio-reactive.md` and `scripts/extract-audio-data.py`). It owns the data format, the extraction helper (which ships with that skill, not with `/brag`, 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.+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 `/brag`, 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.@@ -148,9 +148,9 @@ Get a cue source first (see `audio.md` → "Beat and cue sources"): a bundled pr### How to implement**Major moments (strong cues):**-1. Load the cue source: the preset/analysis JSON (`strongCues` + `beats`), or `beats/<audio>.json` from `hyperframes beats` (`beats` only).+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. Adjust the GSAP tween start time to land within ±0.15s of the cue.+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):**@@ -173,10 +173,10 @@ If SFX are enabled, also pass `skills/brag/assets/sfx/sfx-analysis.md` as selectAfter `brag-output/brag-plan.md`, `brag-output/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 `brag-output/composition/`. /brag is its own workflow — do not enter the `hyperframes` entry-point intent interview or route to `/product-launch-video`.+1. Load the Hyperframes domain skills (`hyperframes-core`, `hyperframes-animation`, `hyperframes-creative`, `hyperframes-keyframes`, `hyperframes-cli`) to create or update `brag-output/composition/`. /brag 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 brag plan, and the source files it should reference.3. Let Hyperframes choose the implementation details.-4. Run Hyperframes check (it reruns lint).+4. Run Hyperframes check (the single gate before render).5. Render to `brag-output/brag.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.diff --git a/skills/brag/references/step-4-deliver.md b/skills/brag/references/step-4-deliver.mdindex 790eca8..cf6111b 100644--- a/skills/brag/references/step-4-deliver.md+++ b/skills/brag/references/step-4-deliver.md@@ -4,15 +4,15 @@```bashcd brag-output/composition-npx hyperframes check # one browser gate: reruns lint, then audits runtime, layout/overflow, motion, and WCAG contrast+npx hyperframes check # brag's single pre-render gate — fix every error it reports```-Fix all errors. `check` is the single gate — it reruns lint, so don't add a standalone `lint` before it. WCAG contrast failures are gating **errors** (4.5:1 for normal text, 3:1 for large text — 24px+, or 19px+ bold), not warnings. Each finding carries the sampled fg/bg colors, the measured-vs-required ratio, and a `suggestedColor` in the right palette direction — apply it or adjust within the palette family, then re-run `check`; most fixes need no screenshot. There is no per-element contrast escape hatch for real text (the `data-layout-allow-*` hatches cover overflow / overlap / occlusion only). The only bypass is `check --no-contrast`, which skips the entire WCAG pass (all-or-nothing) — not a way to accept one borderline element. `check`'s layout pass backstops the "keep all text readable" creative law — fix any reported overflow.+Fix all errors. `check` is brag's 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 (adds Gemini frame analysis when GEMINI_API_KEY is set)+npx hyperframes snapshot # PNG key frames```## Preview@@ -21,7 +21,7 @@ npx hyperframes snapshot # PNG key frames (adds Gemini frame analysis when GEMnpx hyperframes preview```-Tell the user the preview is running and give them the localhost URL. Invite them to check it before rendering. The preview hot-reloads on file changes.+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:@@ -156,7 +156,6 @@ brag-output/share-copy.txt — the share captioncomposition/ — the Hyperframes projectindex.html- frame.md...```