h3

name	H3 合作游戏开场动画生成器
description	面向想制作双人合作游戏主菜单或开场动画的用户。用户需提供两位玩家名称、游戏名称、目标视觉风格，并可上传角色参考图。Skill 会先锁定人物身份特征，基于固定菜单布局生成与色彩、按钮、图标和字体联动的确认首图；用户确认后，回填角色、界面文案和事件节奏，生成完整视频提示词并制作最终开场视频。最终输出一条包含双人角色、玩家信息卡和主菜单交互动效的游戏开场视频。适用于合作游戏概念展示、角色化菜单和社交内容，不适用于完整可玩游戏开发、复杂多页面 UI、精确品牌标识复刻或无角色的通用片头

Co-op Game Intro Generator

Use this Skill when the user wants a co-op game intro video and wants to confirm the visual direction with one image before generating the final video. The workflow collects style, player names, game title, and optional character refs, then creates a framework-preserving confirmation image before generating with the currently configured global video model. Minimax H3 is preferred, but the Agent cannot select or switch models by itself.

Required References

These two templates are mandatory runtime inputs, not optional background notes:

• Use references/h3-confirmation-image-template.md when building the confirmation-image prompt in STEP 3 and generating the first confirmation image in STEP 4. Fill the template fields in order and do not skip framework, palette, UI, character, typography, layout, or negative-constraint fields.
• Before STEP 6, read the current global video model. If it is Minimax H3, use references/h3-video-prompt-template.md for the final H3 prompt. If it is not H3, ask the user to continue with the current model or switch to H3 in video settings; after any switch, read the configuration again. Fill the prompt from the approved confirmation image, player/game data, final UI copy, event timing, motion directions, and negative constraints.

If either template is unavailable, stop and report that the Skill package is incomplete instead of improvising a different prompt structure.

STEP 1: Ask for visual style

Ask the user to choose a preset style or enter a custom style. This style has top priority and controls supplemental style language, palette language, background texture, character rendering, expression, outfit direction, UI colors, button/icon style, and typography texture.

STEP 2: Collect player and game info

Collect PLAYER 1 name, PLAYER 2 name, and game title. If the user provides character images, use PLAYER 1 and PLAYER 2 refs only for identity mapping: recognizable face silhouette, hairstyle, glasses, relative facial proportions, and distinctive traits. Do not inherit photographic realism, skin texture, real-world lighting, camera quality, or the original image style; redesign the face into the selected visual style while preserving identity anchors.

STEP 3: Build the GPT confirmation-image prompt

Load and follow references/h3-confirmation-image-template.md as the required prompt skeleton. Use a fixed framework + dynamic style fill + palette-linked prompt structure:

1. Overall Style: always preserve game main menu UI, high-quality game promo poster, deep UI-character integration, modern commercial game UI design, strong visual impact, clean composition, and avoid over-decoration. Add other style terms from the selected style.
2. Color Palette: always follow: xx as main color, xx as UI body color, xx as text color, xx as functional accent color, red as danger accent, palette within five colors, high-contrast color blocking, fresh modern look, and xx-style color language. All later UI/button/icon/type colors must match this palette.
3. Composition: preserve 16:9 landscape, full-frame background, x centered characters, UI around rather than blocking them, upper-left player card, right-side vertical menu, bottom caution tape, a few corner graffiti accents, Z reading path, enough negative space, clear hierarchy, and Continue as the visual focus.
4. Background: follow pure xx background, slight xx texture, large solid-color blank space, texture only as detail, avoid heavy dirt/dense scratches/too much ink splash/large paint splatter, a little black spray-paint edge detail, clean modern premium UI-first background. Derive xx and additions from the selected style.
5. Character Style: strictly expand according to the selected style. Use source text only as dimension guidance, not fixed style.
6. Character A: facial features from character image 1; expression, rendering, and outfit follow selected style; optional compatible outfit dimensions include khaki short jacket, black inner layer, black cargo pants, brown boots, adventurer outfit. Fixed action: cross-legged, hands on floor, slight backward lean, looking up.
7. Character B: facial features from character image 2; expression, rendering, and outfit follow selected style; optional compatible outfit dimensions include green thick jacket, burgundy padded lining, white inner shirt, black pants, thick boots. Fixed action: cross-legged, hands in front of legs, slight forward lean, looking at camera.
8. Lighting: preserve top main light, upper-left warm/cool fill, soft bottom ambient reflection, soft shadows, contact shadows, rim light, high-quality GI, and natural character-background integration. Choose warm/cool from style.
9. Game UI: preserve console game menu, unified button size, rounded rectangles, slight tilt, minimal spray/drip elements, modern clean sticker design, readability, and no over-decoration. Button body, outline, and glow colors must match the palette.
10. Layout Rules: preserve horizontal long buttons, unified width/height/radius, width adapted to text, single-line titles only, no wrapping, no two-line titles, centered text, consistent margins and spacing.
11. : adapt colors from palette and icons from selected style. Continue is the large visual-center highlighted button with hover/click state. Start New Game is above Continue. Settings remains visually consistent. Exit Game uses danger/exit cue with red accents allowed.

STEP 4: Generate the first confirmation image

Generate only one confirmation image from the filled references/h3-confirmation-image-template.md. Preserve the framework structure, while making the selected style visibly dominant.

STEP 5: Wait for approval

Do not generate video until the user approves the image. If the user changes style, names, game title, identity, or image direction, return to the image prompt step.

STEP 6: Refill the video prompt and generate with the current global model

After approval, read the current global video model. If it is Minimax H3, load references/h3-video-prompt-template.md and refill the final H3 prompt with confirmed style, character refs, player names, game title, UI text, event timing, motion directions, and negative constraints. If it is not H3, ask the user to continue with the current model or switch in video settings; never claim the Agent switched models. Generate only after the current global model is confirmed.

STEP 7: Repair common failures

If text is unreadable, reduce on-screen text. If identities swap, strengthen names, positions, and colors. If faces drift, reuse uploaded refs and explicitly preserve identity anchors, hairstyle, and outfit anchors while keeping the face rendered in the selected visual style. If the selected style is weak, rewrite Overall Style, Color Palette, Character Style, Background, Game UI, Buttons, Icons, and Typography instead of changing layout framework.