Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.
TypeScript ai-sdkclaude-codeclicode-searchcodexcoding-agentscontext-retrievaldeveloper-toolsjevsemantic-searchtypescriptvercel-ai-gateway
skills: make launch-video standalone
David Zhang80a216bfa0bf
diff --git a/.agents/skills/launch-video/SKILL.md b/.agents/skills/launch-video/SKILL.mdindex 7bfba76..ba7ef3d 100644--- a/.agents/skills/launch-video/SKILL.md+++ b/.agents/skills/launch-video/SKILL.md@@ -7,9 +7,8 @@ description: Produce a professional, beat-locked motion-graphics launch video (sBuild a ~30s showreel entirely in code: Remotion scenes plus a soundtracksynthesized from the same **cue sheet**, so every hit on screen lands on a hit in-the mix. The bar is a real production, not a demo or prototype. Read-[references/brief.md](references/brief.md) first: the quality bar and the-feedback that shaped this workflow.+the mix. The bar is a designer's showreel, not a demo or prototype: dense,+juicy motion that a technical audience can also learn the mechanism from.## Workflow@@ -23,16 +22,17 @@ feedback that shaped this workflow.every scene change on a bar line. Write one module holding every event time(scene starts, word reveals, stamps, typing, impacts, risers); scenes and themusic both import it. Arc that works: problem cold open → drop + product- reveal with a real command (the README's first example) → behind-the-scenes mechanism → the engine/model →- proof number (breakdown, riser, slam) → lockup with install command. Done when- every visual event has a cue and every cue has a sound.+ reveal with a real command (the README's first example) → behind-the-scenes+ mechanism → the engine/model → proof number (breakdown, riser, slam) → lockup+ with install command. Done when every visual event has a cue and every cue+ has a sound.3. **Synthesize the soundtrack from the cue sheet.** Kick, clap, hats, sidechainedbass/pad/arp on a chord progression; builds into drops; a sound for each UIevent (pop, tick, key click, ✓ blip, ✗ thud, whoosh, impact, ding). Master toroughly −11 to −14 LUFS. You cannot listen: verify with ffmpeg `ebur128` and a`showspectrumpic` spectrogram that risers and impacts sit at cue times, andsay in the handoff that the audio was checked by measurement, not by ear.- Default style unless the brief says otherwise: bright electronic (synth-pop /+ Default style unless the user asks otherwise: bright electronic (synth-pop /future bass).4. **Build the scenes** under the motion rules below. Drive them from absolutetime in seconds, not frames, so cue values stay literal.diff --git a/.agents/skills/launch-video/references/brief.md b/.agents/skills/launch-video/references/brief.mddeleted file mode 100644index 0220f80..0000000--- a/.agents/skills/launch-video/references/brief.md+++ /dev/null@@ -1,38 +0,0 @@-# Brief and feedback--The quality bar for a launch video, and the corrections that shaped this skill.-Treat each correction as a failure mode to avoid on the first pass.--## Brief--> Make a dynamic ~30-second motion graphics video that shows what an incredible-> motion designer you are, like it's your showreel for a résumé. Go all out.-> Introduce the project: its purpose, visuals of how it works behind the scenes-> (the audience is technical), the models or engines it relies on and why they-> matter, and its headline measured result. It must have music, and the motion-> must match the music. Make it a real professional production, not a demo or-> prototype. Favor more animation and motion design; never use screenshots raw.-> Break them down into components and icons so those animate too. Make the-> motion juicy, using the best motion design techniques available.--## Feedback, in order--1. **Preview showed a near-empty frame.** The social upload preview showed the- cold open's first sparse frames. Tell: the thumbnail is blank or nearly blank.-2. **A single poster frame at frame 0 was not enough.** The feed still showed a- frame a few frames in. Tell: a one-frame poster is skipped; the thumbnail- needs a hold.-3. **Dark poster before a light opening.** Keep the pre-roll on the opening's- background so playback does not start with a flash.-4. **The product in action beats a stats slide as the preview.** The preferred- thumbnail was the reveal frame (logo, tagline, terminal with a finished- command and its output), not the benchmark key art. The key art stays useful- as a README image.-5. **Keep the source.** The render project belongs in the repo, not a scratch- directory.--## What landed well--A problem cold open, a beat drop into the logo reveal, a dark behind-the-scenes-section built from animated icons, a slam on the headline number with its-disclosure intact, and a lockup with the install command.