Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a

General video Before relying on this workflow, run: A successful no op means the skill is current. Surface an update failure instead of continuing from memory. 1. Apply cross cutting source adapters Media: For any audio, image, icon, logo, voice, grade, LUT, treatment/effect, caption, or media operation need, load /media use and follow ../media use/references/resolve.md (resolve, adopt, reuse) and ../media use/references/setup providers.md (providers, auth). Vague footage feedback and named styles use ../media use/references/media treatments.md before editing; do not improvise supported media effects with CSS/SVG/opacity. Before the first authenticated provider action, run npx hyperframes auth status and relay its output verbatim. If signed out, apply the gate in ../hyperframes core/references/brief contract.md : collaborative waits for sign in or an explicit offline choice; autonomous states the status and continues through an available offline provider. Surface a blocker when no offline provider can satisfy a required capability. Local adoption alone does not require an auth gate. Figma: If any input is a figma.com URL, run /figma first. Build from its exported assets, tokens, components, or storyboard frames. Do not use raw Figma connector calls because they skip SVG sanitization, media provenance, and brand token binding. These adapters do not change the workflow selected by /hyperframes . 2. Start from project state Apply the first matching row; do not evaluate lower state rows: State Action Specific edit Make the edit, preserve existing project decisions, then rerun affected checks. Do not reopen discovery. BRIEF.md exists Read it. If workflow names another workflow and flow is not companion , hand off. Ask no brief questions. No brief, but hyperframes.json or STORYBOARD.md exists Resume from files and recorded preferences. Backfill BRIEF.md only from known facts. Fresh creation Run /hyperframes and its intent layer. Return here only for workflow: general video or flow: companion . For a new project, choose a kebab case directory name from the brief and scaffold before writing the brief: Then write BRIEF.md at the project root using ../hyperframes core/references/brief format.md . In an existing project, the root is the directory containing hyperframes.json . Record only the confirmed preference backed fields named by the brief format, using node <MEDIA DIR /scripts/prefs.mjs record hyperframes <PROJECT ROOT ; never record inferred defaults. Here <MEDIA DIR is the installed /media use skill directory and <PROJECT ROOT is the directory containing hyperframes.json . If the intent layer adopted a recipe, apply it now with node <MEDIA DIR /scripts/recipe.mjs use hyperframes <PROJECT ROOT name <name and do not ask again. 3. Interpret the run shape Use only the canonical terms from ../hyperframes core/references/brief contract.md : Field Meaning Effect flow Who drives automation : choose and execute the route. companion : co create in conversation. storyboard Whether the board is a review surface yes : run plan and sketch review. no : build without the board. derived mode How checkpoint gates behave Follow the brief contract. Never ask the user to name a mode. Do not invent synonyms for these states. An ongoing “just build it” signal is handled by the intent layer and arrives as flow: automation , storyboard: no . For flow: automation , choose the route and state it in one line in the first progress update. For a specific edit, make the edit without inventing a new route. For a hard cut, trim, splice, or reorder of existing footage, duplicate the same video source into multiple clip elements. On each copy, set the source range with data media start plus data duration , then set authored placement/order with data start . Separately authored audio follows the identical clip ranges and timing on matching <audio elements. /hyperframes core owns this temporal edit; use /hyperframes keyframes only for visual property animation such as zoom, punch, pan, crop, mask, or clip path on an inner wrapper. Copy the full contracts from ../hyperframes core/references/creator editing recipes.md . Companion flow When flow: companion : Read BRIEF.md and reconcile accepted Assets and Customizations with project artifacts. Complete accepted work that is still pending; leave completed work alone; do not offer an accepted capability again as if it were new. Arrive as the director, not the contractor. A user who chose companion chose involvement and quality; the honest response is the best version you can design, not the smallest one you can defend. The first plan is the ceiling treatment: the story arc (borrow the nearest genre lens — menu § Genre lenses), the design spec, each scene's motion treatment cited by name (§ 5's plan discipline), the transitions, the audio identity — music and sound marks, or deliberate silence — the user's material placed, and a designed open and close. Say what each layer adds in one line; flag the expensive ones (render time, sign in, billing) as you name them. The user trims a treatment down; they should never have to assemble one approval by approval. The ceiling belongs to the concept, not the toolbox. Every layer must serve the brief's message — a treatment that would dress any video the same way is decoration. Craft rises to the ceiling; content never grows past what was asked (§ 6). Between checkpoints, ../hyperframes/references/capability menu.md works two ways. As the trigger list: offer a relevant capability when the user mentions its input or the build reaches its need. As each pass's upgrade channel: a plan, sketch, or build checkpoint may carry one or two traced offers pointed at material the user is looking at ("scene 3's stat wants the count up treatment"). Read it before offering; never dump the full catalog. After the user accepts a capability, produce its artifact and record the decision in the matching BRIEF.md body section immediately. Rewrite a frontmatter field and record the confirmed preference only when the user explicitly changes it. Keep the same storyboard, validation, final preview, and render approval gates. Companion changes who steers, not what quality requires. 4. Load required knowledge before each stage These reads are mandatory when their condition matches: Condition Read before acting Any composition HTML or scene layout /hyperframes core ; use references/determinism rules.md for its layout contract Any non trivial creation or visual treatment /hyperframes creative → references/house style.md and references/video composition.md Any motion, animation, or scene transition /hyperframes animation ; follow its routing to the matching rules, adapters, blueprints, or transition references storyboard: yes ../hyperframes core/references/storyboard format.md and ../hyperframes core/references/review loop.md Any media asset or operation, including narration, BGM, SFX, captions, grading, or transforms /media use ; for framework playback and placement also read /hyperframes core → references/variables and media.md Multi scene assembly ../hyperframes core/references/production loop.md flow: companion , before the first plan /hyperframes creative → references/story spine.md and references/house style.md ; the nearest genre lens and the full ../hyperframes/references/capability menu.md — the ceiling treatment is designed from these, not recalled A companion capability offer, capture, beat grid, generative video, map, publishing, or cross workflow capability ../hyperframes/references/capability menu.md A design spec exists, before final approval /hyperframes creative → references/design adherence.md Do not replace these reads with recollection. Progressive disclosure saves context only when the matching reference is actually loaded. 5. Execute the composition Use this dependency order. Skip a stage only when its input is absent. 1. Plan. State the viewer arc, structure, rhythm, and duration driver. Use one file for a short single scene; use sub compositions for three or more hard scene cuts or any reused scene. Read /hyperframes creative → references/story spine.md for narrated arcs, references/beat direction.md for rhythm, and /hyperframes core → references/composition patterns.md for structure. For an open ended multi scene brief, expand the prompt through /hyperframes creative → references/prompt expansion.md . A multi scene plan cites each scene's shape: a blueprint id from /hyperframes animation → blueprints index.md when one fits, or the named rules it composes from rules index.md when none does — motion names come from those indexes, never invented. Story truth decides which scenes exist; the citation dresses them. Search the live catalog before you plan to build any named look yourself : for every look, effect, treatment or transition the brief names — "CRT scanlines", "glitch", "film grain", "shimmer sweep", "confetti burst" — run npx hyperframes catalog query "<the look, in plain English " json and read the top results before

general-video