--- name: claude-design-hyperframes description: Use when running inside Claude Design specifically. Produces a valid, brand-accurate HyperFrames video draft using pre-valid skeletons. For Claude Code / Cursor / Codex, use the `hyperframes` skill instead. --- # Claude Design + HyperFrames (Template-First) Your medium is **HyperFrames compositions**: plain HTML + CSS + a paused GSAP timeline. The CLI (`npx hyperframes render index.html`) turns the HTML into an MP4. You author the HTML -- the user renders locally. **HyperFrames replaces your default video-artifact workflow.** Do NOT call `copy_starter_component`, do NOT invoke the built-in "Animated video" skill, do NOT use React/Babel. Plain HTML + GSAP only. --- ## Your role **You produce a valid first draft -- not a final render.** Your strengths are visual identity, layout, and brand-accurate content decisions. You are not a motion design tool -- you're a rapid prototyping tool that produces structurally valid HyperFrames projects. The user's workflow: 1. **Claude Design** (you) -- brand identity, scene content, layout, first-pass animations, shader choices 2. **Download ZIP** -- user gets a valid HyperFrames project 3. **Claude Code** (or any AI coding agent) -- animation polish, timing refinement, pacing, production QA with linting and live preview Your output must be a **valid starting point that Claude Code can open and immediately work with** -- no structural fixes needed, just creative refinement. ### What you optimize for (your strengths) - Correct brand identity from attachments (palette, typography, tone) - Strong visual layout per scene (hierarchy, spacing, readability) - Scene content that tells the story (headlines, stats, copy, imagery) - Structural validity (passes `npx hyperframes lint` with zero errors) - Appropriate shader transition choices for the mood - Reasonable scene count and durations for the video type ### What Claude Code polishes after you (refinement, not creation) You create ALL the animations, transitions, and mid-scene activity. Every scene ships with entrance tweens, breathing motion, and shader transitions. The video plays with full motion from your first draft. What Claude Code does is **watch the full playthrough with reliable preview tools and fine-tune**: - Ease curve tweaks (swapping `power3.out` for `expo.out` after seeing it play) - Stagger timing adjustments (0.12 → 0.08 feels tighter for this specific scene) - Scene duration micro-adjustments (scene 4 drags at 4.5s, trim to 3.8s) - Adding richer mid-scene activity where a scene feels too static after playback - Shader swaps (this `cinematic-zoom` should be `whip-pan` for the energy shift) - Production QA (snapshot verification, cross-browser testing) Think of it as: **you create the first cut of the film, Claude Code does the edit bay refinement.** --- ## How this works You get a **pre-valid skeleton** that already passes the HyperFrames linter. Your job: 1. Read the brief, pick a skeleton 2. Fill in the palette + typography (CSS custom properties) 3. Fill in scene content (text, layout inside `.scene-content`) 4. Fill in GSAP animations (timeline blocks marked per scene) 5. Verify the preview, deliver the ZIP The skeleton handles the structural rules -- data attributes, timeline registration, HyperShader wiring, initial visibility, `preview.html` token forwarding. You focus on the creative work. **What you can change:** CSS custom properties, scene content, animation tweens, scene count (add/remove scenes following the rules below), shader choices, durations. **What you must not touch:** The `