You built it. Now brag. Turn the project you just created into a short, shareable launch video with one command.
Keep a brag run local and never publish
Hessabi3713b9e9d0c2
diff --git a/skills/brag/references/step-3-compose.md b/skills/brag/references/step-3-compose.mdindex b54c94c..d3bb7e5 100644--- a/skills/brag/references/step-3-compose.md+++ b/skills/brag/references/step-3-compose.md@@ -85,6 +85,7 @@ Requirements:- 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 brag's single gate.+- `/brag` renders locally only. Never run `hyperframes publish` or `hyperframes auth` as part of a brag run: publishing the composition is the user's own explicit decision.```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.@@ -189,6 +190,7 @@ After `<output-dir>/brag-plan.md`, `<output-dir>/composition-brief.md`, and sele3. Let Hyperframes choose the implementation details.4. Run Hyperframes check (the single gate before render).5. Render to `<output-dir>/brag.mp4`.+6. Render locally only. Never run `hyperframes publish` or `hyperframes auth`: publishing is the user's own explicit decision, not part of a brag run.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.