[Misc] Add portable MiniMax H3 skills (#7923)

Signed-off-by: princepride <wangzhipeng628@gmail.com>
2026-09-22 11:10:42 +08:00
1 parent 303edff930
commit f8a00b1491
@@ -0,0 +1,64 @@
 ---
 name: 3d-animation-short-generator
 description: Develop stylized 3D narrative shorts through story, character and environment references, timed shot tables, storyboards, generation, and assembly. Use for coherent animated storytelling or its planning stages, not isolated image edits or photorealistic live action.
 metadata:
  compatibility: File-based agent workflow with sibling h3-prompt-writing. Media generation and editing require available tools or a configured backend.
 ---
 # 3D Animation Short Generator
 Read the [portable workflow](../h3-prompt-writing/references/portable-workflow.md).
 For a complete film, progress from story to references, shot table, text storyboard,
 clips, and assembly. Keep these as local artifacts, using existing user decisions
 and authorization. If only a planning stage is requested, deliver that stage.
 ## Story and visual contract
 Capture premise, desired emotional outcome, duration, ratio, model, and audio mode.
 Use warm stylized 3D as a default only when style is unspecified: readable geometric
 silhouettes, designed hair clumps, tactile materials, soft skin shading where
 appropriate, expressive brows/eyes, and elastic posing. User-selected 2D or other
 styles override this preset rather than receiving accidental 3D texture.
 Create an active protagonist with a want, obstacle, meaningful choice, and payoff.
 Connect the ending to an earlier visual/emotional anchor. Use as many beats as the
 duration needs; do not pad a tiny story into an eight-beat formula. Dialogue should
 change a relationship or move the action, and use the user's requested language.
 ## Reference design
 - Character references lock name, silhouette, proportions, face, hair, costume,
  signature props, and color. Label identity in the production document; clean
  rendering anchors should not carry labels that could leak into the video.
 - Scene references contain environments only unless the user requested a composite.
  Record landmarks, lighting direction/time of day, entrances, exits, and prop state.
 - A reference board with multiple views is for design review. Prefer appropriate
  clean views for model input so grids and pose sheets do not become final frames.
 - When an asset changes, update all affected prompts and clips, with a manifest
  identifying the current revision.
 ## Shot planning
 Read [shot-table-spec.md](references/shot-table-spec.md) for the six-column table
 and continuity checks. Then read
 [storyboard-guidelines.md](references/storyboard-guidelines.md) for the matching
 text storyboard and optional pencil previews. The text storyboard is the source
 of shot timing; preview art does not silently replace it.
 Vary shot size and elastic performance to serve the story. Camera tilts, close-ups,
 or exaggeration are choices for specific beats, not quotas. Track off-screen
 characters and spatial landmarks so they do not teleport back into later shots.
 ## Generation and assembly
 Before rendering, read [model-selection.md](references/model-selection.md) and
 [fallback-policy.md](references/fallback-policy.md). Use the chosen model through
 available tools. Compile prompts using the H3 base or reference guide as appropriate.
 Remove storyboard-only labels, arrows, panel borders, and sketch styling from
 rendering inputs. Tie each clip to the current scene and character references.
 Read [qc-checklist.md](references/qc-checklist.md) for assembly and final review.
 Keep the planned shot order and audio continuity. Use a continuous score when
 requested, duck it under dialogue/SFX, and do not add subtitles unasked. Deliver
 the actual film or the requested planning package, with reproducible prompts and
 any unresolved identity, scene, or timing defects.
@@ -0,0 +1,4 @@
 interface:
  display_name: "3D Animation Shorts"
  short_description: "Plan stories, character anchors, shots, and edits"
  default_prompt: "Use $3d-animation-short-generator to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,21 @@
 # Targeted generation recovery
 Compare the failed result against the shot's actual identity/spatial anchors.
 Classify the failure: wrong input or API mapping, reference drift, overloaded
 action, timing, audio, or a render/export failure. Fix transport/configuration
 errors before spending another generation attempt.
 For drift, quote the relevant anchors and remove unrelated reference roles. For
 overloaded action, simplify or split the shot while preserving the requested total
 duration and handoffs. For a scene change, use the new scene reference and avoid
 conditioning on a previous scene when that would contradict the new setting.
 Use the retry/resource limit from the shared portable workflow. A persistent
 failure should lead to a concrete choice (simpler action, a supplied reference,
 an authorized alternate model, or an explicitly incomplete shot), not automatic
 provider switching or an endless loop. Never present a placeholder as a finished
 clip or hide an incorrect scene in final assembly.
 For optional pencil previews, reduce annotation or panel count. Use the text
 storyboard if visualization is not essential; do not rerender correct video
 solely because a human-review sketch changed.
@@ -0,0 +1,21 @@
 # Model and format selection
 Honor an existing model choice. Otherwise prefer MiniMax H3 when available, and
 inspect the running backend for partitions, reference modes, audio, resolutions,
 duration limits, and long-video options. Do not assume hosted and local services
 have identical limits, quality, prices, or parameter names.
 If another model is requested, use its real documented input contract. A provider
 switch needs the user's authorization; never silently use a different service
 because a preset names it as a fallback. For an authorized mixed-model workflow,
 record model and settings per shot and check cross-shot style differences.
 Keep delivery resolution separate from native generation resolution. Record actual
 width/height, fps, frame count, and any crop, retiming, or upscaling. Do not claim
 native 2K when the video was generated at 768p and restored later.
 Compile shot action, camera, identity, scene, and audio into the chosen model's
 prompt format. For H3 use the bundled writing guides. Strip production labels and
 preview grids. Prompt for designed silhouettes, elastic action, material and
 lighting details when these belong to the user's 3D style; do not add text/UI just
 because a model can generate them.
@@ -0,0 +1,19 @@
 # Assembly and review
 Use current clip revisions in shot-table order. Preserve useful dialogue and SFX;
 mix a continuous requested score underneath them. Inspect edits at sound bridges
 and dialogue boundaries, avoiding cut vowels and accidental audio gaps. Only add
 subtitles, music, or retiming consistent with the brief.
 Review identity, landmarks, screen direction, light/time of day, prop state,
 emotional payoff, intelligibility, SFX timing, and music balance. Look for leaked
 storyboard panels, sketch lines, arrows, labels, timecodes, or watermarks. Verify
 the complete file's duration, dimensions, fps, frame count, audio, and decode.
 Keep planning documents, references, raw clips, and final edits in distinguishable
 folders. Record the exact assets used in the final edit. After a character, scene,
 prompt, clip, or score is revised, update its downstream dependents and archive the
 previous result; do not silently combine stale and current versions.
 Report observed defects and what was repaired, including external editing or
 upscaling. A successful API response proves completion, not visual correctness.
@@ -0,0 +1,30 @@
 # Six-column shot table
 | Shot ID & Duration | Continuity Handoff | Reference Anchors (Spatial + Identity) | Hook Type | Shot Description (Per-Second Directives) | Audio & Dialogue Track |
 | --- | --- | --- | --- | --- | --- |
 Use stable IDs such as S01. Record incoming and outgoing image state, prop
 position, eyeline, motion, and emotional state in Continuity Handoff.
 Reference Anchors contains named landmarks and screen-relative positions; each
 character's screen position, facing and pose; recently exited characters' locations;
 lighting baseline and modifiers; and exact character/scene asset paths or IDs.
 An explicit scene/time change can replace these anchors; an accidental flip cannot.
 Hook Type names the shot's purpose: setup, reveal, reversal, joke, suspense,
 tenderness, chase, or callback. Do not force a joke or cut into a quiet scene.
 For each second or meaningful sub-second beat, cover action/pose/expression,
 camera, spatial/prop state, sound, and the handoff to the next interval. Use compact
 phrases rather than inventing movement in intentionally still moments. Include
 anticipation, squash/stretch, overshoot, and follow-through where appropriate.
 Keep the complete dialogue/narration script in Audio & Dialogue Track, with
 speaker, timing, delivery, and SFX. Distinguish off-screen narration from speaking
 characters; a visible listener should not lip-sync the narrator's words.
 Before rendering, check full time coverage, supported generation durations, a
 readable number of active characters, matching scene/identity references, and
 coherent row-to-row handoffs. Mark intentional cuts/time jumps. Fix contradictory
 states rather than using a generic continuity assurance. A visual shot may span
 multiple generation windows when the verified backend supports continuation.
@@ -0,0 +1,29 @@
 # Text storyboard and optional visualization
 Maintain one `storyboard.md` with a section per shot. Each section contains:
 1. Shot ID, title, duration, and narrative purpose.
 2. Exact scene and character reference IDs.
 3. Spatial anchors: landmarks, character positions/facing, off-screen characters,
   key/fill/rim lighting, and important props.
 4. Incoming and outgoing continuity state.
 5. Time-ordered beats: pose/expression, camera, audio, and anchor changes.
 Use per-second or finer intervals only where meaningful; cover the complete shot.
 For narrated moments, specify whether a visible character speaks or only reacts.
 Optional ASCII staging diagrams can clarify screen direction but are not images
 to supply as rendering references.
 For heavy revision of a shot, extract its section to a named file and link it from
 the main document. Choose one authoritative version; reintegrate or update the
 link after revision so later generation cannot read stale content.
 Only generate pencil storyboards when requested or already authorized as previews.
 Use equal-sized time-ordered panels, with timecode, pose/expression, camera arrow,
 and audio/anchor notes. Suggested layouts: three panels in a strip, four in a 2×2
 grid, six in 2×3. More complex scenes may need fewer representative key poses.
 Keep shot/character/scene labels readable for human review, but never feed these
 annotated grids as clean final frames. The text timeline remains authoritative.
 If preview panels fail, simplify annotation or rely on text within the agreed
 scope. An optional visualization failure need not block a usable text storyboard.
@@ -0,0 +1,53 @@
 # MiniMax H3 skill provenance
 Upstream: https://github.com/MiniMax-AI/MiniMax-H3
 Source snapshot: `d21241f0a4b3acbb34c97dae47fa417b7065e438`, retrieved 2026-09-19.
 Source directory:
 https://github.com/MiniMax-AI/MiniMax-H3/tree/d21241f0a4b3acbb34c97dae47fa417b7065e438/skills
 The nine upstream skill names are retained. Each local skill corresponds to the
 same-named upstream `skills/<name>/` directory. Credit for the original creative
 workflows and templates belongs to MiniMax-AI and the upstream contributors.
 ## Files and adaptation
 - `h3-prompt-writing/references/base-format.md` and `ref-format.md` are new,
  condensed descriptions of the public prompt interface. They preserve necessary
  field names and notation but do not copy the upstream guides or their examples.
  The entrypoint adds a portable execution reference and clarifies clip/window
  duration for verified long-video backends.
 - The eight style-specific `SKILL.md` files are rewritten portable adaptations of
  the upstream workflows. Their reference documents retain the relevant creative
  methods while removing host-specific execution assumptions.
 - The two `co-op-game-intro-generator/references/` templates retain the upstream
  creative structure with an added portable contract and explicit user overrides.
  Their instructions are normalized to English, and the video template expresses
  visible UI copy as localized variables with English defaults. It also removes
  an unrequested gender restriction and a fixed yellow/black environment
  transformation.
 - The five 3D animation references are condensed adaptations of their upstream
  counterparts: shot table, storyboards, model selection, fallback, and review.
 - Product, papercraft, collage, and music references extract reusable direction
  from their corresponding upstream skill. The shared portable workflow, catalog,
  and UI metadata are additions for this repository.
 No upstream `LICENSE`, `COPYING`, or `NOTICE` file was present in the Git tree at
 the pinned snapshot. Its README links to the MiniMax H3 Community License on the
 model release. Because that license has redistribution conditions, this package
 does not include the upstream prompt guides verbatim. This provenance record
 preserves attribution and does not assert that this repository's code license
 relicenses upstream material.
 ## Runtime changes
 Canvas documents become local files and asset manifests; choice-card UI becomes
 the host's normal clarification mechanism when a decision is actually missing.
 Available generation/editing tools replace proprietary dispatch calls. Previous
 user choices and authorization persist across steps. Providers, prices, resolution
 support, and long-video features are checked rather than hardcoded as guarantees.
 User intent overrides style presets, including instrumental/no-text work, selected
 language, final morph shape, no-cut sequences, and custom player designs. Native
 generation and external processing remain separately identified in delivery.
@@ -0,0 +1,96 @@
 # Portable MiniMax H3 Skills
 This directory contains one general prompt-writing skill and eight creative
 skills adapted from
 [MiniMax-AI/MiniMax-H3](https://github.com/MiniMax-AI/MiniMax-H3/tree/main/skills).
 See [H3-SOURCES.md](H3-SOURCES.md) for the source revision, attribution, and
 adaptation scope.
 ## Skill catalog
 | Skill | Intended use |
 | --- | --- |
 | [h3-prompt-writing](h3-prompt-writing/SKILL.md) | Structured prompts for T2VA, I2VA, FL2VA, L2VA, and Ref2VA |
 | [minimalist-product-ad-generator](minimalist-product-ad-generator/SKILL.md) | Minimal product ads, isolated product references, copy, and pacing |
 | [3d-animation-short-generator](3d-animation-short-generator/SKILL.md) | 3D narrative shorts, character and environment design, shot tables, storyboards, and editing |
 | [papercraft-stop-motion-explainer](papercraft-stop-motion-explainer/SKILL.md) | Layered paper art, puppets, mechanisms, and miniature educational scenes |
 | [brand-promo-video-generator](brand-promo-video-generator/SKILL.md) | Brand promos, verified assets and claims, product interaction, and calls to action |
 | [music-video-subtitle-generator](music-video-subtitle-generator/SKILL.md) | Music videos, instrumental visual narratives, beat planning, and optional lyric typography |
 | [co-op-game-intro-generator](co-op-game-intro-generator/SKILL.md) | Two-player game menus, confirmation images, and animated world entry |
 | [paper-collage-explainer-generator](paper-collage-explainer-generator/SKILL.md) | Halftone photo collage, incremental paper assembly, and visual metaphors |
 | [handdrawn-live-video-generator](handdrawn-live-video-generator/SKILL.md) | Live action with rough luminous drawings, physical contact, continuous morphing, and delayed pursuit |
 ## Usage
 Codex discovers repository skills from `.agents/skills/`. Clients that scan
 skills only when a session starts may need a new session. Claude Code reads the
 same files through the same-named relative symlinks in `.claude/skills/`. Other
 agents that support Markdown skills can load the relevant `SKILL.md` directly
 and follow its links to supporting references.
 Examples:
 ```text
 Use $music-video-subtitle-generator to design a 30-second two-dimensional
 fluid-motion graphic for this instrumental track. Do not add lyrics or
 subtitles. Preserve leftward motion and initially return only a storyboard and
 three H3 prompts.
 ```
 ```text
 Use $co-op-game-intro-generator to create a two-player game intro. The players
 are Lin and Mei, the style is layered paper sculpture, and the title is
 Together. Create the confirmation image first and wait for my approval before
 generating video.
 ```
 ## MV smoke test
 Test `music-video-subtitle-generator` together with `h3-prompt-writing` using a
 user-owned song with timestamped lyrics and an original adult-character
 reference image:
 ```text
 Use $music-video-subtitle-generator and $h3-prompt-writing to turn this song
 into a historical-romance music video about a woman and a man. Intercut
 narrative acting with the woman's singing performance, do not display lyric
 text, split the work according to the backend's verified clip duration, and
 preserve the complete original song in the final master.
 ```
 Verify that the global timeline matches the source audio duration, lyrics remain
 verbatim, and each generation window records its incoming state, outgoing state,
 and local timing. Ref2VA prompts must preserve the six-section field order and
 resolve every reference label to a real input. The assembled video must decode
 completely, and its final audio must come from the supplied source rather than a
 model reconstruction.
 When moving the collection to another repository or a user-level skill folder,
 copy all nine skill directories and preserve their sibling layout. The eight
 creative skills share `h3-prompt-writing/references/portable-workflow.md` and the
 H3 format guides, so copying only one `SKILL.md` is insufficient. Keep each
 skill's `references/` and `agents/` directories with it. `agents/openai.yaml`
 provides optional Codex UI metadata and does not restrict the workflow to an
 OpenAI-based agent or require a dedicated plugin.
 ## Execution boundaries
 Prompt writing, storyboarding, and planning require only an agent that can read
 and write files. Actual image, video, speech, music, and editing work uses tools
 or services available in the current environment. When a capability is missing,
 deliver the complete usable production package and identify the unfinished media
 step.
 The user's style, language, assets, audio, model selection, and existing
 authorization take priority. An MV template does not add lyrics to an
 instrumental track, and a clean motion-graphics request does not inherit film
 grain. A prompt-only request does not start generation. When the user requests
 approval of a confirmation image before rendering, preserve that checkpoint.
 Treat vLLM-Omni long-video extensions as capabilities of the checked-out branch
 and active backend. Do not present a development branch's continuation parameters
 as a universal H3 API. Preserve real requests and raw outputs, distinguish model
 results from post-production and upscaling, and inspect actual media properties.
 These skills contain no model weights and do not automatically start a service
 or invoke a paid generation endpoint.
@@ -0,0 +1,66 @@
 ---
 name: brand-promo-video-generator
 description: Plan, prompt, or produce brand, product, website, app, and service promotional shorts using traceable assets, accurate claims, timed beats, and clear calls to action. Use for launch and campaign videos, not invented product evidence or long narrative films.
 metadata:
  compatibility: File-based workflow with sibling h3-prompt-writing and available research, media generation, inspection, and editing tools.
 ---
 # Brand Promo Video Generator
 Read the [portable workflow](../h3-prompt-writing/references/portable-workflow.md).
 Use supplied brand assets, source links, and existing session decisions. No
 proprietary tool allowlist or canvas is required. A completed promo requires real
 generation/editing capability; otherwise deliver an explicitly incomplete production
 package with finished prompts and a concrete generation handoff.
 ## Establish facts and assets
 Inspect product images, UI screenshots, logo exports, typography, colors, and
 campaign material. Resolve duration, ratio, audience, campaign focus, exact claims,
 CTA, copy language, narration, and required deliverable from context. Ask for
 missing identity-bearing assets when they are essential; do not fabricate logos,
 product UI, screenshots, results, or performance claims.
 Build a compact truth sheet from user-supplied originals and official sources.
 Record asset ID, role, local path, source URL/note, and verification status. Do not
 confuse a retrieved search thumbnail with an original brand asset. Distinguish
 verified facts from clearly labeled concept copy. Preserve the requested language;
 chat language alone does not justify translating supplied campaign text.
 ## Design a product-specific story
 Choose a spine that exposes real cause and effect:
 - Software: user intent → actual interaction → useful output → evidence → CTA.
 - Physical product: reveal → interaction → mechanism/detail → use → benefit → CTA.
 - Service: situation → process → evidence → outcome → promise.
 - Image-led brand: authentic imagery → repeated visual motif → emotional payoff.
 Plan time/frame ranges, asset IDs, one main action, product evidence, exact copy,
 readable hold, color state, camera, transition, and rhythm. Use the actual output
 fps for frame timing. Five to eight major beats can fit a 15-second promo, but
 readability takes priority over a fixed beat count.
 Let product edges, UI movement, light, cursor paths, or matched geometry motivate
 transitions. Use a few energy peaks and deliberate settling moments. Preserve logo
 clear space and readable screenshots. Avoid invented HUDs or metrics that look like
 product proof. Summarize the truth sheet and plan before rendering; continue under
 existing authorization unless the user requested approval at that stage.
 ## Produce and inspect
 Use authentic still/UI plates for exact content. Generated material can supply
 conceptual scenes, atmosphere, and transition geometry with clear provenance.
 Compile actual H3 references and shots using the appropriate bundled guide.
 Check backend resolution, duration, and audio support before calling it.
 Use native instrumental/SFX direction when appropriate; do not generate a second
 score automatically. Separate narration or music is useful when requested for
 control or remixing. Preserve original SFX during assembly when they matter, and
 duck music under speech. Do not add subtitles unless requested.
 Check claims and exact product names against sources, inspect logo geometry and
 copy, verify real UI states, and review transitions, aspect ratio, duration, audio,
 and decoding. For wrong identity-bearing content, use the correct supplied/source
 asset rather than polishing an imitation. Deliver the video, prompts/timeline,
 asset manifest, and any remaining factual or visual limitations.
@@ -0,0 +1,4 @@
 interface:
  display_name: "Brand Promo Videos"
  short_description: "Build brand promos from verified assets and claims"
  default_prompt: "Use $brand-promo-video-generator to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,73 @@
 ---
 name: co-op-game-intro-generator
 description: Design or generate a two-player co-op game menu and opening animation from player names, title, style, and optional identity references. Use for character-led game intros, not playable game implementation or complex multi-page interfaces.
 metadata:
  compatibility: File-based workflow with sibling h3-prompt-writing and bundled image/video templates. Rendering uses available generation tools.
 ---
 # Co-op Game Intro Generator
 Read the [portable workflow](../h3-prompt-writing/references/portable-workflow.md).
 Before writing a confirmation-image prompt, read
 [h3-confirmation-image-template.md](references/h3-confirmation-image-template.md).
 Before writing the video prompt, read
 [h3-video-prompt-template.md](references/h3-video-prompt-template.md).
 Both templates are required package resources, not remote tools.
 ## Resolve player and style bindings
 Reuse or collect the two player names, game title, visual style, desired duration,
 ratio, and optional identity references. The template defaults to a 15-second,
 16:9 menu-to-world sequence; adapt it to explicit user requirements. Do not assume
 the players' gender, body shape, outfits, or equipment from a generic example.
 Use each portrait only for recognizable identity anchors: face silhouette, hair,
 glasses, proportions, and distinguishing traits. Reinterpret rendering, skin
 texture, lighting, and costume in the selected visual style. If a portrait or body
 comparison reference is absent, write a text design rather than inventing an asset
 label. Maintain player-to-name mapping across all references and frames.
 ## Confirmation image
 Fill the template's style, palette, characters, title, and name variables. Keep
 the two characters central, player cards toward the upper left, menu on the right,
 and the continue action as the main interaction focus. The title establishes
 identity without competing with that focus. Buttons, icons, typography, and all
 player/equipment panels share one palette and style. Keep menu labels on one line.
 The style changes material, shapes, fonts, and decoration; it should not randomly
 rearrange the menu hierarchy. User-requested layout or ratio changes take priority
 over template defaults. Preserve the exact supplied title/names and requested copy.
 For image-only/prompt-only work, stop at that deliverable. For video production,
 generate and inspect the confirmation image if within scope. Honor a request to
 approve the image first; otherwise use the established end-to-end authorization
 and continue after reporting the selected image and fixing material defects.
 ## Video event plan
 Fill the video template from the current image and player bindings. Its baseline
 sequence is menu → first player's light equipment → second player's heavy equipment
 → shared confirmation → world loading → both enter the world. Equipment, world,
 body contrast, and timing are editable design choices; preserve requested identity
 and style instead of forcing a cyberpunk example onto another setting.
 Bind UI reference, each actual portrait, and any real body-comparison image to
 distinct roles. Compile this creative template into the H3 mode guide's fields;
 the mixed-language template is not itself an API request. Preserve literal visible
 UI text in its required language, and remove all unfilled variables before dispatch.
 Do not treat a composition reference as an exact first-frame anchor unless the
 selected backend actually supports that role.
 ## Review and repair
 Check both names, exact menu strings, layout, player identity, side assignment,
 equipment distinction, and the transition into the requested world. Match UI
 hover/click, mechanical locks, loading, and footsteps to the visible events.
 For identity swaps, strengthen name/position/reference bindings; for weak style,
 revise palette, material, character, and typography together. Reduce excessive
 UI text if necessary without silently changing required player names.
 Deliver the requested prompts/assets or the inspected intro video, with reference
 roles and any text/timing limitations. Missing templates block template execution;
 missing generation capability still permits a complete prompt handoff.
@@ -0,0 +1,4 @@
 interface:
  display_name: "Co-op Game Intros"
  short_description: "Design two-player menus and world-entry animation"
  default_prompt: "Use $co-op-game-intro-generator to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,397 @@
 # H3 Confirmation Image Template
 ## Portable adaptation
 This is a creative template, not a tool call. User requirements override its
 default ratio, layout, poses, and wording. Fill every relevant variable from the
 brief; set `{character_count}` to two for this skill. When portraits are absent,
 replace portrait references with explicit character designs. Do not claim to
 reference an image that was not supplied. Use the image-generation capability
 available in the host environment; no specific image provider is required.
 ## Core Rule
 Generate a polished 16:9 landscape confirmation image for a cooperative game main menu.
 The image consists of two independent systems:
 • UI Framework (fixed)
 • Visual Style (dynamic)
 The UI Framework defines the layout, composition, information hierarchy, interaction logic, reading flow, menu structure, and readability. These elements must remain unchanged.
 {visual_style} only controls the artistic appearance, including rendering medium, materials, color language, lighting mood, environment style, character design, costume language, UI materials, icon language, typography appearance, decorative motifs, and overall atmosphere.
 Changing {visual_style} should feel like applying a different art direction to the same professionally designed game menu, never redesigning the interface itself.
 If any default description conflicts with {visual_style}, prioritize {visual_style} while preserving the UI framework.
 ---
 ## Design Goal
 Create a premium commercial console game main menu mockup in 16:9 landscape format. The image should combine the quality of a polished game promotional artwork with the clarity of a professional game UI. Characters and interface must feel naturally integrated, with strong visual hierarchy, excellent readability, clean composition, and a clear interaction focus.
 ---
 ## Overall Style
 Follow the user-selected visual style: {visual_style}.
 The selected style controls the rendering medium, illustration style, materials, palette language, environment, character appearance, outfit design, UI appearance, icon language, typography treatment, decorative elements, and atmosphere.
 All visual elements must belong to one unified artistic language.
 Do not mix incompatible visual styles within the same image.
 The UI framework, layout, hierarchy, composition, and interaction logic must remain consistent regardless of style.
 ---
 ## Color Palette
 Derive the entire color system from {visual_style}.
 Use:
 • {main_background_color} as the primary background color.
 • {ui_body_color} as the main UI color.
 • {text_color} as the primary text color.
 • {functional_accent_color} as the interaction highlight color.
 • Red only for warning, danger, or exit actions.
 Limit the overall palette to five primary colors.
 All buttons, player cards, icons, borders, highlights, decorative elements, typography, and visual effects must follow the same color system.
 Avoid introducing unrelated colors outside the selected palette.
 ---
 ## Composition
 Use a fixed 16:9 landscape layout.
 Place {character_count} playable characters in the center as the visual subject.
 The UI surrounds the characters without blocking them.
 Place the player information cards in the upper-left corner.
 Place the main menu vertically on the right.
 Place a decorative horizontal strip along the bottom, adapting naturally to {visual_style} (such as ribbon, warning strip, wooden plank, stone slab, energy bar, scroll, etc.).
 Keep a clear Z-shaped reading flow:
 Player Cards → Characters → Menu → Continue Button.
 The Continue button must always remain the primary visual focus.
 Maintain generous negative space and excellent readability.
 ---
 ## Background
 Generate a background naturally derived from {visual_style}.
 The background supports the interface rather than competing with it.
 Keep enough clean negative space behind all important UI elements.
 Use subtle textures, environmental details, and decorative motifs only where appropriate for the selected style.
 Avoid excessive visual noise, dense decoration, heavy dirt, scratches, paint splatter, or distracting textures.
 The overall background should feel polished, premium, modern, and suitable for a commercial game menu.
 ---
 ## Character Style
 All characters strictly follow {visual_style}.
 The selected style determines:
 • rendering medium
 • body proportion
 • facial stylization
 • costume language
 • material treatment
 • lighting response
 • animation style
 • overall character quality
 Only the character identity anchors and pose remain fixed. Facial rendering, eye design, nose simplification, mouth shape, skin treatment, expression style, and head proportion must be fully reinterpreted in {visual_style}.
 No default character style may override {visual_style}.
 ---
 ## Character A / PLAYER 1
 ### Identity
 Use character reference image 1 only for identity mapping.
 The reference image donates identity anchors only: recognizable face silhouette, hairstyle, glasses if present, relative facial proportions, and distinctive personal traits.
 It does not donate photographic realism, real skin texture, real-world lighting, camera quality, or the original image style.
 Do not lose the character's identity anchors, but the face must be redesigned into {visual_style}.
 All facial rendering, eye design, nose simplification, mouth shape, skin treatment, expression style, and head proportion must follow {visual_style}.
 Do not swap identity with other characters.
 ### Appearance
 Character rendering, expression, outfit, materials, and accessories are fully derived from {visual_style} while maintaining a recognizable playable-game-character silhouette.
 ### Action
 Character A sits cross-legged on the ground.
 Both hands support the body on the floor.
 The upper body leans slightly backward.
 Character A looks upward toward the camera.
 ---
 ## Character B / PLAYER 2
 ### Identity
 Use character reference image 2 only for identity mapping.
 The reference image donates identity anchors only: recognizable face silhouette, hairstyle, glasses if present, relative facial proportions, and distinctive personal traits.
 It does not donate photographic realism, real skin texture, real-world lighting, camera quality, or the original image style.
 Do not lose the character's identity anchors, but the face must be redesigned into {visual_style}.
 All facial rendering, eye design, nose simplification, mouth shape, skin treatment, expression style, and head proportion must follow {visual_style}.
 Do not swap identity with other characters.
 ### Appearance
 Character rendering, expression, outfit, materials, and accessories are fully derived from {visual_style} while maintaining a recognizable playable-game-character silhouette.
 ### Action
 Character B sits cross-legged on the ground.
 Both hands rest naturally in front of the legs.
 The upper body leans slightly forward.
 Character B looks directly toward the camera.
 ---
 ## Lighting
 Lighting follows {visual_style} while preserving clear readability.
 Use a primary top light, secondary fill light, soft ambient bounce, contact shadows, gentle rim lighting, and high-quality global illumination where appropriate.
 Faces should remain clearly visible.
 Characters must integrate naturally into the environment while maintaining strong separation from the background.
 ---
 ## Game UI
 Create a professional commercial console game main menu.
 The menu structure, interaction hierarchy, spacing, composition, reading flow, and information architecture remain fixed.
 {visual_style} only changes the artistic appearance of the interface.
 The selected style may affect:
 • UI materials
 • surface textures
 • border treatment
 • corner shape
 • decorative motifs
 • color rendering
 • lighting treatment
 • icon language
 • typography appearance
 • interaction effects
 It must NOT change:
 • menu hierarchy
 • button order
 • button placement
 • player-card placement
 • composition
 • interaction logic
 • information architecture
 • readability
 The entire interface should feel like one professionally designed game UI system rather than separate elements assembled together.
 ---
 ## UI Visual Language
 Derive the complete UI appearance from {visual_style}.
 The selected style determines:
 • button materials
 • border language
 • panel materials
 • decorative details
 • edge treatment
 • visual weight
 • highlight style
 • interaction feedback
 • shadow treatment
 • texture language
 Possible materials include wood, stone, paper, leather, cloth, glass, crystal, hologram, neon, metal, ceramic, carved surfaces, painted surfaces, magical energy, pixel blocks, watercolor paper, ink brush, comic graphics or any other material naturally belonging to {visual_style}.
 Every UI element must share the same material language and artistic style.
 ---
 ## Button Layout Rules
 Place all menu buttons vertically on the right side.
 Maintain a consistent vertical rhythm.
 Every button uses the same design family.
 Button width automatically adapts to text length.
 Keep all menu titles on a single line.
 No automatic wrapping.
 No stacked text.
 Text remains horizontally centered.
 Keep consistent padding.
 Maintain equal spacing between buttons.
 Avoid visual clutter.
 ---
 ## Continue Button
 The Continue button is always the primary visual focus.
 Make it visually dominant using the emphasis method naturally belonging to {visual_style}.
 Possible emphasis methods include:
 • larger size
 • stronger contrast
 • brighter color
 • unique material
 • distinctive border
 • lighting
 • glow
 • engraving
 • magical energy
 • holographic effect
 • embossed frame
 • animated visual cue
 Do not force glow or neon if they conflict with {visual_style}.
 The Continue button should immediately attract the player's attention.
 ---
 ## Start New Game Button
 Place above Continue.
 Use the standard secondary button appearance.
 Keep the visual language consistent with the selected style.
 Add one small style-appropriate icon if suitable.
 Maintain single-line text.
 ---
 ## Settings Button
 Use the standard secondary button appearance.
 Use one settings icon naturally derived from {visual_style}.
 Maintain consistent proportions, spacing, and hierarchy.
 ---
 ## Exit Game Button
 Use the standard secondary button appearance.
 Use red only as the danger indicator.
 Red should remain an accent rather than the dominant color.
 Add one style-appropriate exit icon if suitable.
 ---
 ## Player Cards
 Create an upper-left player information system for {character_count} players.
 The appearance follows {visual_style}.
 Card materials, borders, corners, textures, shadows, decorations, and icons are automatically derived from the selected style.
 Each player card contains:
 • Player label
 • Player nickname
 • READY status
 Player names:
 PLAYER 1
 {player1_name}
 PLAYER 2
 {player2_name}
 READY always uses the functional accent color.
 The cards should remain highly readable and visually connected to the rest of the interface.
 ---
 ## Icon System
 Derive all icons from {visual_style}.
 Use one unified icon family throughout the entire interface.
 Possible icon languages include:
 • minimal outline
 • solid filled
 • geometric
 • comic
 • pixel
 • engraved
 • carved
 • painted
 • brush
 • rune
 • glyph
 • holographic
 • crystal
 • paper-cut
 • origami
 • embossed
 • low-poly
 • flat design
 • stylized 3D
 All icons must share:
 • the same artistic style
 • the same material language
 • the same perspective
 • the same lighting treatment
 • the same stroke language
 • the same color hierarchy
 Icons should remain simple, recognizable, and functional.
 Each interface block may contain at most one horizontal row of icons.
 No wrapping.
 No vertical stacking.
 Icons should support the interface rather than dominate it.
 ---
 ## Typography
 Typography hierarchy remains fixed.
 Typography appearance follows {visual_style}.
 The selected style controls:
 • font family
 • decorative treatment
 • texture
 • material
 • outline
 • lighting
 • shadow
 • wear pattern
 Maintain:
 • excellent readability
 • strong visual hierarchy
 • single-line menu buttons
 • consistent spacing
 • high contrast
 Button width should always adapt to text length.
 Never allow menu titles to wrap onto multiple lines.
 ---
 ## Game Title
 Display the game title:
 {game_title}
 The title should become the primary branding element of the menu.
 Its material, decorative style, typography, and rendering all follow {visual_style}.
 Avoid imitating existing commercial game logos.
 Create an original title treatment inspired by the selected style.
 Keep the title highly readable.
 Avoid random symbols or meaningless letters.
 ---
 ## Interaction States
 Represent the interface as an active game menu.
 Buttons may display appropriate interaction feedback naturally belonging to {visual_style}.
 Possible interaction feedback includes:
 • hover
 • pressed state
 • magical glow
 • energy pulse
 • holographic highlight
 • carved illumination
 • ink spread
 • brush bloom
 • metallic reflection
 • paper emboss
 • animated border
 • pixel flashing
 Only use interaction effects that naturally belong to the selected style.
 Avoid forcing modern UI effects into incompatible artistic styles.
 ---
 ## Rendering
 Generate a polished AAA-quality commercial game menu artwork.
 Characters, environment, UI, typography, icons, and decorative elements should feel like one cohesive production.
 Maintain premium rendering quality.
 Strong visual hierarchy.
 Professional commercial presentation.
 High readability.
 Balanced composition.
 Clean finish.
 ---
 ## Negative Constraints
 No split screen.
 No duplicated characters.
 No identity swap.
 No loss of identity anchors. No photorealistic face unless {visual_style} explicitly requires photorealism. No realistic photo face pasted onto a stylized body. No mismatched face style.
 No hairstyle changes.
 No unreadable UI.
 No distorted buttons.
 No overlapping interface.
 No random text.
 No random symbols.
 No watermark.
 No copied game logo.
 No branded interface.
 No inconsistent icon styles.
 No mixed UI materials.
 No excessive decoration.
 No overwhelming background.
 No visual clutter.
 No broken layout.
 No low readability.
 ---
 ## Medium Lock
 Render as a polished commercial game key art combined with a professional console game main menu mockup.
 The interface remains fixed.
 Only the artistic appearance changes according to {visual_style}.
@@ -0,0 +1,249 @@
 # H3 Video Prompt Template
 ## Portable adaptation
 This is a creative planning template. User requirements override its default
 15-second timeline, body proportions, equipment, environment, ratio, and palette.
 Retiming must preserve readable event order. Use only supplied reference assets:
 omit `{height_ref}` or identity-image bindings when absent and replace their role
 with text design constraints. Compile the filled plan into the H3 base or Ref2VA
 format before rendering; preserve exact visible UI strings in the user's language.
 Use available tools and the actual backend's parameter schema. Audio directions
 describe desired content rather than asserting that a particular API supports it.
 ## Template completion
 Resolve the palette variables `{background_color}`, `{ui_color}`, `{text_color}`,
 `{functional_accent_color}`, and `{power_accent_color}` from the selected style.
 Keep the five values distinct enough for readable UI contrast. Use the power
 accent for danger, exit, and warning states unless the user supplies a separate
 semantic-color requirement.
 Fill visible copy in the user's requested language. The following English values
 are defaults only, not mandatory output:
 - `{player1_label}` / `{player2_label}`: `PLAYER 1` / `PLAYER 2`
 - `{ready_label}`: `READY`
 - `{start_label}`, `{continue_label}`, `{settings_label}`, `{exit_label}`:
  `START NEW GAME`, `CONTINUE`, `SETTINGS`, `EXIT GAME`
 - `{player1_equipment_label}`: `RIGHT ARM EQUIPMENT`
 - `{player1_option_a}` / `{player1_option_b}`: `PHANTOM GRIP` / `CHRONOS CLAW`
 - `{player2_equipment_label}`: `ARMAMENT CUSTOMIZATION`
 - `{hand_label}`, `{forearm_label}`, `{elbow_label}`, `{upper_arm_label}`:
  `HAND`, `FOREARM`, `ELBOW`, `UPPER ARM`
 - `{confirm_label}` / `{loading_label}`: `CONFIRM CONFIG` / `LOADING`
 Before compiling the rendering prompt, search the filled template for every
 remaining token enclosed in braces. Replace required values. For an absent optional
 reference, remove its binding and rewrite every dependent clause as a text-only
 constraint. Do not dispatch a prompt while any template token remains.
 ## Prompt principle
 Use the same method as the GPT confirmation-image prompt:
 **Fixed video event framework + dynamic user-style fill + locked character identity + palette-linked UI system.**
 The video prompt must not blindly preserve the source prompt's default style. It must preserve the timeline, UI events, player positions, equipment logic, and text structure, while dynamically rewriting visual treatment, palette, character rendering, lighting, UI surface, icons, and city-world style according to the user's selected style.
 ## Priority order
 1. User-selected style: {visual_style}
 2. Confirmed image / UI reference: {ui_ref}
 3. PLAYER 1 identity reference: {player1_ref}
 4. PLAYER 2 identity reference: {player2_ref}
 5. Height/body comparison reference: {height_ref}
 6. Fixed source video event framework
 ## Reference roles
 - {ui_ref}: confirmed first image. Use it to lock UI layout, menu hierarchy, color system, typography scale, button structure, character-game integration, and overall composition logic.
 - {player1_ref}: PLAYER 1 identity anchor. Lock exact face, hairstyle, glasses if present, facial proportions, body identity, and nickname mapping to {player1_name}.
 - {player2_ref}: PLAYER 2 identity anchor. Lock exact face, hairstyle, facial proportions, body identity, and nickname mapping to {player2_name}.
 - {height_ref}: body comparison anchor. Lock the visible contrast between the two players and prevent identical body proportions.
 ## Global style baseline
 The overall art direction must prioritize the user's selected {visual_style}.
 Preserve these fixed qualities: a game main-menu interface, premium game-trailer
 finish, deep integration between the UI and characters, modern commercial game
 UI design, strong visual impact, clean composition, and restrained decoration.
 Derive the remaining visual treatment from {visual_style}: character rendering,
 expressions, costume language, color system, lighting temperature, UI materials,
 button icons, typography texture, and the world revealed after loading.
 ## Palette system
 Derive the complete video palette from {visual_style}, with linked UI colors:
 - Use {background_color} as the primary background and world color.
 - Use {ui_color} as the main UI color.
 - Use {text_color} as the text color.
 - Use {functional_accent_color} as PLAYER 1's functional accent color.
 - Use {power_accent_color} as PLAYER 2's power accent and for danger, exit,
  and warning states.
 - Limit the complete palette to five colors.
 - Use a vivid, modern, high-contrast color language consistent with
  {visual_style}.
 Menus, equipment panels, player cards, buttons, the HUD, loading bars, icons,
 and text must share this color system. Do not introduce unrelated colors.
 ## Character identity and style lock
 PLAYER 1 follows the facial identity in {player1_ref}. Preserve the face,
 facial proportions, hairstyle, glasses when present, personal identity, and the
 mapping to the nickname {player1_name}. Adapt expression, rendering, clothing,
 and mechanical equipment to {visual_style}. PLAYER 1 always stays on the left,
 with a taller, slender, agile build. Equipment uses the functional accent color,
 and the mechanical claw is light, narrow, and flexible.
 PLAYER 2 follows the facial identity in {player2_ref}. Preserve the face,
 facial proportions, hairstyle, personal identity, and the mapping to the
 nickname {player2_name}. Adapt expression, rendering, clothing, and mechanical
 equipment to {visual_style}. PLAYER 2 always stays on the right, with a shorter,
 broader, power-oriented build. Equipment uses {power_accent_color}, and the
 mechanical fist is broad, heavy, and visibly weighty.
 Do not swap character identities, merge faces, swap nicknames, or converge the
 two body types.
 ## Fixed timeline framework
 ### [0-2 seconds] - Two-player main menu
 Composition and camera: A high-angle extreme wide shot follows the composition
 logic of {ui_ref}. The camera tilts slightly downward and slowly pushes in.
 Visuals: PLAYER 1 ({player1_name}) and PLAYER 2 ({player2_name}) sit side by
 side at the center. PLAYER 1 remains on the left and PLAYER 2 on the right. They
 look up toward the camera with only natural breathing, blinking, and subtle body
 movement.
 UI: The upper-left player card displays `{player1_label}`, `{player1_name}`, and
 `{ready_label}` exactly as filled. The second card in the upper-center or
 upper-left two-card system displays `{player2_label}`, `{player2_name}`, and
 `{ready_label}` exactly as filled. The vertical menu on the right displays
 `{start_label}`, `{continue_label}`, `{settings_label}`, and `{exit_label}`
 exactly as filled. `{continue_label}` is the visual center and primary
 highlighted button.
 Dynamic style fill: Adapt the menu background, ground texture, button shapes,
 icons, typography, borders, glow, and sticker treatment to {visual_style}, while
 preserving the layout and hierarchy in {ui_ref}.
 Sound: Menu ambience, subtle UI-hover sounds, and a low electronic atmosphere
 before the click. Ignore this direction when generating silent video.
 ### [2-4 seconds] - PLAYER 1 right-arm configuration
 Composition and camera: In a medium shot, the camera pushes smoothly from the
 main menu toward PLAYER 1's right arm. PLAYER 2 remains visible and stable in the
 background.
 UI: The right-side menu contracts and slides away. A panel with functional-accent
 guide lines slides in from the left and displays `{player1_label}` and
 `{player1_equipment_label}` exactly as filled. The equipment list first
 highlights `{player1_option_a}`, then moves the selection to
 `{player1_option_b}`.
 Action: PLAYER 1's right cuff opens automatically and a lightweight mechanism
 unfolds beneath the forearm. The fingers spread as long claw-like joints slide
 into position and lock one by one, briefly revealing fine wiring, miniature
 pistons, and metal connectors. Functional-accent LEDs illuminate sequentially
 when configuration completes.
 Dynamic style fill: Adapt the mechanism, panel material, icons, lines, locking
 animation, and light effects to {visual_style}. Keep the result light, precise,
 and flexible, proportioned to PLAYER 1 without changing the face, hairstyle, or
 main clothing design.
 Sound: Precise mechanical unfolding, light UI switching tones, and small locking
 clicks.
 ### [4-7 seconds] - PLAYER 2 heavy-arm configuration
 Composition and camera: A medium shot tracks smoothly between the players and
 arcs toward PLAYER 2's left side. PLAYER 1 remains in the background, quietly
 examining the configured mechanical hand.
 UI: A {power_accent_color} panel slides in and displays `{player2_label}` and
 `{player2_equipment_label}` exactly as filled. Its grid contains `{hand_label}`,
 `{forearm_label}`, `{elbow_label}`, and `{upper_arm_label}`, with the selection
 moving quickly but legibly through all four.
 Action: PLAYER 2's left sleeve opens in sections. Heavy forearm plates spring
 outward, the previous components detach, and new armor slides into place along
 guide rails. A thick mechanical bearing replaces the elbow joint, and the broad
 mechanical hand reassembles and locks. Thick wiring, hydraulic pistons, and a
 dark metal skeleton appear briefly during the replacement. A restrained warm
 indicator illuminates as each component locks.
 Dynamic style fill: Adapt the heavy arm, UI panel, component icons, materials,
 and light effects to {visual_style}. Keep it broad, weighty, and powerful, in
 clear contrast with PLAYER 1's lightweight claw.
 Sound: Low motor movement, heavy mechanical engagement, and weighty locking
 feedback.
 ### [7-8.5 seconds] - Shared configuration confirmation
 Composition and camera: Pull back smoothly to a medium two-player composition,
 with PLAYER 1 on the left and PLAYER 2 on the right.
 UI: The two equipment panels converge at center to form a shared button that
 displays `{confirm_label}` exactly as filled. Adapt its border, glow, icon, and
 sticker treatment to {visual_style}, while keeping the hierarchy and text legible.
 Action: The cursor clicks the button. A functional-accent energy pulse travels
 through PLAYER 1's mechanical claw, while a {power_accent_color} pulse travels
 through PLAYER 2's fist. All UI panels contract inward and disappear. Both
 players uncross their legs and adjust their posture: PLAYER 1 lifts one knee
 lightly and articulates the claw fingers in sequence; PLAYER 2 plants one foot
 firmly and slowly closes the heavy fist.
 Sound: Confirmation tone, two-color energy pulses, and UI contraction.
 ### [8.5-10 seconds] - Shared world loading
 Composition and camera: A wide shot reveals a shared loading bar at the bottom.
 UI: The loading bar displays `{loading_label}` exactly as filled and fills
 rapidly from 0% to 100%. Its left half uses {functional_accent_color} and its
 right half uses {power_accent_color}. Adapt the HUD and loading-bar shape,
 border, texture, and typography to {visual_style}, while keeping them legible.
 Environment transformation: Continuously transform the confirmed
 {visual_style} menu background into a game world in the same style. Menu strips,
 color blocks, and patterns become corresponding roads, structures, and world
 elements. Preserve the confirmed palette rather than forcing a yellow-and-black
 or cyberpunk city.
 Key constraint: The transformation remains continuous and natural, with no hard
 cut, smoke occlusion, or identity change.
 Sound: Rising loading tone and an ambience transition from menu to game world.
 ### [10-15 seconds] - Two-player world entry
 Composition and camera: Move from an extreme wide shot into a third-person
 tracking view. At 100% loading, both characters stand simultaneously. The camera
 descends smoothly and arcs behind them into a stable two-player cooperative view.
 World style: Generate the complete world from {visual_style}. Preserve the game
 opening structure: dense buildings, roads, signal lights, signs, crowds or other
 moving background elements, passing vehicles, overhead wires, industrial pipes,
 and a distant skyline. Materials, architecture, signage, lighting, and motion
 must follow {visual_style}. Do not let the source template's cyberpunk default
 override the user unless the selected style is cyberpunk.
 Character relationship: Clearly show the players from behind and preserve their
 body contrast. PLAYER 1 is on the left, tall and slender, with the lightweight
 claw hanging naturally. PLAYER 2 is on the right, shorter and broader, with the
 heavy fist slightly raised. PLAYER 1 steps forward first, PLAYER 2 follows, and
 they enter the street side by side.
 HUD: The HUD fades in. A mini-map appears in the upper right. Separate status
 bars labeled `{player1_name}` and `{player2_name}` appear in the lower left.
 The first uses {functional_accent_color}; the second uses {power_accent_color}.
 A shared objective marker appears in the street ahead.
 Sound: City ambience, distant vehicles, footsteps, and a HUD fade-in cue.
 ## Negative constraints
 No extra player, duplicated character, identity or username swapping, merged bodies, unintended face/hair changes, missing player, unrequested split screen or cuts, random camera shake, floating body parts, gruesome dismemberment, unwanted weapons, style-incompatible neon, unreadable UI, random letters, misspelled usernames, extra menu options, copied game logo, or watermark. Preserve the user's chosen character designs and palette.
@@ -0,0 +1,42 @@
 ---
 name: h3-prompt-writing
 description: Write MiniMax H3 video generation prompts for T2VA, I2VA, FL2VA, L2VA, and Ref2VA. Use when rewriting multimodal requests into H3 prompt structures, composing integrated_multimodal_description, overall_soundscape, and non_diegetic_music, aligning keyframes, or defining reference labels for images, videos, and audio.
 metadata:
  compatibility: Portable to any agent that can read local files — no external API calls, MiniMax Hub tools, or proprietary runtime required. The agents/openai.yaml file only adds optional ChatGPT/Codex UI metadata; it does not restrict the skill to OpenAI agents.
 ---
 # H3 Prompt Writing
 ## Workflow
 0. Read [portable-workflow.md](references/portable-workflow.md) for scope, available tools, durable artifacts, and generation handoff. For prompt-only work, no generation tools are required.
 1. Identify the input mode: T2VA, I2VA, FL2VA, L2VA, or full-reference Ref2VA.
 2. For base text/keyframe modes, read `references/base-format.md` and follow its final prompt structure.
 3. For full-reference mode, read `references/ref-format.md` and follow its six-section rewrite format.
 4. Preserve the exact field names, section order, labels, and timing notation from the selected guide.
 ## Base Modes
 - T2VA: build the full audiovisual timeline from text.
 - I2VA: start from the first frame and develop forward from it.
 - FL2VA: describe the continuous path between the first and last frames.
 - L2VA: infer a plausible opening and converge to the supplied last frame.
 Use `integrated_multimodal_description`, `overall_soundscape`, and `non_diegetic_music` in the order shown in `references/base-format.md`.
 ## Full-Reference Mode
 Ref2VA rewrites use `subject_definitions`, `summary`, `retention_analysis`, `detailed_description`, `overall_soundscape`, and `non_diegetic_music` in that order. Reference labels stay consistent across all sections.
 Read `references/ref-format.md` for label rules and retention analysis.
 ## Output Rules
 - Write rewrite sections in English; preserve dialogue, lyrics, and visible scene text in their original language.
 - Describe each shot by composition, subjects, environment, actions, camera, sound, and the exact point where referenced content appears.
 - Avoid plot summaries, unresolved reference labels, and timing that does not match the requested duration.
 ## Tips for Better Results
 - Match the description to the effective duration of the current clip or generation window. The upstream guides describe 4–15-second clips; longer work requires a verified backend extension or an explicit assembly plan, as described in the portable workflow.
 - Keep reference labels consistent (e.g. `<Picture 1>`, `<Video 1>`, `<Audio 1>`) across every section.
 - Prefer concrete visual and audio details over abstract words like "cinematic" or "beautiful".
 - When using keyframes (I2VA / FL2VA / L2VA), clearly state how the first and/or last frame connects to the timeline.
@@ -0,0 +1,4 @@
 interface:
  display_name: "H3 Prompt Writing"
  short_description: "Write structured H3 prompts for each input mode"
  default_prompt: "Use $h3-prompt-writing to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,86 @@
 # H3 base-mode prompt format
 Use this reference for T2VA, I2VA, FL2VA, and L2VA prompt writing. It is a
 compact, repository-authored description of the required output contract, not a
 copy of an upstream prompt guide.
 ## Select the anchor mode
 - T2VA has no image anchor. Build the audiovisual sequence from the brief.
 - I2VA binds `<Picture 1>` to the first frame at 0.00 seconds.
 - FL2VA binds `<Picture 1>` to the first frame and `<Picture 2>` to the final
  frame. Describe the observable path between them.
 - L2VA binds `<Picture 1>` to the final frame. Infer a compatible opening and
  converge to the supplied image.
 For an image-anchored mode, put a plain-English alignment statement before the
 structured fields. State each picture label, its shot, and its exact target time.
 The ending time must match the effective clip duration, formatted to two decimal
 places. Do not invent a picture label when no image was supplied.
 ## Emit three fields in order
 ```text
 integrated_multimodal_description: [Shot 1] ...
 overall_soundscape: ...
 non_diegetic_music: ...
 ```
 `integrated_multimodal_description` is the playback-ordered visual and diegetic
 audio plan. Establish the initial style, framing, subjects, environment, and
 spatial relationships, then describe actions and state changes. For keyframe
 modes, explicitly preserve or approach the relevant composition, identity,
 clothing, colors, objects, and geometry.
 `overall_soundscape` summarizes ambience, physical effects, and non-verbal human
 sound. Do not repeat dialogue or music already described elsewhere. Use `N/A`
 only for explicitly silent output.
 `non_diegetic_music` describes music heard by the audience but not the characters.
 Specify audible properties such as instrumentation, tempo, rhythm, dynamics, and
 ending behavior. Put source-visible music, singing, radio, or instrument playing
 in the main description. Use `N/A` when no score is wanted.
 ## Timeline notation
 - Start the opening with `[Shot 1]` and no timestamp.
 - Mark each later cut with a sequential label and a strictly increasing time,
  for example `[Shot 2] At 00:03.500, ...`.
 - Use a new shot for an actual edit or meaningful viewpoint/time change. Keep a
  continuous action or morph in one shot and describe its internal timing.
 - Describe camera motion as an action: type, direction, useful amplitude, and
  speed. Do not append a disconnected list of camera keywords.
 - Keep every cut and event within the requested clip duration.
 ## Speech, text, and sound
 Give each speaking or singing source a stable ID such as `(S1)` or `(S2)` and
 reuse it across shots. Put only the language tag and literal words inside the
 dialogue wrapper:
 ```text
 The courier (S1) says softly: <d>[English] The gate is open.</d>
 ```
 Preserve supplied dialogue, lyrics, punctuation, and visible text verbatim. State
 when a voice is off-screen and keep the visible character's lips closed when that
 is required. If a line spans a cut, describe the audio continuity on both sides
 of the cut. Place visible signs, labels, and interface copy in double quotes.
 Tie diegetic sounds to the event that produces them. Avoid describing the same
 sound as both diegetic and non-diegetic.
 ## Anchor-specific checks
 - I2VA: begin from the supplied frame rather than merely borrowing its style.
 - FL2VA: describe intermediate motion; do not provide two unrelated still-image
  descriptions. Reach Picture 2 at the actual end time.
 - L2VA: keep the final picture assigned to the last shot, not automatically to
  Shot 1, and make the preceding action physically plausible.
 - All modes: reference labels must map to supplied assets and remain stable.
 Before delivery, verify the field order, shot numbering, timestamps, reference
 labels, dialogue fidelity, requested language, duration, and absence of unresolved
 template variables.
@@ -0,0 +1,121 @@
 # Portable H3 production workflow
 This is the runtime contract for the nine H3 skills in this repository. Read it
 alongside the selected creative skill. The bundle uses local files and available
 tools; no proprietary canvas, choice-card widget, planner, or executor is required.
 ## Scope and decisions
 - Resolve the requested deliverable first: prompt, storyboard, assets, or finished
  video. A prompt-only request ends with the prompt; it does not start generation.
 - Reuse the user's duration, language, style, model, audio policy, supplied assets,
  and existing authorization. State reasonable defaults for optional gaps. Ask
  only about missing inputs or choices that materially affect the requested work.
 - Creative checkpoints are reviewable artifacts, not mandatory repeated approvals.
  Honor an explicit request to approve a preview before rendering. When the user
  has authorized the complete workflow or delegated creative choices, show the
  plan and continue within that scope without requiring a special UI control.
 - A skill never grants permission to publish, send messages, spend outside an
  authorized budget, or change models against the user's choice. User constraints
  override a preset's style, language, shot count, timing, or audio defaults.
 ## Tools and durable artifacts
 1. Inspect the actual available tools, existing scripts, endpoint documentation,
   and supplied media. Do not invent a tool name, model parameter, or returned path.
 2. Write plans and prompts to the user-selected project folder. If none is given,
   use a new named folder under `outputs/`, outside the skill package. Keep useful
   artifacts such as `brief.md`, `storyboard.md`, `prompts/`, `references/`,
   `clips/`, and `final/`; create only those needed for this deliverable.
 3. Record each reference's role and path: identity, environment, style, typography,
   first/last frame, or audio. Tie generated clips to the prompt revision, input
   assets, model, settings, and output paths. Update downstream references when an
   asset changes; retain previous outputs instead of overwriting user files.
 4. Use available image generation/editing tools for requested raster assets. Use
   an available video endpoint or local service for clips, and available audio
   tooling for requested standalone speech/music. For assembly and inspection,
   use an installed editor or tools such as FFmpeg, ffprobe, and OpenCV. Follow the
   host's tool policies, including its preferred image generation mechanism.
 5. Independent tool jobs may run concurrently when resources permit; this skill
   does not require separate agents or delegated generation.
 6. If a required capability is missing, finish the useful in-scope preparation:
   complete prompts, asset-role manifest, timeline, and verified request example
   where possible. State the missing capability and unfinished media step. Do not
   silently substitute another model, claim a render happened, or call a written
   plan a completed video. Resume generation when the capability becomes available.
 ## Compile the creative plan into H3 prompts
 Read [base-format.md](base-format.md) for T2VA / I2VA / FL2VA / L2VA, or
 [ref-format.md](ref-format.md) for Ref2VA. These are writing modes, not guaranteed API
 task names. Check the selected backend's input mapping before sending a request.
 - Base prompts use `integrated_multimodal_description`, `overall_soundscape`,
  `non_diegetic_music`, in that order, with the appropriate keyframe preamble.
 - Ref2VA uses `subject_definitions`, `summary`, `retention_analysis`,
  `detailed_description`, `overall_soundscape`, `non_diegetic_music`, in that order.
 - Every reference label must resolve to a supplied asset, in the same order used
  by the backend. Omit nonexistent optional references and their dependencies.
 - Keep the creative brief in the user's language. Structured H3 rendering prompts
  use English prose and exact field labels, while dialogue, lyrics, and visible
  text retain their requested language and wording. If the user explicitly wants
  only a same-language creative prompt, deliver that without silently replacing it
  with English. Compile a separate rendering prompt when generation is requested.
 - `[Shot 1]` has no initial timestamp. Later shot labels mark actual cuts. For a
  continuous morph, describe timed actions inside one shot rather than turning
  each form into a new shot. Express camera direction, speed, and useful amplitude.
 - Separate image style from character identity. A style reference must not inject
  its people, scenery, layout, typography, texture, or lighting into unrelated
  shots. For literal text fidelity, inspect the rendered result; a prompt is not
  proof that the exact lettering or beat synchronization was achieved.
 ## Longer videos and audio
 Use the actual backend's supported duration, dimensions, frame grid, reference
 count, audio modes, and model partition. Inspect this checkout's H3 implementation
 or serving documentation before building requests. Do not assume that a feature
 branch's long-video extension exists on main or on a hosted service.
 For a verified vLLM-Omni Ref2VA continuation backend, `long_video=true` with
 `long_video_mode=continuation` can accept one `continuation_prompts` entry per
 planned window only when the Ref2VA request is executed with its local text
 encoder. Step execution and stages that use an external text encoder reject
 `continuation_prompts`; omit the field and use the supported per-step inputs in
 those configurations. Compute the window count from the aligned total frames,
 window size, and overlap. Each prompt uses local window time; track global
 shot/music time separately. Repeated overlap is guidance, not additional output
 duration. Do not use this mode on a task/partition that does not support it.
 Otherwise split into supported clips and assemble them. Same-scene clips may use
 tail/head keyframe continuity when supported. Scene changes should have explicit
 new scene references; a previous scene's latent tail can preserve the wrong
 setting. Choose cuts, morphing, and transitions from the brief rather than imposing
 hard cuts whenever a work exceeds 15 seconds. Generation windows and visual shots
 are different: one window may contain cuts, and one shot may span multiple windows.
 For supplied music, use the selected excerpt as the master timeline unless the
 user requests replacement. For native audio, write the musical/SFX direction in
 the prompt and verify that the backend actually returns audio. Do not invent a
 generic `generate_audio` parameter. If available, locked-source audio latents guide
 generation but the audio-VAE reconstruction is not bit-identical to the source.
 Use explicit final audio stream-copy when an exact original track is required.
 Prompted BPM is a target, not measured timing. Avoid automatically adding lyrics,
 voiceover, subtitles, or multiple competing scores to an instrumental request.
 ## Verification and bounded recovery
 Inspect reference images before using them. After rendering, inspect representative
 frames, transitions, opening/ending states, text, identities, and scene continuity.
 Check audio by listening when possible; report any limit on audio review. Check
 duration, dimensions, fps, frame count, audio presence, and decode validity with
 media tools. If preserving audio exactly, compare extracted audio stream hashes.
 Correct a demonstrated failure with a targeted change to the affected prompt,
 reference, or edit. Keep raw generation alongside edited/upscaled versions and
 label the difference. Use an agreed retry/resource budget; absent one, allow one
 targeted rerender, then report persistent defects and concrete options rather than
 entering an unbounded generation loop. Do not switch providers automatically.
 Deliver actual artifact paths, the prompts/settings needed to repeat the work,
 and material visual/audio limitations. Distinguish requested behavior, observed
 model output, and post-production repairs.
@@ -0,0 +1,105 @@
 # H3 full-reference prompt format
 Use this reference for Ref2VA prompt writing. It is a compact,
 repository-authored description of the output contract, not a copy of an
 upstream prompt guide.
 ## Emit six fields in order
 ```text
 subject_definitions: ...
 summary: ...
 retention_analysis: ...
 detailed_description: [Shot 1] ...
 overall_soundscape: ...
 non_diegetic_music: ...
 ```
 Write the structural prose in English. Preserve the requested language and exact
 wording for dialogue, lyrics, and visible text.
 ## Reference labels
 Assign labels only to supplied content and keep every label stable across all six
 fields:
 - `<Subject N>` identifies reusable visible content such as a person, object,
  environment, costume, interface, action, or visual treatment.
 - `<Picture N>` identifies an image used as a concrete frame, composition, or
  storyboard anchor. If an image only defines a subject, cite it in that subject's
  definition instead of inventing a separate target-frame role.
 - `<Video N>` identifies a source video being edited or continued, or a video
  whose temporal structure is referenced.
 - `<Audio N>` identifies a supplied audio signal that is copied or referenced.
  Audio and video label numbers are independent even when they came from one file.
 In `subject_definitions`, give each tracked item a separate line. State its source,
 role, and the features that later sections must preserve or transform. Do not
 create labels for assets or roles that do not exist.
 ## Summary and retention
 `summary` is one short paragraph describing the target and the principal reference
 relationships. Use only labels already defined. Distinguish these operations:
 - a concrete image frame anchor;
 - generation guided by identity, style, action, camera, or audio characteristics;
 - direct editing of a source video;
 - continuation from a source video;
 - copying an audio signal;
 - referencing audio properties without copying the signal.
 `retention_analysis` has one line per label and states where it is used and what
 changes. Use consistent machine-readable relationship values:
 - Visual: `fully_preserved`, `partially_preserved`, `attribute_transfer`, or
  `weak_reference`.
 - Audio: `fully_copy`, `partially_copy`, `reference`, or `weak_reference`.
 Explain the concrete retained and changed traits after the relationship value.
 Do not claim full preservation when identity, geometry, timing, or signal content
 is intentionally altered. Do not count newly requested target action as an
 unintended loss of reference fidelity.
 ## Detailed description
 `detailed_description` is the playback-ordered rendering plan. For each shot,
 cover the current composition, subject appearance and position, environment,
 lighting, actions and state changes, camera behavior, diegetic sound, and the
 point at which each reference becomes relevant.
 - Start with `[Shot 1]` and no timestamp.
 - Give later cuts sequential labels with strictly increasing times, such as
  `[Shot 2] At 00:03.500, ...`.
 - Place relevant reference labels next to the described subject, frame, motion,
  or sound; do not collect detached labels at the end.
 - Use stable `(S1)`, `(S2)`, and subsequent IDs for vocal sources. Put literal
  speech or lyrics inside `<d>[Language] ...</d>`.
 - Preserve supplied visible text verbatim and place it in double quotes.
 - Describe continuous transformations inside one shot unless an actual cut is
  intended. State camera direction, speed, and amplitude when useful.
 For video editing, explicitly identify what stays from the source timeline and
 what is replaced. For continuation, distinguish the inherited opening state from
 new content. For style reference, transfer visual properties without accidentally
 copying people, scenery, layout, or typography.
 ## Audio fields
 `overall_soundscape` summarizes ambience, physical action sounds, and non-verbal
 human sounds. `non_diegetic_music` describes score audible only to the audience.
 Keep dialogue and diegetic music in `detailed_description`. Use `N/A` only when
 the corresponding layer is intentionally absent.
 If audio is copied, state whether the whole signal or only a range/layer is used.
 If it is referenced, describe the specific property—such as voice timbre, tempo,
 rhythm, or texture—without claiming signal reuse.
 Before delivery, verify the six-field order, one-to-one label definitions,
 retention coverage, shot timing, dialogue fidelity, requested language, and
 absence of unresolved template variables.
@@ -0,0 +1,69 @@
 ---
 name: handdrawn-live-video-generator
 description: Write or generate a continuous live-action scene with a rough luminous hand-drawn entity that contacts real objects, morphs, and escapes a slightly delayed handheld camera. Use for gentle surreal mixed-media shorts, not flat-vector-only animation or horror clips.
 metadata:
  compatibility: Portable prompt writing with sibling h3-prompt-writing; actual generation requires an available video backend and any referenced media.
 ---
 # Handdrawn Live-Action Fusion
 Read the [portable workflow](../h3-prompt-writing/references/portable-workflow.md).
 Keep the user's requested scope and language. A creative-prompt request delivers
 the prompt, without generating media. For a requested finished video, prepare
 the prompt and proceed under existing authorization using available tools.
 ## Creative contract
 The default is a 15-second, 16:9 continuous scene in an everyday real space. A
 flat luminous drawn entity visibly contacts a real hand/object early, transforms
 as one traceable being, escapes through connected space, and the handheld camera
 reacts slightly late. Duration and ratio follow the user's explicit choices.
 Use rough crayon, chalk, colored pencil, pastel, or brush strokes with uneven fill,
 frayed edges, line jitter, and frame-by-frame redraw. Keep the live-action setting
 physically grounded and the drawn presence visibly planar. Uniform neon tubes,
 plush characters, polished CG, and clean vector strokes would change this style.
 Choose a fresh setting, entity, palette, contact mechanism, transformation chain,
 escape route, camera reaction, and emotional ending within the user's constraints.
 Do not ban an otherwise requested motif simply because an upstream example used
 it. The tone is warm, playful, and gently surprising rather than threatening.
 ## Timed action structure
 For a 15-second brief, use these intervals as a starting structure:
 - 0–3s: establish obvious real/drawn contact, such as landing on a palm or slipping
  around a finger. The real participant reacts.
 - 3–6s: begin a continuous morph while retaining a color smear, line, curve, or tail
  from the previous shape. Give it a playful action.
 - 6–10s: let it escape into an adjacent part of the same space. The camera pans,
  tilts, or moves only after the entity starts leaving its view.
 - 10–13s: add another readable interaction or surprise, keeping the same entity.
 - 13–15s: extend an earlier drawn motif across the space into a gentle larger
  transformation, then resolve with a small emotional/comic detail.
 Retiming changes the intervals proportionally or reorganizes beats; do not leave
 15-second timestamps in a shorter prompt. Preserve a user's explicit final form
 instead of forcing the spatial finale when it conflicts with their ending.
 ## Prompt delivery and rendering
 For a same-language creative prompt, begin with duration, ratio, real space, and
 the live-action/drawing fusion. Then describe phone-camera texture, the timed
 action intervals, drawn material, camera lag, specific exclusions, and ambient
 sound. Avoid unrelated headings or an essay when the user asked for copy-ready text.
 For actual H3 generation, create a separate structured rendering prompt using the
 appropriate base/Ref2VA guide: English prose with literal dialogue/visible text in
 the requested language. Preserve the creative intent and actual media bindings.
 Do not send unsupported model settings or promise exact first-frame conditioning
 merely because an image is present.
 ## Review
 Check clear early physical contact, one continuous entity, connected geography,
 retained shape motifs, delayed camera reaction, rough planar drawing, and a
 non-threatening ending. Avoid jump scares, sudden blackouts, menacing anatomy, and
 unrequested extra characters. Deliver the actual prompt/video and state any
 remaining contact, continuity, texture, or camera-timing defects.
@@ -0,0 +1,4 @@
 interface:
  display_name: "Handdrawn Live-Action Fusion"
  short_description: "Direct drawn morphs and real-world interactions"
  default_prompt: "Use $handdrawn-live-video-generator to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,71 @@
 ---
 name: minimalist-product-ad-generator
 description: Plan, prompt, or produce minimalist product advertising shorts from product images, preserving variants, material, color, concise typography, and rhythmic camera motion. Use for product launches and ecommerce films, not presenter-led ads or complex UI demonstrations.
 metadata:
  compatibility: File-based agent workflow. Requires the sibling h3-prompt-writing package; rendering uses available image, video, audio, and editing tools.
 ---
 # Minimalist Product Ad Generator
 Read the [portable workflow](../h3-prompt-writing/references/portable-workflow.md).
 Use [product direction](references/product-direction.md) when planning anchors,
 copy, and timed beats. Respect the requested output: prompt-only work needs no
 generation tool, while a finished film includes generation, inspection, and assembly.
 ## Resolve the product brief
 Inspect supplied product photos, packaging, renders, and detail shots. Record the
 product category, main variant, actual body/accent colors, material finish, usable
 mechanisms, and requested copy. Preserve identity and product facts; visual polish
 does not authorize recoloring the product or inventing a feature.
 Reuse the specified duration, ratio, language, and model. With no constraints,
 suggest a 10-second H3 film and one of white studio, dark rim light, brand color
 field, or light lifestyle staging. Ask for a missing product reference when exact
 identity is required; distinguish a speculative concept from an existing product.
 If the user delegates direction, record the adopted choices and proceed.
 ## Design the film
 1. Choose a product-specific spine: launch reveal, mechanism interaction, or color
   family. Describe concrete actions such as a lid opening or a crown turning.
 2. Write short sensory/benefit copy grounded in supplied facts. Preserve the user's
   exact approved wording and language. For newly requested English copy, 3–5 words
   usually fit one readable line; do not force English on other-language campaigns.
 3. Plan three independent anchors: hero silhouette, material/mechanism detail, and
   final product/copy composition. Generate only the assets needed or requested.
   Do not combine them into a panel sheet that the video model might reproduce.
 4. Keep product color, light direction, ratio, and finish consistent across anchors.
   Original photos establish identity; generated anchors must pass that identity
   check before they can replace them as rendering references.
 5. Build the beat table from the reference. Include setup, action, impact, and a
   stable closing composition; vary shot distance only when it reveals something.
 ## Prompt and render
 Compile each beat into the appropriate H3 fields using the sibling writing guide.
 Bind every anchor to its actual role. Include exact visible copy, entry/exit times,
 colors, and same-line text motion in the rendering prompt, not only in the plan.
 Keep typography in intentional negative space without covering the product. A
 copy-reference image does not mean its line must persist throughout the whole film.
 For a short ad, prefer one coherent full-frame film when the backend supports it.
 Keep variants ordered: main variant first, supporting variants later, full family
 only when useful at the close. Avoid product walls, grids, or an anchor-sheet ending.
 Use native audio when appropriate to the brief. A restrained electronic score may
 use crisp plucks, airy pads, kick/sub accents and tactile wooden percussion. Set
 tempo and energy from the user's direction. Generate a separate score only if
 requested or needed for a disclosed audio repair, using an available tool.
 ## Review and deliver
 Verify product geometry, variant colors, functional action, final copy, aspect
 ratio, and closing readability. Listen for excessive bass, dropouts, and unfinished
 endings. If editing to supplied music, select a suitable continuous excerpt and
 align visual impacts to observed beats; do not claim synchronization from text alone.
 For bad typography, first reduce simultaneous text or correct its reference. Exact
 lettering may need a disclosed overlay when consistent with the user's goal; keep
 the raw output. Deliver the film, prompt/beat plan, used copy and music excerpt,
 and any remaining product/text fidelity issues.
@@ -0,0 +1,4 @@
 interface:
  display_name: "Minimalist Product Ads"
  short_description: "Direct product anchors, copy, motion, and audio"
  default_prompt: "Use $minimalist-product-ad-generator to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,52 @@
 # Product anchors, typography, and beats
 ## Narrative choices
 - Launch: negative space → hero product → material detail → real mechanism action
  → supporting variants → stable product and copy.
 - Feature touch: stillness → interaction trigger → visible mechanism → detail
  magnification → useful result → closing.
 - Color family: main variant alone → supporting colors enter → ordered relation
  → unified material finish → full set and copy.
 ## Independent anchor briefs
 | Anchor | What it locks | Check |
 | --- | --- | --- |
 | Hero | Main variant, recognizable silhouette, attractive opening view | Match supplied body color and product structure |
 | Detail | Material, reflection, texture, visible mechanism | No invented ports, controls, or functionality |
 | Closing | Product position, negative space, typography treatment | Real copy, readable contrast, no panel/grid layout |
 Each is a standalone full-frame image with the project ratio. Reference roles
 protect appearance and layout; they do not replace the storyboard or require three
 sequential static-image segments. Simplify the number of anchors if the backend
 cannot bind them all, and update the prompt labels accordingly.
 ## Typography
 Use one readable line at a time, with a typeface appropriate to the brand. A clean
 semibold sans-serif is a useful default, not a requirement to copy a specific brand.
 For a two-part color treatment, use dark text on a light field or light text on a
 dark field, then emphasize the second part with a specific real product color.
 Check contrast rather than blindly coloring text like the product.
 The first phrase may enter gently; the second follows while the first shifts
 slightly within the same line. Do not accidentally turn this into stacked lines.
 Use actual copy in the prompt and spell out its timing. Avoid arrows, separators,
 or placeholder marks that the model may reproduce. For a 10-second ad, one middle
 copy moment and one stable closing line are often enough. Omit copy when requested.
 ## Beat table
 | Time range | Shot purpose | Visual lead and camera | Variant state | Exact copy | Text color/motion | Handoff | Rhythm |
 | --- | --- | --- | --- | --- | --- | --- | --- |
 Use one main action per beat. For 5/10/15-second films, roughly 3–4/5–7/6–9 beats
 are planning suggestions, not required cuts. Record the ending product position
 and motion vector so the next beat can inherit them. Ensure the closing line has
 time to be read rather than using every second for motion.
 If replacing music, keep useful SFX unless replacement of the whole track was
 requested. Use a continuous excerpt with a clear entry, stable middle, and suitable
 ending. A short tail fade may resolve a click; do not hide an incomplete phrase
 behind a long fade. Confirm the entire result remains audible.
@@ -0,0 +1,74 @@
 ---
 name: music-video-subtitle-generator
 description: Plan, write, audit, or produce music videos with coordinated music, imagery, camera motion, optional performance, and lyric typography. Use for beat-aware MVs and instrumental visual narratives, not ordinary subtitle cleanup or unrelated video edits.
 metadata:
  compatibility: File-based workflow with sibling h3-prompt-writing; audio analysis, generation, and final assembly use available tools and backends.
 ---
 # Music Video and Lyric Typography
 Read the [portable workflow](../h3-prompt-writing/references/portable-workflow.md)
 and, when building a timeline, [music timeline](references/music-timeline.md).
 Deliver the requested scope: audit, prompt, storyboard, or complete video.
 ## Lock the musical and visual intent
 Identify duration, ratio, output resolution, music source/excerpt, visual style,
 character/scene references, performance mode, and whether text is wanted. Treat a
 supplied song as the master track unless the user requests replacement. Preserve
 provided lyrics exactly; do not translate or rewrite them unasked. For instrumental
 work, do not invent singing, lyrics, a performer, or typography. Generate original
 lyrics only when requested or clearly within an authorized songwriting brief.
 Measure supplied audio duration and inspect/listen for beat, phrase, breath, drop,
 and energy changes using available tools. Label estimated or planned timing when
 measurement is unavailable. If the requested excerpt exceeds the audio, resolve
 the discrepancy without silently stretching or looping it.
 ## Reference roles
 - Character references control identity, silhouette, wardrobe, and presence.
 - Scene references control environment, time of day, spatial anchors, and lighting.
 - Typography references control letter treatment, layout, and motion, not people
  or scenery visible in those references.
 - Music references control the requested track or sound style; distinguish copying
  a supplied recording from generating similar instrumentation.
 Do not apply a preset's grain, darkness, hard cuts, or constant close-ups to an
 incompatible brief. A bright nighttime scene remains night. A continuous flat
 vector morph keeps smooth color fields and uses elastic shape motion for accents.
 Use hard cuts, slow holds, or dissolves only when appropriate to the user's intent.
 ## Compose the timeline and H3 prompts
 Map visual actions, camera moves, scene changes, and optional text to the music's
 global time. Build a causal visual progression instead of defaulting to one person
 singing throughout. Allow room to read a shape, gesture, or lyric before changing it.
 For longer work, choose a supported continuation or clip-assembly approach through
 the portable workflow. Keep visual shot boundaries distinct from generation
 windows. Local window prompts must account for overlap without replaying the full
 previous action. A new scene may require a new reference rather than inheritance
 of the old scene. Record entry/exit states for each planned segment.
 Compile the timeline into H3's base or Ref2VA fields, preserving dialogue, lyrics,
 and visible text verbatim. Include concrete instrumentation and rhythmic accents,
 but treat requested BPM and beat alignment as targets until checked in the output.
 ## Typography and finishing
 When requested, give each shot one main readable text event. Keep words away from
 eyes and critical lip motion. Match sung text to the active phrase, and distinguish
 spatial typography from subtitle bars. Reduce text complexity if the model cannot
 render it, or use a disclosed overlay consistent with the requested deliverable.
 For supplied audio, assemble clips to one global master track, maintaining phrase
 and lip continuity; avoid cuts inside a vowel. For native audio, inspect actual
 continuity across generation windows. Preserve useful SFX and avoid layered duplicate
 music. Retiming, grain, grading, interpolation, and upscaling are deliberate editing
 choices, not automatic finishing requirements.
 Verify transformation/story order, identities, scene changes, requested text,
 musical continuity, timing, and full media decode. Label raw and processed versions.
 Deliver the final file and current prompt/timeline files, with measured properties
 and remaining limitations rather than claims of perfect synchronization.
@@ -0,0 +1,4 @@
 interface:
  display_name: "Music Video Direction"
  short_description: "Plan music-driven scenes and optional lyric text"
  default_prompt: "Use $music-video-subtitle-generator to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,40 @@
 # Global music and local video timing
 Use this planning skeleton, omitting vocal/text fields when not requested:
 ```text
 Global: music/excerpt, duration, ratio, character/style/scene locks, cut policy.
 Segment S01 — global start/end; local generation start/end
 Incoming state:
 Music cue: measured beat/phrase timestamp, or clearly labeled planned accent
 Vocal line and speaker (if present):
 Visible typography (if requested):
 Visual action and camera:
 Outgoing state and transition:
 References with exact roles:
 ```
 Keep one global music clock. For measured tempo B, the nominal quarter-note spacing
 is 60/B seconds, but real tracks may have pickups, swing, tempo changes, or inaccurate
 automatic detections. Validate important cut points against the waveform/listening.
 An onset detector also finds SFX and melodic attacks; it does not prove drum beats.
 Choose a phrase-complete excerpt when possible. Track breaths, lyric pauses, and
 vowel continuity for a performance MV. For an instrumental morph, accent the
 physical preparation, transformation impact, and release rather than introducing
 unrequested cuts. The final shape or story payoff needs a readable ending.
 For continuation, maintain a table of absolute output frames and local window
 times. Use the verified backend's native alignment and overlap behavior. Opening
 overlap continues the inherited state; new actions belong after it. Do not sum
 overlap twice or describe every window as a fresh opening shot.
 For separately generated clips, use a previous tail frame only when the next shot
 continues the same scene and the backend supports that keyframe role. For an
 intentional cut, retain appropriate identity references and select the new scene.
 Preserve screen direction or a useful match element when it helps the transition.
 When text is requested, track exact string, language, entry/exit time, screen
 region, and motion. Typography style cards must not donate their depicted characters
 or settings. Preserve user text; do not silently shorten lyrics to fit a template.
@@ -0,0 +1,69 @@
 ---
 name: paper-collage-explainer-generator
 description: Translate narration, ideas, or knowledge points into editorial halftone paper-collage metaphors, still prompts, storyboards, or stop-motion clips. Use for photographic cutout collage and tactile assembly, distinct from paper-puppet dioramas or generic cartoons.
 metadata:
  compatibility: File-based workflow with sibling h3-prompt-writing; media creation uses available image/video tools and an editor when needed.
 ---
 # Paper Collage Explainer Generator
 Read the [portable workflow](../h3-prompt-writing/references/portable-workflow.md)
 and [collage design](references/collage-design.md) when constructing scenes.
 Honor prompt-only and asset-only requests as well as finished video requests.
 ## Meaning and media policy
 Extract each source line's meaning, emotion, action verb, visual metaphor, and
 three to six readable object groups. Preserve the user's topic and wording as
 context; do not put narration on screen merely because it is available.
 Default to tactile paper SFX, with no BGM, voiceover, or subtitles unless requested.
 An explainer does not inherently require speech. Existing user requests for those
 layers already establish the choice; do not ask again. A short 16:9 clip of roughly
 four seconds is a useful default for one assembly beat, subject to backend limits.
 ## Plan the image and motion together
 Create a concise plan of metaphor, palette, object groups, assembly order, duration,
 and sound cues. For a series, keep paper texture, halftone treatment, keylines,
 shadows, and rhythmic language consistent; vary the metaphor and color field only
 where the meaning benefits. A user's no-text or no-music requirement applies to
 every downstream asset, prompt, clip, and edit.
 Design each still as the completed final composition. Use black-and-white
 photographic halftone cutouts, selective colored cardstock, warm cream keylines,
 subtle fiber/torn edges, and soft physical layer shadows on a bold color field.
 Keep layered depth and negative space; avoid excessive age, dirt, wrinkles, or
 automatic brown/kraft backgrounds. Exact editable layers require a compositing
 workflow, not a claim that a generated raster video is a layered project.
 Generate final-composition stills when requested/needed and inspect them. Follow
 any requested approval gate; otherwise continue within the authorized workflow.
 ## Animate the assembly
 Start from a clean paper field matching the planned final color. Base pieces enter,
 then the main metaphor, then supporting objects. Each piece slides or pops in,
 bounces slightly, presses flat, pauses, and locks. End with a brief hold on the
 completed composition. Use stop-motion assembly rather than global fades, smooth
 digital drifting, fast spinning, or liquid morphs unless explicitly requested.
 Use the supplied final still as a last-frame anchor only when the backend supports
 it. Otherwise identify it honestly as composition/style guidance; do not describe
 a reference image as a guaranteed final-frame constraint. Compile the actual H3
 mode with the sibling guide and bind only real inputs.
 Map short paper slides, pops, taps, rustles, and snaps to motion. Preserve those
 SFX during assembly. When the user adds music or narration later, mix with the
 useful SFX unless they request full replacement.
 ## Review and deliver
 Check the metaphor without relying on text, object count/readability, matching
 opening color, visible piece-by-piece construction, final-frame resemblance,
 controlled paper texture, and no unwanted UI/letters/music/voiceover. If the
 assembly is weak, simplify the groups and make their arrival order concrete.
 For multiple clips, preserve the planned order and SFX. Deliver prompts, current
 stills, and actual clips/assembly as requested. Explain any missing generation
 capability or remaining drift; keep raw output separate from edited fixes.
@@ -0,0 +1,4 @@
 interface:
  display_name: "Paper Collage Explainers"
  short_description: "Animate editorial paper metaphors with tactile SFX"
  default_prompt: "Use $paper-collage-explainer-generator to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,33 @@
 # Editorial collage design
 For each source idea record meaning, emotion, one active verb, a concrete visual
 metaphor, three to six object groups, and a tactile sound cue. For example, a
 collaboration concept can become separate cutout hands fitting paper routes
 together; it need not become a screen full of the word "collaboration".
 Style signature: flat bold color field, black-and-white halftone photographic
 cutouts, selective colored cardstock accents, warm cream keylines, soft physical
 paper shadows, fine uncoated fiber, refined irregular torn edges, layered seams.
 Control texture so the video feels handmade without becoming dirty or distressed.
 Palette choices may support meaning: orange/red for urgency, mustard for tools or
 warning, green for reflection, purple for memory, teal for collaboration, rose for
 theatrical contrast. These are suggestions, not universal semantic rules. Use the
 user's palette and avoid an unrelated kraft-paper opening.
 Still specification: source meaning → metaphor → ratio → background/accent colors
 → object roles → foreground/midground/background → final composition → exclusions.
 Motion specification: matching empty color field → base paper structures → main
 subject → secondary groups → light bounce/press-flat/pause → completed composition.
 Explicitly describe material boundaries and which piece moves at each beat. A
 static camera is usually enough to reveal assembly; add movement only when useful.
 Sound specification: synchronize restrained slides, pops, taps, rustles, and snaps.
 Set `non_diegetic_music: N/A` for the default SFX-only H3 prompt. Do not use silence
 as a synonym for no background music. Dialogue and subtitles are optional layers.
 Review one established clip as a style/cadence reference for subsequent clips.
 Change the specific failure: fewer groups for clutter, more physical arrival
 steps for digital drifting, less aging for dirty paper, stronger final state for
 composition drift. Do not apply an unrelated aesthetic preset to fix one defect.
@@ -0,0 +1,68 @@
 ---
 name: papercraft-stop-motion-explainer
 description: Turn knowledge topics into layered papercraft stop-motion explainers, including visual metaphors, miniature sets, prompts, storyboards, motion and sound plans, or rendered video. Use for tactile paper dioramas and mechanisms, not ordinary vector cartoons or photographic collage.
 metadata:
  compatibility: Portable file-based workflow with sibling h3-prompt-writing; actual media generation uses tools available in the host environment.
 ---
 # Papercraft Stop-Motion Explainer
 Read the [portable workflow](../h3-prompt-writing/references/portable-workflow.md).
 For scene/prompt planning read [paper staging](references/paper-staging.md).
 Route a single image prompt, image series, short animation prompt, or storyboard
 request directly to that artifact; do not force a full film workflow.
 ## Knowledge and direction
 Identify the exact topic, source facts, audience, desired learning outcome, and
 output type. Preserve technical terms and causal meaning. A visual metaphor helps
 explain a mechanism; it must not turn into a false scientific claim.
 Reuse requested duration and ratio. If unspecified, a 30-second, 16:9 general-audience
 concept is a reasonable starting point. Offer distinct directions only when useful:
 pop-up-book journey, paper laboratory, layered cross-section, miniature nature
 theater, or mechanism board. Each should identify one learning outcome, a paper
 mechanism that conveys it, and the signature visual moment.
 ## Build the paper world
 Design characters only if they help the explanation. Specify paper construction,
 silhouette, joint/hinge design, replaceable facial parts, gestures, and repeatable
 identity cues. Keep the central knowledge object readable.
 Plan foreground occluders, midground mechanism, background scenery, and a distant
 paper plane when the shot benefits from depth. Record each layer's material,
 thickness, cut/fold edges, shadow, movement, and educational role. Use real paper
 mechanics such as pull-tabs, sliders, rotating discs, page folds, and pinned joints.
 Motion is stepped with small pauses and rebounds, not a smooth CG melt.
 Create an asset list by function: characters, scientific objects, information cards,
 environment, and moving mechanisms. For a complete production, prepare one to three
 preview briefs or images when useful and authorized. Respect any preview approval
 requested by the user; otherwise continue under the existing end-to-end scope.
 ## Prompts and timeline
 Write a compact storyboard with columns: time, knowledge beat, visual action,
 paper movement, camera/transition, sound cue. Each shot explains one knowledge
 step, with a readable pause for a necessary label. Keep ratio, material, light
 direction, identity, and domain vocabulary consistent across image-series prompts.
 For a short image-to-video prompt, begin from the actual image and animate a few
 paper mechanisms with restrained push-in or lateral parallax. Preserve thickness,
 cut edges, texture, and layer shadows. Compile final rendering prompts using the
 bundled H3 mode guide, with truthful references and local clip timing.
 ## Sound, generation, and review
 Map paper flips, cardboard slides, joint taps, soft pops, and rustles to actual
 motion. Match any requested music to the topic and cultural context rather than
 automatically using the same whimsical score. Keep speech intelligible. If narration
 is requested, preserve its approved wording, measure its duration, and adjust the
 timeline or script within the user's scope; do not silently speed up the voice.
 Use available generation/editing tools, then inspect both educational accuracy
 and paper construction: readable mechanism, separate layers/shadows, hinged or
 stepped motion, plausible camera movement, and a clear ending takeaway. Check
 narration tails, clicks, audio gaps, and music balance. Deliver requested artifacts
 and state missing rendering capabilities or unresolved scientific/visual issues.
@@ -0,0 +1,4 @@
 interface:
  display_name: "Papercraft Explainers"
  short_description: "Explain ideas with layered paper mechanisms"
  default_prompt: "Use $papercraft-stop-motion-explainer to prepare the requested H3 prompts or video with the available tools."
@@ -0,0 +1,48 @@
 # Paper staging and prompt building blocks
 ## Materials and depth
 Use layered matte cardboard, visible thickness, fibers, folds, seams, tabs, brads,
 cut edges, and physical shadows. Separate foreground, mechanism, background, and
 far background with spacing. Roughly 4–7 layers often suffice; remove layers that
 hide the explanation. Place reading-heavy labels on stable planes. Use miniature
 macro photography and moderate depth of field without blurring necessary facts.
 | Plane | Useful content | Motion | Purpose |
 | --- | --- | --- | --- |
 | Foreground | Paper leaves, frame, curtain, props | Small parallax or hinged reveal | Depth without concealing the mechanism |
 | Midground | Knowledge model, host, arrow/cards | Pull-tab, slider, joint, rotating disc | Main cause and effect |
 | Background | Diorama set or schematic layers | Slow paper rail shift | Context and hierarchy |
 | Far plane | Paper sky/board | Restrained change | Stable visual support |
 ## Prompt ingredients
 Image: topic and core object → miniature diorama → layered paper construction →
 specific material edges → physical light/shadows → clear depth → necessary labels.
 One frame should communicate one main idea, not the entire lesson at once.
 Image series: repeat the style/identity anchors, then state what changes and why
 that state explains the next knowledge step. Keep the same ratio and light direction.
 Short animation: preserve the supplied image, make a small paper mechanism move,
 include tiny pauses/rebounds, and select one restrained camera move. Small puppet
 gestures and background rails can provide life without overwhelming the model.
 ## Camera and transitions
 Use slow push-in, lateral parallax, static demonstration, macro detail, or a slight
 top-down cross-section view. A full orbit requires a set built for that view.
 Transitions may use a page flip, pop-up unfold, pull-tab, paper cloud, circular
 mask, cut-paper door, layer separation, confetti, or sticker reveal. Avoid liquid
 morphing, neon glitches, and glass shatter unless explicitly requested as contrast.
 ## Sound and exclusions
 Use a few motion-specific accents: paper flip, scissors, cardboard slide, joint
 tap, tape peel, or box opening. A score, when appropriate, can use light percussion,
 plucked instruments, or topic-specific instrumentation. Do not infer narration
 merely because the video teaches something.
 Keep constraints concise and relevant: no glossy plastic, smooth CG morphs, metal
 surfaces replacing paper, missing thickness/shadows, or frantic camera movement.
 Include them in supported prompt fields; do not invent a negative-prompt API field.
@@ -0,0 +1 @@
 ../../.agents/skills/3d-animation-short-generator
@@ -0,0 +1 @@
 ../../.agents/skills/brand-promo-video-generator
@@ -0,0 +1 @@
 ../../.agents/skills/co-op-game-intro-generator
@@ -0,0 +1 @@
 ../../.agents/skills/h3-prompt-writing
@@ -0,0 +1 @@
 ../../.agents/skills/handdrawn-live-video-generator
@@ -0,0 +1 @@
 ../../.agents/skills/minimalist-product-ad-generator
@@ -0,0 +1 @@
 ../../.agents/skills/music-video-subtitle-generator
@@ -0,0 +1 @@
 ../../.agents/skills/paper-collage-explainer-generator
@@ -0,0 +1 @@
 ../../.agents/skills/papercraft-stop-motion-explainer
@@ -60,6 +60,14 @@ self-check.
  `test-weekly.yml`), and copy-paste local plus CI-like `pytest` commands; see
  `references/test-routing.md` for level-to-command mapping
 ## MiniMax H3 Creative Skills
 The [portable H3 collection](../../.agents/skills/README.md) contains the prompt
 writing skill and eight creative workflows for product ads, 3D shorts, paper art,
 brand promos, music videos, co-op intros, and hand-drawn/live-action fusion.
 Same-named directories here link to the canonical `.agents/skills/` copies, so
 Claude Code and Codex use the same instructions and templates.
 ## Maintenance Guidelines
 - Keep skill names short and task-oriented.
		`@@ -0,0 +1 @@`
							`../../.agents/skills/3d-animation-short-generator`
		`@@ -0,0 +1 @@`
							`../../.agents/skills/brand-promo-video-generator`
		`@@ -0,0 +1 @@`
							`../../.agents/skills/co-op-game-intro-generator`
		`@@ -0,0 +1 @@`
							`../../.agents/skills/handdrawn-live-video-generator`
		`@@ -0,0 +1 @@`
							`../../.agents/skills/minimalist-product-ad-generator`
		`@@ -0,0 +1 @@`
							`../../.agents/skills/music-video-subtitle-generator`
		`@@ -0,0 +1 @@`
							`../../.agents/skills/paper-collage-explainer-generator`
		`@@ -0,0 +1 @@`
							`../../.agents/skills/papercraft-stop-motion-explainer`