website-to-hyperframes
Capture a website and create a HyperFrames video from it. Use when: (1) a user provides a URL and wants a video, (2) someone says "capture this site", "turn this into a video", "make a promo from my site", (3) the user wants a social ad, product tour, or any video based on an existing website, (4) the user shares a link and asks for any kind of video content. Even if the user just pastes a URL — this is the skill to use.
What this skill does
# Website to HyperFrames Capture a website, then produce a professional video from it. Users say things like: - "Capture https://... and make me a 25-second product launch video" - "Turn this website into a 15-second social ad for Instagram" - "Create a 30-second product tour from https://..." The workflow has 7 steps. Each produces an artifact that gates the next. --- ## Step 1: Capture & Understand **Read:** [references/step-1-capture.md](references/step-1-capture.md) Run the capture, read the extracted data, and build a working summary using the write-down-and-forget method. **Gate:** Print your site summary (name, top colors, fonts, key assets, one-sentence vibe). --- ## Step 2: Write DESIGN.md **Read:** [references/step-2-design.md](references/step-2-design.md) Write a simple brand reference for the captured website. 6 sections, ~90 lines. This is a cheat sheet, not the creative plan — that comes in Step 4. **Gate:** `DESIGN.md` exists in the project directory. --- ## Step 3: Write SCRIPT **Read:** [references/step-3-script.md](references/step-3-script.md) Write the narration script. The story backbone. Scene durations come from the narration, not from guessing. **Gate:** `SCRIPT.md` exists in the project directory. --- ## Step 4: Write STORYBOARD **Read:** [references/step-4-storyboard.md](references/step-4-storyboard.md) Write per-beat creative direction: mood, camera, animations, transitions, assets, depth layers, SFX. This is the creative north star — the document the engineer follows to build each composition. **Gate:** `STORYBOARD.md` exists with beat-by-beat direction and an asset audit table. --- ## Step 5: Generate VO + Map Timing **Read:** [references/step-5-vo.md](references/step-5-vo.md) Generate TTS audio, transcribe for word-level timestamps, and map timestamps to beats. Update STORYBOARD.md with real durations. **Gate:** `narration.wav` (or .mp3) + `transcript.json` exist. Beat timings in STORYBOARD.md updated. --- ## Step 6: Build Compositions **Read:** The `hyperframes` skill (load it — every rule matters) **Read:** [references/step-6-build.md](references/step-6-build.md) Build each composition following the storyboard. After each one: self-review for layout, asset placement, and animation quality. **Gate:** Every composition has been self-reviewed. No overlapping elements, no misplaced assets, no static images without motion. --- ## Step 7: Validate & Deliver **Read:** [references/step-7-validate.md](references/step-7-validate.md) Lint, validate, snapshot, preview. Deliver the localhost Studio project URL (`http://localhost:<port>/#project/<project-name>`) to the user first — only render to MP4 on explicit request. Do not treat `index.html` as the project handoff link; it is source-code context only. **Gate:** `npx hyperframes lint` and `npx hyperframes validate` pass with zero errors, and the final response includes the active Studio project URL. --- ## Quick Reference ### Video Types | Type | Duration | Beats | Narration | | --------------------- | -------- | ----- | ---------------------- | | Social ad (IG/TikTok) | 10-15s | 3-4 | Optional hook sentence | | Product demo | 30-60s | 5-8 | Full narration | | Feature announcement | 15-30s | 3-5 | Full narration | | Brand reel | 20-45s | 4-6 | Optional, music focus | | Launch teaser | 10-20s | 2-4 | Minimal, high energy | ### Format - **Landscape**: 1920x1080 (default) - **Portrait**: 1080x1920 (Instagram Stories, TikTok) - **Square**: 1080x1080 (Instagram feed) ### Reference Files | File | When to read | | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [step-1-capture.md](references/step-1-capture.md) | Step 1 — reading captured data | | [step-2-design.md](references/step-2-design.md) | Step 2 — writing DESIGN.md | | [step-3-script.md](references/step-3-script.md) | Step 3 — writing the narration script | | [step-4-storyboard.md](references/step-4-storyboard.md) | Step 4 — per-beat creative direction | | [step-5-vo.md](references/step-5-vo.md) | Step 5 — TTS, transcription, timing | | [step-6-build.md](references/step-6-build.md) | Step 6 — building compositions with self-review | | [step-7-validate.md](references/step-7-validate.md) | Step 7 — lint, validate, snapshot, preview | | [techniques.md](references/techniques.md) | Steps 4 & 6 — 10 visual techniques with code patterns (SVG drawing, Canvas 2D, 3D, typography, Lottie, video, typing, variable fonts, MotionPath, transitions) |
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".