[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75VY5CMBD4Q9FAMFEZ8HMZJ":3,"skill-same:01M75VY5CMBD4Q9FAMFEZ8HMZJ":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M75VY5CMBD4Q9FAMFEZ8HMZJ","general-video",null,"ItWasYou-SAM\u002FSkill-is-All-you-Need","ItWasYou-SAM","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255364315?v=4","01M75VMN2DKTF5V9QPG2D5PBY0","Sam","01M75VMN31FCZMM9RZ4W8ZHCR4",6,"MIT","https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need\u002Fblob\u002Fmaster\u002F04-video-production\u002Fgeneral-video\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: general-video\ndescription: >\n  Use this skill when creating multi-scene video compositions, brand reels, montages, or freeform video at any length.\n  Do not use for product launches, PR videos, or caption-only work.\ntriggers:\n  - \"create a video\"\n  - \"make a montage\"\n  - \"brand reel\"\n  - \"multi-scene video\"\n  Use as the fallback for custom HyperFrames HTML video composition authoring\n  when no specialized workflow fits. Covers longer or multi-scene pieces,\n  brand\u002Fsizzle reels, montages, title cards, motion posters at length, static\n  loops, and freeform compositions at any length or format. Not for marketed\n  product promos (product-launch-video), general website-to-video capture\n  (website-to-video), topic explainers (faceless-explainer), GitHub PR\n  videos (pr-to-video), captioning existing footage (embedded-captions),\n  Remotion ports (remotion-to-hyperframes), or short unnarrated motion-graphics\n  hits such as logo stings, kinetic type, stat\u002Fchart pops, lower-thirds,\n  animated tweets\u002Fheadlines, or page highlights. If a specialized workflow clearly fits the input, prefer it\n  (see \u002Fhyperframes); use this only as the input\u002Flength-agnostic fallback.\nmetadata: { \"tags\": \"orchestrator, general-video, fallback, freeform, composition-authoring\" }\n---\n\n# general-video — general composition authoring\n\n> **Confirm the route before you build.** This is the **fallback** for custom composition authoring. If the input clearly fits a specialized workflow, prefer it: marketed product → `\u002Fproduct-launch-video`; general site → `\u002Fwebsite-to-video`; topic explainer → `\u002Ffaceless-explainer`; GitHub PR → `\u002Fpr-to-video`; existing footage → `\u002Fembedded-captions` · `\u002Fgraphic-overlays`; short unnarrated motion graphic → `\u002Fmotion-graphics`; Remotion port → `\u002Fremotion-to-hyperframes`. **Out of scope**: live \u002F at-render-time data, NLE-style editing of a finished video, or producing footage HyperFrames can't capture. Unsure? **Read `\u002Fhyperframes` first.**\n\n**Build exactly what was asked.** A title card is a title card — not a title card + three supporting scenes + ambient music + captions. If extra scenes or elements would genuinely improve the piece, _propose_ them; don't add them silently. For small edits (fix a color, adjust one duration, add one element), skip the planning steps and go straight to the build.\n\n## Approach\n\n### Discovery — open-ended requests only\n\nFor vague, exploratory requests (\"make something for our brand\", \"a cool intro\") — understand intent before picking colors:\n\n- **Audience** — who watches? developers \u002F executives \u002F general consumers?\n- **Platform** — where does it play? social (15s) \u002F website hero \u002F product demo \u002F internal?\n- **Priority** — what matters most? motion quality \u002F content accuracy \u002F brand fidelity \u002F speed?\n- **Variations** — one best shot, or 2-3 meaningfully different options (different pacing, energy, or structure — not just color swaps)?\n\nFor specific requests (\"add a title card\", \"fix the timing on scene 3\"), skip discovery.\n\n### Step 1 — Design system → `hyperframes-creative`\n\nEstablish the visual identity first. If the project has a design spec, read it (precedence `frame.md` → `design.md` → `DESIGN.md`; treat it as brand truth — exact colors, fonts, constraints).\n\n**If no spec exists, you MUST read BOTH `hyperframes-creative\u002Freferences\u002Fhouse-style.md` AND `hyperframes-creative\u002Freferences\u002Fvideo-composition.md` before choosing any color or font.** `house-style.md` gives the \"interpret the prompt \u002F generate real content\" opener, lazy-default list, and layer recipe; `video-composition.md` gives the video-medium density \u002F scale \u002F **foreground detailing** (data bars, registration marks, monospace metadata, \"8-10 elements, two the user didn't ask for\") that separates \"produced\" from \"generated.\" Reading only one is the most common miss — `video-composition.md` is the one agents skip, and it is exactly the one that prevents flat, centered, web-page-looking output. Do not self-invent a palette and skip these; crossing into `hyperframes-creative` is mandatory here, not an optional branch. From there, also pull a named style\u002Fmood → `references\u002Fvisual-styles.md`, or the interactive picker → `references\u002Fdesign-picker.md`, as needed. The spec\u002Fstyle defines the **brand**, not the composition rules.\n\n**Find the angle (vague brief, no spec):** before picking colors, write ONE sentence — what does this name\u002Fword\u002Ftopic evoke, and what visual _world_ (metaphor, setting, instrument, motif) expresses it? E.g. a cybersecurity tool → vault doors \u002F perimeter scan lines \u002F lock tumblers; a meditation app → tide, breath, slow light bloom. Read the _meaning_ of the subject, not just its letters; pick a concrete angle over a literal restyle. This is the cheap substitute for prompt expansion (Step 2) on single-scene pieces, where expansion is correctly skipped — and it is the difference between a designed concept and a generic logo-on-a-gradient.\n\n\u003CHARD-GATE>\nBefore writing ANY composition HTML, verify you have ALL FOUR:\n1. **A visual identity** grounded in the spec or `house-style.md` — not invented on the spot. (Reaching for `#333`, `#3b82f6`, or `Roboto`? You skipped it.)\n2. **A one-sentence concept angle** (the \"find the angle\" step) for anything beyond a trivial edit — not a literal restyle of the prompt words.\n3. **A font pairing from the embed list** (`hyperframes-creative\u002Freferences\u002Ftypography.md` → \"Fonts that embed\") chosen on purpose — not `Inter`\u002F`Helvetica Neue`\u002F`system-ui` by default, and never an un-embedded display font you're just hoping renders (un-bundled names embed only if auto-captured locally — and cloud renders won't capture them).\n4. **A foreground\u002Fdensity plan from `video-composition.md`** — the anchor-to-edges, 8-10-elements, foreground-metadata, background-texture rules. (Centered stack on a flat color with fewer than ~6 elements and no edge-anchored detail? You skipped it — that is the generic tell.)\n\u003C\u002FHARD-GATE>\n\n### Step 2 — Prompt expansion → `hyperframes-creative`\n\nRun for every multi-scene composition (skip for single-scene pieces and trivial edits). Ground the request against the design spec + house style into a consistent intermediate that downstream work reads the same way. See `hyperframes-creative\u002Freferences\u002Fprompt-expansion.md`.\n\n### Step 3 — Plan\n\nBefore writing HTML, think at a high level:\n\n1. **What** — the viewer experience: narrative arc, key moments, emotional beats.\n2. **Structure** — how many compositions, sub-comp vs inline, which tracks carry video \u002F audio \u002F overlays \u002F captions. For the monolithic-single-file vs modular-sub-comp call, see `hyperframes-core\u002Freferences\u002Fcomposition-patterns.md` § Two Architectures (rule of thumb: ≥3 hard scene cuts, or any reused scene → modularize; a short single-scene piece stays one file).\n3. **Rhythm** — name the pattern before implementing (e.g. `fast-fast-SLOW-SHADER-hold`); see `hyperframes-creative\u002Freferences\u002Fbeat-direction.md`.\n4. **Timing** — which clips drive duration, where transitions land, the pacing.\n5. **Layout** — build the end state first (see below).\n6. **Animate** — then add motion via `hyperframes-animation`.\n\n## Layout Before Animation\n\nPosition every element where it sits at its **most visible moment** — fully entered, correctly placed, not yet exiting. Write that as static HTML + CSS first. **No GSAP yet.**\n\n**Why:** if you position elements at their animated start state (offscreen, scaled to 0, opacity 0) and tween to where you _think_ they land, you are guessing the final layout — overlaps stay invisible until render. Build the end state first and you see and fix layout problems before adding motion.\n\n1. **Identify the hero frame** for each scene — the moment the most elements are simultaneously visible. That is the layout you build.\n2. **Write static CSS** for that frame. The content container must fill the scene with padding, not absolute offsets:\n\n```css\n.scene-content {\n  display: flex;\n  flex-direction: column;\n  justify-content: center;\n  width: 100%;\n  height: 100%;\n  padding: 120px 160px; \u002F* padding positions content; fills any scene size *\u002F\n  gap: 24px;\n  box-sizing: border-box;\n}\n```\n\nNever use `position: absolute; top: Npx` on a content container — it overflows when content is taller than the space. Reserve absolute positioning for decoratives.\n\n> ⚠ **The `width\u002Fheight: 100%` above only resolves if every ancestor has a resolved height.** The root `\u003Cdiv data-composition-id>` and any wrapper between it and `.scene-content` must be sized (`position: relative; width: 1920px; height: 1080px` on the root — see `hyperframes-core` → \"Root must be sized\"). Skip this and the flex container collapses to ~0, content piles into the **top-left corner**, and the first glyph clips at x=0 — while `lint`\u002F`inspect` still report 0 issues. And **always keep the `padding`** (≥80px) on `.scene-content`: it is the title-safe margin. Never replace it with bare `gap`.\n\n3. **Add entrances** — animate FROM offscreen\u002Finvisible TO the CSS position with `gsap.from()` (in sub-compositions prefer `gsap.fromTo()` so the start state is explicit; see `hyperframes-core\u002Freferences\u002Fsub-compositions.md`). The CSS position is ground truth; the tween is the journey to it.\n4. **Exits are transition-handled** — per the scene-transition rules in `hyperframes-animation\u002Ftransitions\u002F`, only the **final** scene animates elements out; between scenes the transition IS the exit.\n\n**Shared space across time:** if element A exits before element B enters in the same area, both still need correct CSS positions for their respective hero frames — timeline ordering keeps them from coexisting, and the layout step catches accidental overlap. Layered glows\u002Fshadows and z-stacked depth are _intentional_ overlap; the step is about catching _unintentional_ collisions (two headlines on top of each other, content bleeding off-frame).\n\n## Build — delegate to the domain skills\n\nThis maps the skill's full surface (see the `description`) to its references — non-exhaustive; when an intent isn't listed, route through `hyperframes-creative` (look\u002Fconcept), `hyperframes-animation` (motion), `hyperframes-core` (contract), `hyperframes-media` (audio\u002Fcaptions). **The first row is ADDITIVE — read it AND your intent row, not one or the other.**\n\n| Building…                                                             | Read first (in order)                                                                                                                                                       |\n| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **ALWAYS — every non-trivial piece, on top of your intent row below** | `hyperframes-creative\u002Freferences\u002Fhouse-style.md` + `references\u002Fvideo-composition.md` (also gated in Step 1 \u002F HARD-GATE; the \"produced, not generated\" foreground detailing) |\n| **Kinetic typography \u002F text-forward**                                 | `hyperframes-animation\u002Ftechniques.md` (kinetic type) + `adapters\u002Fgsap-easing-and-stagger.md` + `rules\u002Fkinetic-beat-slam.md`                                                 |\n| **Title card \u002F lower-third \u002F overlay \u002F PiP \u002F text-behind-subject**    | `hyperframes-creative\u002Freferences\u002Fcomposition-patterns.md` + (for the centered\u002Fsized frame) `hyperframes-core` → \"Root must be sized\"                                        |\n| **Logo \u002F brand-mark reveal**                                          | `hyperframes-animation\u002Frules\u002Fsvg-path-draw.md` (draw-on) + `rules\u002F3d-text-depth-layers.md` + `rules\u002Fscale-swap-transition.md`                                               |\n| **Data \u002F stats \u002F numbers**                                            | `hyperframes-animation\u002Frules\u002Fcounting-dynamic-scale.md` + `rules\u002Fstat-bars-and-fills.md` + `hyperframes-creative\u002Freferences\u002Fdata-in-motion.md`                              |\n| **Product \u002F app \u002F UI demo**                                           | `hyperframes-animation\u002Frules\u002F3d-page-scroll.md` + `rules\u002Fcursor-click-ripple.md` + `rules\u002Fpress-release-spring.md`                                                          |\n| **Audio-reactive \u002F music-driven**                                     | `hyperframes-creative\u002Freferences\u002Faudio-reactive.md` (pre-extract bands; map to motion)                                                                                      |\n| **Narrated \u002F voiceover \u002F captions \u002F subtitles**                       | `hyperframes-media` (`tts`, `transcribe`, caption authoring) → place assets via `hyperframes-core`                                                                          |\n| **Multi-scene \u002F transitions**                                         | `hyperframes-animation\u002Ftransitions\u002Foverview.md` **then** `transitions\u002Fcatalog.md` (you are not done after the overview — the GSAP recipe is in the catalog)                 |\n| **Modular \u002F sub-compositions**                                        | `hyperframes-core\u002Freferences\u002Fcomposition-patterns.md` + `references\u002Fsub-compositions.md`                                                                                    |\n\n## Output checklist → `hyperframes-cli`\n\n- [ ] `npx hyperframes lint` and `npx hyperframes validate` pass (block on results)\n- [ ] design adherence verified if a spec (`frame.md` \u002F `design.md`) exists — checklist in `hyperframes-creative\u002Freferences\u002Fdesign-adherence.md`\n- [ ] `npx hyperframes inspect` passes, or every overflow is intentionally marked\n- [ ] contrast warnings addressed; for multi-scene work, review the animation map (`hyperframes-animation\u002Fscripts\u002Fanimation-map.mjs`)\n- [ ] deliver the preview; render to MP4 only on explicit request\n- [ ] surface the preview **only at handoff** (it is the stable, final preview); don't pop one mid-build — build-phase snapshots are headless\n\n## Not this workflow\n\n- A specific **product \u002F company \u002F SaaS \u002F website** being marketed, launched, or promoted → `\u002Fproduct-launch-video`\n- A **concept \u002F topic \u002F article \u002F how-X-works** being explained, no product → `\u002Ffaceless-explainer`\n- A **GitHub PR \u002F code change** → `\u002Fpr-to-video`\n- An **existing talking-head video** to add captions to → `\u002Fembedded-captions`\n- Porting an existing **Remotion** composition → `\u002Fremotion-to-hyperframes`\n- Cutting \u002F editing a **finished video file** like an NLE → out of scope (HyperFrames composites HTML and media into a deterministic timeline; it does not edit footage)\n","# general-video — general composition authoring\n\n> **Confirm the route before you build.** This is the **fallback** for custom composition authoring. If the input clearly fits a specialized workflow, prefer it: marketed product → `\u002Fproduct-launch-video`; general site → `\u002Fwebsite-to-video`; topic explainer → `\u002Ffaceless-explainer`; GitHub PR → `\u002Fpr-to-video`; existing footage → `\u002Fembedded-captions` · `\u002Fgraphic-overlays`; short unnarrated motion graphic → `\u002Fmotion-graphics`; Remotion port → `\u002Fremotion-to-hyperframes`. **Out of scope**: live \u002F at-render-time data, NLE-style editing of a finished video, or producing footage HyperFrames can't capture. Unsure? **Read `\u002Fhyperframes` first.**\n\n**Build exactly what was asked.** A title card is a title card — not a title card + three supporting scenes + ambient music + captions. If extra scenes or elements would genuinely improve the piece, _propose_ them; don't add them silently. For small edits (fix a color, adjust one duration, add one element), skip the planning steps and go straight to the build.\n\n## Approach\n\n### Discovery — open-ended requests only\n\nFor vague, exploratory requests (\"make something for our brand\", \"a cool intro\") — understand intent before picking colors:\n\n- **Audience** — who watches? developers \u002F executives \u002F general consumers?\n- **Platform** — where does it play? social (15s) \u002F website hero \u002F product demo \u002F internal?\n- **Priority** — what matters most? motion quality \u002F content accuracy \u002F brand fidelity \u002F speed?\n- **Variations** — one best shot, or 2-3 meaningfully different options (different pacing, energy, or structure — not just color swaps)?\n\nFor specific requests (\"add a title card\", \"fix the timing on scene 3\"), skip discovery.\n\n### Step 1 — Design system → `hyperframes-creative`\n\nEstablish the visual identity first. If the project has a design spec, read it (precedence `frame.md` → `design.md` → `DESIGN.md`; treat it as brand truth — exact colors, fonts, constraints).\n\n**If no spec exists, you MUST read BOTH `hyperframes-creative\u002Freferences\u002Fhouse-style.md` AND `hyperframes-creative\u002Freferences\u002Fvideo-composition.md` before choosing any color or font.** `house-style.md` gives the \"interpret the prompt \u002F generate real content\" opener, lazy-default list, and layer recipe; `video-composition.md` gives the video-medium density \u002F scale \u002F **foreground detailing** (data bars, registration marks, monospace metadata, \"8-10 elements, two the user didn't ask for\") that separates \"produced\" from \"generated.\" Reading only one is the most common miss — `video-composition.md` is the one agents skip, and it is exactly the one that prevents flat, centered, web-page-looking output. Do not self-invent a palette and skip these; crossing into `hyperframes-creative` is mandatory here, not an optional branch. From there, also pull a named style\u002Fmood → `references\u002Fvisual-styles.md`, or the interactive picker → `references\u002Fdesign-picker.md`, as needed. The spec\u002Fstyle defines the **brand**, not the composition rules.\n\n**Find the angle (vague brief, no spec):** before picking colors, write ONE sentence — what does this name\u002Fword\u002Ftopic evoke, and what visual _world_ (metaphor, setting, instrument, motif) expresses it? E.g. a cybersecurity tool → vault doors \u002F perimeter scan lines \u002F lock tumblers; a meditation app → tide, breath, slow light bloom. Read the _meaning_ of the subject, not just its letters; pick a concrete angle over a literal restyle. This is the cheap substitute for prompt expansion (Step 2) on single-scene pieces, where expansion is correctly skipped — and it is the difference between a designed concept and a generic logo-on-a-gradient.\n\n\u003CHARD-GATE>\nBefore writing ANY composition HTML, verify you have ALL FOUR:\n1. **A visual identity** grounded in the spec or `house-style.md` — not invented on the spot. (Reaching for `#333`, `#3b82f6`, or `Roboto`? You skipped it.)\n2. **A one-sentence concept angle** (the \"find the angle\" step) for anything beyond a trivial edit — not a literal restyle of the prompt words.\n3. **A font pairing from the embed list** (`hyperframes-creative\u002Freferences\u002Ftypography.md` → \"Fonts that embed\") chosen on purpose — not `Inter`\u002F`Helvetica Neue`\u002F`system-ui` by default, and never an un-embedded display font you're just hoping renders (un-bundled names embed only if auto-captured locally — and cloud renders won't capture them).\n4. **A foreground\u002Fdensity plan from `video-composition.md`** — the anchor-to-edges, 8-10-elements, foreground-metadata, background-texture rules. (Centered stack on a flat color with fewer than ~6 elements and no edge-anchored detail? You skipped it — that is the generic tell.)\n\u003C\u002FHARD-GATE>\n\n### Step 2 — Prompt expansion → `hyperframes-creative`\n\nRun for every multi-scene composition (skip for single-scene pieces and trivial edits). Ground the request against the design spec + house style into a consistent intermediate that downstream work reads the same way. See `hyperframes-creative\u002Freferences\u002Fprompt-expansion.md`.\n\n### Step 3 — Plan\n\nBefore writing HTML, think at a high level:\n\n1. **What** — the viewer experience: narrative arc, key moments, emotional beats.\n2. **Structure** — how many compositions, sub-comp vs inline, which tracks carry video \u002F audio \u002F overlays \u002F captions. For the monolithic-single-file vs modular-sub-comp call, see `hyperframes-core\u002Freferences\u002Fcomposition-patterns.md` § Two Architectures (rule of thumb: ≥3 hard scene cuts, or any reused scene → modularize; a short single-scene piece stays one file).\n3. **Rhythm** — name the pattern before implementing (e.g. `fast-fast-SLOW-SHADER-hold`); see `hyperframes-creative\u002Freferences\u002Fbeat-direction.md`.\n4. **Timing** — which clips drive duration, where transitions land, the pacing.\n5. **Layout** — build the end state first (see below).\n6. **Animate** — then add motion via `hyperframes-animation`.\n\n## Layout Before Animation\n\nPosition every element where it sits at its **most visible moment** — fully entered, correctly placed, not yet exiting. Write that as static HTML + CSS first. **No GSAP yet.**\n\n**Why:** if you position elements at their animated start state (offscreen, scaled to 0, opacity 0) and tween to where you _think_ they land, you are guessing the final layout — overlaps stay invisible until render. Build the end state first and you see and fix layout problems before adding motion.\n\n1. **Identify the hero frame** for each scene — the moment the most elements are simultaneously visible. That is the layout you build.\n2. **Write static CSS** for that frame. The content container must fill the scene with padding, not absolute offsets:\n\n```css\n.scene-content {\n  display: flex;\n  flex-direction: column;\n  justify-content: center;\n  width: 100%;\n  height: 100%;\n  padding: 120px 160px; \u002F* padding positions content; fills any scene size *\u002F\n  gap: 24px;\n  box-sizing: border-box;\n}\n```\n\nNever use `position: absolute; top: Npx` on a content container — it overflows when content is taller than the space. Reserve absolute positioning for decoratives.\n\n> ⚠ **The `width\u002Fheight: 100%` above only resolves if every ancestor has a resolved height.** The root `\u003Cdiv data-composition-id>` and any wrapper between it and `.scene-content` must be sized (`position: relative; width: 1920px; height: 1080px` on the root — see `hyperframes-core` → \"Root must be sized\"). Skip this and the flex container collapses to ~0, content piles into the **top-left corner**, and the first glyph clips at x=0 — while `lint`\u002F`inspect` still report 0 issues. And **always keep the `padding`** (≥80px) on `.scene-content`: it is the title-safe margin. Never replace it with bare `gap`.\n\n3. **Add entrances** — animate FROM offscreen\u002Finvisible TO the CSS position with `gsap.from()` (in sub-compositions prefer `gsap.fromTo()` so the start state is explicit; see `hyperframes-core\u002Freferences\u002Fsub-compositions.md`). The CSS position is ground truth; the tween is the journey to it.\n4. **Exits are transition-handled** — per the scene-transition rules in `hyperframes-animation\u002Ftransitions\u002F`, only the **final** scene animates elements out; between scenes the transition IS the exit.\n\n**Shared space across time:** if element A exits before element B enters in the same area, both still need correct CSS positions for their respective hero frames — timeline ordering keeps them from coexisting, and the layout step catches accidental overlap. Layered glows\u002Fshadows and z-stacked depth are _intentional_ overlap; the step is about catching _unintentional_ collisions (two headlines on top of each other, content bleeding off-frame).\n\n## Build — delegate to the domain skills\n\nThis maps the skill's full surface (see the `description`) to its references — non-exhaustive; when an intent isn't listed, route through `hyperframes-creative` (look\u002Fconcept), `hyperframes-animation` (motion), `hyperframes-core` (contract), `hyperframes-media` (audio\u002Fcaptions). **The first row is ADDITIVE — read it AND your intent row, not one or the other.**\n\n| Building…                                                             | Read first (in order)                                                                                                                                                       |\n| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **ALWAYS — every non-trivial piece, on top of your intent row below** | `hyperframes-creative\u002Freferences\u002Fhouse-style.md` + `references\u002Fvideo-composition.md` (also gated in Step 1 \u002F HARD-GATE; the \"produced, not generated\" foreground detailing) |\n| **Kinetic typography \u002F text-forward**                                 | `hyperframes-animation\u002Ftechniques.md` (kinetic type) + `adapters\u002Fgsap-easing-and-stagger.md` + `rules\u002Fkinetic-beat-slam.md`                                                 |\n| **Title card \u002F lower-third \u002F overlay \u002F PiP \u002F text-behind-subject**    | `hyperframes-creative\u002Freferences\u002Fcomposition-patterns.md` + (for the centered\u002Fsized frame) `hyperframes-core` → \"Root must be sized\"                                        |\n| **Logo \u002F brand-mark reveal**                                          | `hyperframes-animation\u002Frules\u002Fsvg-path-draw.md` (draw-on) + `rules\u002F3d-text-depth-layers.md` + `rules\u002Fscale-swap-transition.md`                                               |\n| **Data \u002F stats \u002F numbers**                                            | `hyperframes-animation\u002Frules\u002Fcounting-dynamic-scale.md` + `rules\u002Fstat-bars-and-fills.md` + `hyperframes-creative\u002Freferences\u002Fdata-in-motion.md`                              |\n| **Product \u002F app \u002F UI demo**                                           | `hyperframes-animation\u002Frules\u002F3d-page-scroll.md` + `rules\u002Fcursor-click-ripple.md` + `rules\u002Fpress-release-spring.md`                                                          |\n| **Audio-reactive \u002F music-driven**                                     | `hyperframes-creative\u002Freferences\u002Faudio-reactive.md` (pre-extract bands; map to motion)                                                                                      |\n| **Narrated \u002F voiceover \u002F captions \u002F subtitles**                       | `hyperframes-media` (`tts`, `transcribe`, caption authoring) → place assets via `hyperframes-core`                                                                          |\n| **Multi-scene \u002F transitions**                                         | `hyperframes-animation\u002Ftransitions\u002Foverview.md` **then** `transitions\u002Fcatalog.md` (you are not done after the overview — the GSAP recipe is in the catalog)                 |\n| **Modular \u002F sub-compositions**                                        | `hyperframes-core\u002Freferences\u002Fcomposition-patterns.md` + `references\u002Fsub-compositions.md`                                                                                    |\n\n## Output checklist → `hyperframes-cli`\n\n- [ ] `npx hyperframes lint` and `npx hyperframes validate` pass (block on results)\n- [ ] design adherence verified if a spec (`frame.md` \u002F `design.md`) exists — checklist in `hyperframes-creative\u002Freferences\u002Fdesign-adherence.md`\n- [ ] `npx hyperframes inspect` passes, or every overflow is intentionally marked\n- [ ] contrast warnings addressed; for multi-scene work, review the animation map (`hyperframes-animation\u002Fscripts\u002Fanimation-map.mjs`)\n- [ ] deliver the preview; render to MP4 only on explicit request\n- [ ] surface the preview **only at handoff** (it is the stable, final preview); don't pop one mid-build — build-phase snapshots are headless\n\n## Not this workflow\n\n- A specific **product \u002F company \u002F SaaS \u002F website** being marketed, launched, or promoted → `\u002Fproduct-launch-video`\n- A **concept \u002F topic \u002F article \u002F how-X-works** being explained, no product → `\u002Ffaceless-explainer`\n- A **GitHub PR \u002F code change** → `\u002Fpr-to-video`\n- An **existing talking-head video** to add captions to → `\u002Fembedded-captions`\n- Porting an existing **Remotion** composition → `\u002Fremotion-to-hyperframes`\n- Cutting \u002F editing a **finished video file** like an NLE → out of scope (HyperFrames composites HTML and media into a deterministic timeline; it does not edit footage)\n",{},"master","f0b9a39cdf4f3e791e3acb54c8740ca23f704176","04-video-production\u002Fgeneral-video",0,"https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need","https:\u002F\u002Fgithub.com\u002FItWasYou-SAM","https:\u002F\u002Fit-was-you-sam.vercel.app\u002F","AI Engineer ","2026-11-10 22:32:18",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ItWasYou-SAM\u002FSkill-is-All-you-Need --skill general-video",{"tool":38,"command":39},"bunx","bunx skills add ItWasYou-SAM\u002FSkill-is-All-you-Need --skill general-video",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ItWasYou-SAM\u002FSkill-is-All-you-Need --skill general-video","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need\u002Fblob\u002Fmaster\u002F04-video-production\u002Fgeneral-video\u002FSKILL.md",true,[],[47,54,61,68,74,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75WFD9BZ3S2ZDECD86QP3T9","invoice-organizer","Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.","https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need\u002Fblob\u002Fmaster\u002F12-business-productivity\u002Finvoice-organizer\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75WF96VTQYB6FHW43DK9JZ3","file-organizer","Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.","https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need\u002Fblob\u002Fmaster\u002F12-business-productivity\u002Ffile-organizer\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M75WF5VR42JXJZ5N6152R4P6","developer-growth-analysis","Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.","https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need\u002Fblob\u002Fmaster\u002F12-business-productivity\u002Fdeveloper-growth-analysis\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M75WF4PKRDZMHWSC90FVJM1R","connect","https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need\u002Fblob\u002Fmaster\u002F12-business-productivity\u002Fconnect\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75WF1H9N7Y1C5V6TM397ZGJ","twitter-algorithm-optimizer","https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need\u002Fblob\u002Fmaster\u002F11-brand-marketing\u002Ftwitter-algorithm-optimizer\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M75WEZGF264KM1G13P0CTY4C","tailored-resume-generator","https:\u002F\u002Fgithub.com\u002FItWasYou-SAM\u002FSkill-is-All-you-Need\u002Fblob\u002Fmaster\u002F11-brand-marketing\u002Ftailored-resume-generator\u002FSKILL.md",[],[]]