Skip to content

armgit / brag

Public Imported from GitHub
0

You built it. Now brag. Turn the project you just created into a short, shareable launch video with one command.

Adapt brag skill to HyperFrames 0.7.64

shunithaviv29008c8335c8
diff --git a/skills/brag/SKILL.md b/skills/brag/SKILL.md
index 1e6821c..d0cb3ee 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` skill (all rules apply)
+**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:** [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 lint` passes with zero errors inside `<output-dir>/composition/`.
+**Gate:** `npx hyperframes check` passes with zero errors inside `<output-dir>/composition/` (the browser gate reruns lint and audits runtime, layout, motion, and contrast).
---
diff --git a/skills/brag/references/audio.md b/skills/brag/references/audio.md
index f8c882d..e49097c 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 current hyperframes audio-reactive workflow (its `references/audio-reactive.md`) to extract per-frame audio data and sample it synchronously inside the composition timeline. The extraction helper ships with the Hyperframes/GSAP skills — `/brag` does not provide it, so don't hardcode a path to it.
+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.
---
diff --git a/skills/brag/references/step-1-inspect.md b/skills/brag/references/step-1-inspect.md
index b7240a9..4bcf25f 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 carry into the Hyperframes composition's DESIGN.md.
+These colors are recorded in `composition-brief.md` and carry into the Hyperframes design spec (`frame.md`).
## Font extraction
diff --git a/skills/brag/references/step-3-compose.md b/skills/brag/references/step-3-compose.md
index 80c123e..f559506 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
-Use the current `hyperframes` skill and CLI workflow. 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 to `/product-launch-video`. 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 lint and validate before render.
+- Run `hyperframes check` before render — check is the single gate and reruns lint.
```
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.
@@ -121,7 +121,7 @@ Run `npx hyperframes tts --list` to see other voices.
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-duration="auto" data-track-index="3" data-volume="1" src="assets/voiceover.wav"></audio>
+<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.
@@ -132,7 +132,7 @@ Scene durations must flex to match the generated audio — check the WAV duratio
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** — `/brag` does not ship an extraction script and must not hardcode a path to one.
-In the composition step, follow `references/audio-reactive.md` in the current hyperframes skill. It owns the data format, the extraction helper (which ships with the Hyperframes/GSAP skills, not with `/brag`), 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 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.
If extraction is unavailable (no helper, or ffmpeg missing), note it in the brief and skip audio-reactive — do not block the render.
@@ -173,10 +173,10 @@ If SFX are enabled, also pass `skills/brag/assets/sfx/sfx-analysis.md` as select
After `brag-output/brag-plan.md`, `brag-output/composition-brief.md`, and selected audio assets exist:
-1. Use the `hyperframes` skill to create or update `brag-output/composition/`.
+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`.
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 lint and validate.
+4. Run Hyperframes check (it reruns lint).
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.
@@ -196,4 +196,4 @@ Before moving to delivery, verify:
- [ ] 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 lint and validate pass, or any blocker is documented for the user.
+- [ ] Hyperframes check passes, or any blocker is documented for the user.
diff --git a/skills/brag/references/step-4-deliver.md b/skills/brag/references/step-4-deliver.md
index 4d9b7dd..790eca8 100644
--- a/skills/brag/references/step-4-deliver.md
+++ b/skills/brag/references/step-4-deliver.md
@@ -4,12 +4,10 @@
```bash
cd brag-output/composition
-npx hyperframes lint # static checks: track overlaps, unregistered timelines, missing ids
-npx hyperframes validate # loads in headless Chrome: WCAG contrast audit + console errors
-npx hyperframes inspect # text / container overflow across the timeline
+npx hyperframes check # one browser gate: reruns lint, then audits runtime, layout/overflow, motion, and WCAG contrast
```
-Fix all errors. The contrast warnings come from `validate` (`lint` is static-only): fix anything below 3:1 for large text or 4.5:1 for body text. Accept borderline cases (3:1–4:1) — brag videos are not accessibility documents, but text must be legible. `inspect` backstops the "keep all text readable" creative law — fix any reported overflow.
+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.
For a visual gut-check before rendering, optionally capture key frames:
@@ -158,7 +156,7 @@ brag-output/
share-copy.txt — the share caption
composition/ — the Hyperframes project
index.html
- DESIGN.md
+ frame.md
...
```