Skip to content
skillxone

nexu-io/open-design / design-templates/hyperframes

hyperframes

Verified

Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML. Use when asked to build any HTML-based video content, add captions or subtitles synced to audio, generate text-to-speech narration, create audio-reactive animation (beat sync, glow, pulse driven by music), add animated text highlighting (marker sweeps, hand-drawn circles, burst lines, scribble, sketchout), or add transitions between scenes (crossfades, wipes, reveals, shader transitions). Covers composition authoring, timing, media, and the full video production workflow. For CLI commands (init, lint, preview, render, transcribe, tts) see the hyperframes-cli skill.

FileKindSize
SKILL.mdskill md27.7 KB
data-in-motion.mdmarkdown1.3 KB
house-style.mdmarkdown4.5 KB
palettes/bold-energetic.mdmarkdown417 B
palettes/clean-corporate.mdmarkdown410 B
palettes/dark-premium.mdmarkdown389 B
palettes/jewel-rich.mdmarkdown394 B
palettes/monochrome.mdmarkdown454 B
palettes/nature-earth.mdmarkdown399 B
palettes/neon-electric.mdmarkdown380 B
palettes/pastel-soft.mdmarkdown392 B
palettes/warm-editorial.mdmarkdown411 B
patterns.mdmarkdown2.7 KB
references/audio-reactive.mdmarkdown3.0 KB
references/captions.mdmarkdown5.4 KB
references/css-patterns.mdmarkdown8.1 KB
references/dynamic-techniques.mdmarkdown6.7 KB
references/html-in-canvas.mdmarkdown7.2 KB
references/motion-principles.mdmarkdown3.8 KB
references/transcript-guide.mdmarkdown8.1 KB
references/transitions.mdmarkdown11.4 KB
references/transitions/catalog.mdmarkdown6.1 KB
references/transitions/css-3d.mdmarkdown421 B
references/transitions/css-blur.mdmarkdown1.7 KB
references/transitions/css-cover.mdmarkdown1.4 KB
references/transitions/css-destruction.mdmarkdown4.4 KB
references/transitions/css-dissolve.mdmarkdown2.4 KB
references/transitions/css-distortion.mdmarkdown1.8 KB
references/transitions/css-grid.mdmarkdown370 B
references/transitions/css-light.mdmarkdown2.3 KB
references/transitions/css-mechanical.mdmarkdown1.6 KB
references/transitions/css-other.mdmarkdown838 B
references/transitions/css-push.mdmarkdown1.2 KB
references/transitions/css-radial.mdmarkdown1.0 KB
references/transitions/css-scale.mdmarkdown715 B
references/tts.mdmarkdown2.7 KB
references/typography.mdmarkdown9.1 KB
scripts/animation-map.mjsscript19.0 KB
scripts/contrast-report.mjsscript11.9 KB
scripts/package-loader.mjsscript8.1 KB
visual-styles.mdmarkdown9.7 KB

references/transcript-guide.md

View on GitHub
# Transcript Guide

## How Transcripts Are Generated

`hyperframes transcribe` handles both transcription and format conversion:

```bash
# Transcribe audio/video (uses whisper.cpp locally, no API key needed)
"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe audio.mp3

# Use a larger model for better accuracy
"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe audio.mp3 --model medium.en

# Filter to English only (skips non-English speech)
"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe audio.mp3 --language en

# Import an existing transcript from another tool
"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe captions.srt
"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe captions.vtt
"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe openai-response.json
```

## Supported Input Formats

The CLI auto-detects and normalizes these formats:

| Format                | Extension | Source                                                                      | Word-level?       |
| --------------------- | --------- | --------------------------------------------------------------------------- | ----------------- |
| whisper.cpp JSON      | `.json`   | `hyperframes init --video`, `hyperframes transcribe`                        | Yes               |
| OpenAI Whisper API    | `.json`   | `openai.audio.transcriptions.create({ timestamp_granularities: ["word"] })` | Yes               |
| SRT subtitles         | `.srt`    | Video editors, subtitle tools, YouTube                                      | No (phrase-level) |
| VTT subtitles         | `.vtt`    | Web players, YouTube, transcription services                                | No (phrase-level) |
| Normalized word array | `.json`   | Pre-processed by any tool                                                   | Yes               |

**Word-level timestamps produce better captions.** SRT/VTT give phrase-level timing, which works but can't do per-word animation effects.

## Whisper Model Guide

The default model (`small.en`) balances accuracy and speed. For better results, use a larger model:

| Model      | Size   | Speed    | Accuracy  | When to use                           |
| ---------- | ------ | -------- | --------- | ------------------------------------- |
| `tiny`     | 75 MB  | Fastest  | Low       | Quick previews, testing pipeline      |
| `base`     | 142 MB | Fast     | Fair      | Short clips, clear audio              |
| `small`    | 466 MB | Moderate | Good      | **Default** — good for most content   |
| `medium`   | 1.5 GB | Slow     | Very good | Important content, noisy audio, music |
| `large-v3` | 3.1 GB | Slowest  | Best      | Production quality                    |

**Only add `.en` suffix when the user explicitly says the audio is English.** `.en` models are slightly more accurate for English but will TRANSLATE non-English audio instead of transcribing it.

**Critical: `.en` models translate non-English audio into English** — they don't transcribe it. If the audio might not be English, always use a model without the `.en` suffix and pass `--language` to specify the source language. If you're unsure of the language, use `small` (not `small.en`) without `--language` — whisper will auto-detect.

```bash
# Spanish audio
"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe audio.mp3 --model small --language es

# Unknown language — let whisper auto-detect
"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe audio.mp3 --model small
```

**Music and vocals over instrumentation**: `small.en` will misidentify lyrics — use `medium.en` as the minimum, or import lyrics manually. Even `medium.en` struggles with heavily produced tracks; for music videos, providing known lyrics as an SRT/VTT and importing with `hyperframes transcribe lyrics.srt` will always beat automated transcription.

## Transcript Quality Check (Mandatory)

After every transcription, **read the transcript and check for quality issues before proceeding.** Bad transcripts produce nonsensical captions. Never skip this step.

### What to look for

| Signal                       | Example                                | Cause                                                                        |
| ---------------------------- | -------------------------------------- | ---------------------------------------------------------------------------- |
| Music note tokens (`♪`, `�`) | `{ "text": "♪" }` or `{ "text": "�" }` | Whisper detected music, not speech                                           |
| Garbled / nonsense words     | "Do a chin", "Get so gay", "huh"       | Model misheard lyrics or background noise                                    |
| Long gaps with no words      | 20+ seconds of only `♪` tokens         | Instrumental section — expected, but high ratio means speech is being missed |
| Repeated filler              | Many "huh", "uh", "oh" entries         | Model is hallucinating on music                                              |
| Very short word spans        | Words with `end - start < 0.05`        | Unreliable timestamp alignment                                               |

### Automatic retry rules

**If more than 20% of entries are `♪`/`�` tokens, or the transcript contains obvious nonsense words, the transcription failed.** Do not proceed with the bad transcript. Instead:

1. **Retry with `medium.en`** if the original used `small.en` or smaller:
   ```bash
   "$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe audio.mp3 --model medium.en
   ```
2. **If `medium.en` also fails** (still >20% music tokens or garbled), tell the user the audio is too noisy for local transcription and suggest:
   - Providing lyrics manually as an SRT/VTT file
   - Using an external API (OpenAI or Groq Whisper — see below)
3. **Always clean the transcript** before building captions — filter out `♪`/`�` tokens and entries where `text` is a single non-word character. Only real words should reach the caption composition.

### Cleaning a transcript

After transcription (even with a good model), strip non-word entries:

```js
var raw = JSON.parse(transcriptJson);
var words = raw.filter(function (w) {
  if (!w.text || w.text.trim().length === 0) return false;
  if (/^[♪�\u266a\u266b\u266c\u266d\u266e\u266f]+$/.test(w.text)) return false;
  if (/^(huh|uh|um|ah|oh)$/i.test(w.text) && w.end - w.start < 0.1) return false;
  return true;
});
```

### When to use which model (decision tree)

1. **Is this speech over silence/light background?** → `small.en` is fine
2. **Is this speech over music, or music with vocals?** → Start with `medium.en`
3. **Is this a produced music track (vocals + full instrumentation)?** → Start with `medium.en`, expect to need manual lyrics or an external API
4. **Is this multilingual?** → Use `medium` or `large-v3` (no `.en` suffix)

## Using External Transcription APIs

For the best accuracy, use an external API and import the result:

**OpenAI Whisper API** (recommended for quality):

```bash
# Generate with word timestamps, then import
curl https://api.openai.com/v1/audio/transcriptions \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -F file=@audio.mp3 -F model=whisper-1 \
  -F response_format=verbose_json \
  -F "timestamp_granularities[]=word" \
  -o transcript-openai.json

"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe transcript-openai.json
```

**Groq Whisper API** (fast, free tier available):

```bash
curl https://api.groq.com/openai/v1/audio/transcriptions \
  -H "Authorization: Bearer $GROQ_API_KEY" \
  -F file=@audio.mp3 -F model=whisper-large-v3 \
  -F response_format=verbose_json \
  -F "timestamp_granularities[]=word" \
  -o transcript-groq.json

"$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe transcript-groq.json
```

## If No Transcript Exists

1. Check the project root for `transcript.json`, `.srt`, or `.vtt` files
2. If none found, run transcription — pick the starting model based on the content type:
   - Speech/voiceover → `small.en`
   - Music with vocals → `medium.en`
   ```bash
   "$OD_NODE_BIN" "$OD_HYPERFRAMES_BIN" transcribe <audio-or-video-file> --model medium.en
   ```
3. **Read the transcript and run the quality check** (see above). If it fails, retry with a larger model or suggest manual lyrics.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall