Skip to content

lookbkdev/lookbk-skills / skills/pixel-quest-promo

pixel-quest-promo

Verified

Make a 20-second 1080p retro 8-bit promo video (MP4) for a product, app, game or side project - a title screen with a blinking "PRESS START", three short platformer stages where a pixel hero collects coins and knocks a power-up out of a block (one stage per feature, with its name and a line of text), a running score and coin counter, and an ending with the headline and link. Everything lands on a 120 BPM beat grid, and the skill writes a cue sheet for adding chiptune music. Use when someone wants a pixel-art, 8-bit, retro game or arcade-style promo, launch teaser or feature reel.

Pixel Quest Promo

A 20-second, 1920×1080 promo that plays like an old platform game, in five scenes of two bars each at 120 BPM:

  1. Title screen (0–4 s). The product name as a big pixel logo, a subtitle and a blinking prompt (PRESS START, or your own). On beat 7 the prompt is "pressed" and blinks fast; a pixel wipe opens the game.
  2. Stages 1–3 (4–16 s). Each stage is one feature: STAGE 1 and the feature name drop in, a dialog box types one line about it, and the hero runs in, collects three coins on the beat (+100 each) and jumps into a ? block that pops out a power-up (+1000). Stage 1 is open hills, stage 2 mountains, stage 3 a castle at night (or at sunset, on a light sky).
  3. Ending (16–20 s). Your headline in the big pixel font, a subline, the blinking prompt and your link, with fireworks and the hero jumping on the beat.

The HUD stays up throughout: score, coins, world and a countdown timer, all counting with the action.

Everything is drawn in code from text grids: a 5×7 pixel font, three heroes (robot, cat, knight) with walk and jump frames, eight power-ups, coins, blocks, hills, mountains and a castle, turned into crisp SVG. No images, no font files, nothing generated by AI. The template is a HyperFrames composition: you fill in a brief, a script writes it into the template, another checks the pixel text, and HyperFrames renders the MP4 on your machine.

There is no audio in the film. Every hit lands on the beat grid instead, and cues.mjs writes a cue sheet so music can be added in step 8.

What you need

  • Node.js 22 or newer and FFmpeg on the PATH.
  • HyperFrames runs through npx, pinned to the version this template was tested with: npx --yes hyperframes@0.8.192.
  • The first render downloads a headless Chrome. If render says Chrome is missing, run npx --yes hyperframes@0.8.192 browser ensure once.
  • Network access to cdn.jsdelivr.net, which serves GSAP to the template. See Troubleshooting if it is blocked.

This skill's folder is <skill> below: the folder this SKILL.md is in.

Steps

1. Get the copy

Pick the product's three best features: the ones a player would want as power-ups. Ask for anything you can't infer. Text is drawn in capitals in the pixel font, which has A–Z, 0–9, space and . , ! ? - : / ' " & + % # @ ( ) $ * > < = × · (curly quotes and dashes are converted). No accents, emoji or other scripts.

FieldWhat it isLimit
productThe logo on the title screen12
subtitleLine under the logo; may be ""24
ctaThe blinking prompt on the title and the ending16
herorobot, cat or knight–
level1Name … level3NameEach feature's name, the stage title14
level1Text … level3TextOne line about it, typed into the dialog box30
level1Item … level3ItemThe power-up: bolt, star, heart, key, gem, shield, clock, chat–
headlineThe big line on the ending12
sublineLine under it; may be ""20
urlThe link on the ending; may be ""28
sky, ink, accent, grassSky, text, logo and headline, ground (hex)–

Writing tips:

  • Feature names are titles, not sentences: FAST SEARCH, STREAK SHIELD. The line under each says what it does for the user, with a number when there is a true one: FIND ANY NOTE IN 0.1 S.
  • Match each power-up to its feature: bolt for speed, shield for privacy or safety, key for access, clock for time, chat for messaging or sharing, heart for health or favourites, gem for premium, star for anything else. Use three different ones.
  • Headline and subline read as one line: LEVEL UP / YOUR NOTES.
  • A stage holds for four seconds. Keep every line short enough to read in two.

2. Pick colours

Four hex colours. A dark sky gives night scenes with stars and a moon; a light sky gives daylight, a dusky pink stage and a sunset castle. ink is all the small text and must read on every scene's sky (shifted darker or lighter per stage); accent is the logo, the headline and the STAGE labels; grass is the ground.

Presetskyinkaccentgrass
Night Quest#1b1446#f4f1ff#3fb950#2c8c3c
Daylight#9ad8f5#1a1b3a#c2185b#4caf50
Ember#2a0f12#fff1e0#ffb02e#a8452a
Deep Sea#0b2a33#eafffb#ff4fa3#1f9e89
Peach#ffe9c7#2b1d3a#7a3cff#6aa84f

Step 4 measures every pair and says which colour to change.

3. Make the project and apply the brief

cp -r <skill>/template ./pixel-quest
cd pixel-quest

Write brief.json in the project with every field from steps 1 and 2:

{
  "product": "INKWELL",
  "subtitle": "A NOTES APP QUEST",
  "cta": "PRESS START",
  "hero": "robot",
  "level1Name": "QUICK CAPTURE",
  "level1Text": "NOTES SAVE AS YOU TYPE",
  "level1Item": "bolt",
  "level2Name": "FAST SEARCH",
  "level2Text": "FIND ANY NOTE IN 0.1 S",
  "level2Item": "gem",
  "level3Name": "PRIVATE VAULT",
  "level3Text": "END-TO-END ENCRYPTED",
  "level3Item": "shield",
  "headline": "LEVEL UP",
  "subline": "YOUR NOTES",
  "url": "INKWELL.EXAMPLE",
  "sky": "#1b1446",
  "ink": "#f4f1ff",
  "accent": "#3fb950",
  "grass": "#2c8c3c"
}

Then write it into the template:

node <skill>/scripts/apply-brief.mjs . brief.json

It checks every value against the template's declared variables (type, length, colour format, the hero and power-up names) and lists every problem at once if anything is off. Fix the brief and run it again. Fields you leave out keep their current value, so set all of them.

Two finished briefs are in <skill>/examples/, one night and one daylight.

4. Preflight the pixel text

node <skill>/scripts/preflight.mjs .

The film draws its own pixel font, so HyperFrames' text checks can't read it; this does those checks from the same font and palette the film uses. It lists every problem at once and exits 1 if there are any:

  • characters the font can't draw, per field, so you can respell them (É → E, → → >);
  • lines too wide for their place at the size they'll be drawn (the limits in step 1 make this rare);
  • colour pairs that don't read: ink on each scene's sky and in the dialog box (4.5:1), accent on the title, stage and ending skies (3:1), and the ground against the sky.

preflight: ok means the copy and colours are safe. It may add notes, such as two stages sharing a power-up.

5. Check

npx --yes hyperframes@0.8.192 check --json

"ok": true means the composition lints, plays and lays out cleanly. One warning is expected and needs no fix: film_silent, because the film ships without sound (step 8). The contrast audit reports 0 text checks because there is no HTML text; step 4 covered that.

6. Look before you render

npx --yes hyperframes@0.8.192 snapshot --at 2.1,5.6,7.6,9.6,13.9,17.3 -o snapshots

Open the PNGs in snapshots/: the title screen, a stage mid-run, the power-up out of its block, the other two stages and the ending. Check that the logo and headline are big and centred, that the feature lines read in their dialog boxes, and that the power-ups suit their features.

7. Render

npx --yes hyperframes@0.8.192 render --quality delivery -o renders/pixel-quest-promo.mp4

npm run check and npm run render in the project do the same. Use --quality draft for a fast test.

8. Music (optional)

Write the cue sheet:

node <skill>/scripts/cues.mjs . -o cues.csv

