/hbg-life-simulation

name: hbg-life-simulation
description: Create Chinese HBG “模拟人生 / 人生副本” narrative videos with a consistent comic IP, a rapid multi-life opening, continuous natural-speed narration, synchronized short captions, dense static manga storyboards, audible fixed-level BGM, alternating zoom/pan motion in HyperFrames, and a consent-gated localhost-only account-backed Images API through CLIProxyAPI as the preferred image channel. Use for 模拟人生、人生副本、统一主角漫画、快闪职业开头、旁白配图、静态漫画分镜、zoom 推拉、左右平移、Edge TTS、字幕压制、本地反代自己的 Codex 账号、CLIProxyAPI，或把长篇中文人生故事组装成视频。

HBG Life Simulation

Build a repeatable Chinese narrative-video pipeline: preserve the story, lock character identity, create an HBG opening, align narration, generate sufficiently dense comic frames, add restrained camera motion, mix audible BGM, and deliver a verified MP4.

Required skill order

1. Read `/imagegen` before generating or editing raster art. 2. Read `/hyperframes`, then the required HyperFrames domain skills before authoring or rendering. 3. Read `/media-use` for narration, captions, BGM, or SFX. 4. Read `/code-video-visual-qa` before the final visual pass.

Required project artifacts

Keep these files in every project:

• `SCRIPT_SOURCE.md`: verbatim user copy.
• `PROJECT_SPEC.json`: story-specific title, chapters, corrections, narration settings, opening assets, flash lives, and audio paths; never hard-code these values in builders.
• `SCRIPT.md`: narration-ready copy; record meaningful corrections at the top.
• `CHARACTERS.md`: immutable identity, clothing, age, and relationship rules.
• `STORYBOARD_BASE.json`: semantic beats with narration-relative `cueTime`.
• `STORYBOARD.json`: final global timing and asset paths.
• `PROMPTS.md`: exact ImageGen prompts and call identifiers.
• `HBG_STYLE.json`: single source of truth for orientation, canvas, caption style/safe area, opening motion, approved opening path, and BGM baseline.
• `audio_meta.json`: real durations and opening/body timing.
• `assets/generated/anchors/`: approved identity/style anchors.
• `assets/generated/sheets/`: original generated sheets.
• `assets/generated/scenes/`: split final scene images.
• `qa/`: source snapshots, encoded frames, media probes, and mix previews.

Never silently rewrite plot, viewpoint, tone, ending, or character motivation.

Workflow

0. Select the image channel before project work

Read [references/local-account-api.md](references/local-account-api.md) and [references/image-generation.md](references/image-generation.md). Run this read-only readiness check before initializing a new HBG project:

scripts/setup_local_cliproxyapi.sh ready

Prefer the user's own localhost CLIProxyAPI account channel, but require explicit confirmation for each new project before consuming account capacity. Never treat invoking this Skill as consent to use the account, install software, start the proxy, start OAuth, log in, or repair an account session.

• If the result is `ready`, tell the user a local account API is available and ask whether to use it for this project. Select `local-account-api` only after the user agrees; do not manually open, print, or summarize its protected environment or OAuth files.
• If the result is `not-running`, ask before starting the configured local proxy.
• If the result is `not-configured` or `unhealthy`, explicitly ask whether to initialize or repair CLIProxyAPI with the user's own account. State that CLIProxyAPI is a third-party proxy, the user must complete browser/device login personally, the flow remains subject to account permissions, quotas, and provider terms, and the setup includes a models check plus one image smoke test that consumes account capacity.
• Do not start image generation, run `start`, `install`, `bootstrap`, `login`, or an OAuth-capable installer command until the user clearly agrees in the current conversation. Do not infer consent from the story request or Skill invocation.
• Never ask the user to paste an account password, Cookie, OAuth record, access token, or API key. Never inspect `auths/`, `client.env`, browser storage, cookies, or provider account data.
• After consent, let the user complete OAuth in the browser or device-code page. Run only non-secret readiness/models checks and the disclosed single-image test.
• If the user declines, the account lacks image entitlement, or the local channel cannot be made healthy without further account action, select `built-in-imagegen` and continue.

Use this consent prompt or a concise equivalent:

是否使用你自己的账号在本机初始化 CLIProxyAPI，作为本次人生副本的默认生图接口？

这会安装第三方 CLIProxyAPI，并打开浏览器或显示设备码，由你本人完成登录。Agent 不会读取账号、Cookie、OAuth 文件或密钥。初始化后会检查 models，并生成 1 张测试图验证图片权限；这会消耗你的账户额度，且仍受账户权限、配额和服务条款限制。

是否继续？

When the result is already `ready`, use a shorter prompt that still discloses account usage:

检测到你已配置好的本地 CLIProxyAPI。是否使用你自己的账号为本项目生成图片？这会消耗你的账户额度，并仍受账户权限、配额和服务条款限制。

Record only the selected channel, consent state, provider label, model, and concurrency in `PROJECT_SPEC.json`. Never record an endpoint, key, OAuth path, token, Cookie, or account identifier.

Initialize the project style

Before step 1, initialize and read the style system:

# Default: landscape 16:9, 1920×1080
node scripts/init_project_style.mjs PROJECT_DIR

# Only when the user explicitly asks for portrait / 9:16 / vertical video
node scripts/init_project_style.mjs PROJECT_DIR --orientation portrait

If the user does not specify orientation, always use landscape. Portrait is supported but never inferred from short-video subject matter, platform, or a previous project. Read [references/style-system.md](references/style-system.md). Do not author separate HTML and ASS style constants, and never copy raw landscape caption/crop coordinates into portrait or vice versa.

Create `PROJECT_SPEC.json` before running any builder. Read [references/project-spec.md](references/project-spec.md). Story-specific data belongs in this file or the semantic storyboard, n