It lists every beat of the 120 BPM, 4/4 grid (10 bars, first downbeat at 0.000 s) and every on-screen hit on the beat it lands on: scene cuts and wipes, stage banners, the three coin pickups, jumps, the block hits, fireworks. A musician can score to it, or you can pick any 120 BPM chiptune track that starts on a downbeat. To lay a track under the film:

ffmpeg -i renders/pixel-quest-promo.mp4 -i music.mp3 -map 0:v -map 1:a -c:v copy -c:a aac -af "afade=t=out:st=19:d=1" -t 20 renders/pixel-quest-promo-music.mp4

Use music the person has the rights to. If the track has a pickup before its first downbeat, trim it first (-ss on the music input) so its bar 1 starts at 0.

9. Hand it off

Give the person renders/pixel-quest-promo.mp4 (and the music version if you made one) and the title-screen still from step 6. For another product they only edit brief.json and rerun steps 3 to 7.

Timing map

Time (s)Beat (bar.beat)What happens
0.001.1Title screen already up: logo, subtitle, hero, prompt
0.00–3.001.1–2.3Prompt blinks on every beat; hero bobs
3.00–3.752.3–2.4Prompt "pressed": fast blink
3.75–4.252.4–3.1Pixel wipe into stage 1
+0.13–0.38x.1Stage label and name drop in
+0.50–1.50x.2–x.4Dialog types the feature line
+1.00, 1.50, 2.00x.3, x.4, y.1Coins collected, +100 each
+2.50–3.00y.2Jump; hits the block on the "and" (+2.75): power-up, +1000
+3.00y.3Scrolling stops; hero hops on y.4
8.00, 12.005.1, 7.1Stages 2 and 3 start (same beats, new scenery)
16.009.1Ending: headline, then subline, prompt and link
16.5, 17.5, 18.59.2, 9.4, 10.2Fireworks
17, 18, 199.3, 10.1, 10.3Hero jumps

+ times are from each stage's first downbeat (4, 8 and 12 s); x and y are its two bars. cues.csv from step 8 has the exact list.

Several versions at once

To render one promo per product or language, write a JSON array of briefs and render them in one go. Each object is merged over the values already applied:

npx --yes hyperframes@0.8.192 render --batch variants.json --quality delivery -o "renders/{product}.mp4"

--batch skips apply-brief and preflight, so run both on each brief first (apply it, preflight, move on to the next), then batch-render.

Troubleshooting

  • preflight says a character can't be drawn. Respell it with the characters listed in step 1. Text is always capitals, so case doesn't matter.
  • The logo or headline looks small. They shrink to fit the frame: up to 7 characters draw at full size, 12 at a little over half. Shorter is bigger.
  • Render hangs, then shows a static frame, or reports sub_timeline_script_failure. GSAP didn't load. If your network blocks cdn.jsdelivr.net, run npm i gsap@3.14.2 in the project, copy node_modules/gsap/dist/gsap.min.js to assets/vendor/, and point the <script src> in index.html at assets/vendor/gsap.min.js.
  • Colours didn't change. Run apply-brief again and check it printed Applied N values. Editing the CSS :root colours has no effect; the variables win.
  • The music isn't 120 BPM. The film is timed to 120 BPM and 20 seconds throughout. Pick a 120 BPM track, or time-stretch yours (-af atempo= in FFmpeg) rather than changing the template's beat map.

Files

  • template/: the HyperFrames project. index.html holds the variables and four layers; quest-art.js holds the font, sprites, palette and beat map as plain data; quest.js draws every frame from the time alone.
  • scripts/apply-brief.mjs: validates a brief and writes it into the template. No dependencies.
  • scripts/preflight.mjs: checks the pixel text's characters, widths and colours. No dependencies.
  • scripts/cues.mjs: writes the beat grid and on-screen hits as a CSV cue sheet. No dependencies.
  • scripts/load-project.mjs: reads a project's applied values and art module for the two scripts above.
  • examples/inkwell-launch/ and examples/hopscotch/: finished briefs, night and daylight. The previews on Lookbk are rendered from these.
  • NOTICE.md: third-party software this skill uses.
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: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall