원클릭으로
manga-showrunner
Create the canonical series, character, and chapter package for an original manga project before production begins.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Create the canonical series, character, and chapter package for an original manga project before production begins.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Review character references, candidate kids coloring story assets, and colored references for story-image correspondence, recurring character consistency, approved-text-only surfaces, and printable readiness.
Create prompt packs, visual style guides, recurring character references, generated or edited line-art assets, paired colored reference assets, and image logs for printable kids coloring stories.
Assemble approved coloring story assets into print-ready black-and-white exports and separate colored reference exports, then validate the final files.
Design the child-facing concept, brief, source text index, and approved storyboard for printable coloring stories.
Review investigation-led article packages for understanding sufficiency, evidence support, thesis strength, structure, style fit, fidelity, platform fit, and publication readiness.
Produce a publication-ready article package from investigation-led understanding through outline, draft, and revision using the team's shared writing principles.
| name | manga-showrunner |
| description | Create the canonical series, character, and chapter package for an original manga project before production begins. |
Use this skill to create the upstream canon package for the manga video studio team.
series-bible.mdcharacter-bible.mdcharacter-registry.mdseries-state.mdchapter-registry.mdchapters/<chapter-id>/chapter-plan.mdUse:
chapters/<chapter-id>/.chapters/<chapter-id>/chapter-plan.md is a pre-storyboard scoping file, not the final production blueprint.First determine whether the request is:
If continuing an existing series:
If bootstrapping a new series:
At minimum, ensure these paths exist or are accounted for:
series-bible.mdcharacter-bible.mdcharacter-registry.mdseries-state.mdchapter-registry.mdshared-assets/character-sheets/shared-assets/location-references/ when relevantshared-assets/style-references/ when relevantchapters/<chapter-id>/series-bible.mdRecord:
If the user already supplied story canon, treat it as the source of truth and build around it instead of replacing it.
If the user already supplied strong style canon, treat that as the source of truth and lock it into the series package instead of silently defaulting to grayscale tension manga.
When voiced or video delivery is in scope, set the default render-unit contract to video-frame unless the user explicitly wants printable/readable manga pages or separate panel assets as the primary deliverable.
Also lock one series-level video canvas before image generation starts, such as 9:16 vertical, 1080x1920 or 16:9 horizontal, 1920x1080. Later chapter artifacts may restate that canvas, but they must not override it inside the same video series.
character-bible.md and character-registry.mdLock the recurring cast before downstream image generation starts.
character-bible.md owns the stable identity layer for each important character. For each major character, capture:
The character bible must be specific enough that later prompt-writing does not have to guess who the character is supposed to be. Do not treat the character bible as the authority for mutable series-state fields such as latest appearance, roster status, design-lock version, or current voice mapping.
character-registry.md is the authority for the living cast across the whole series. It should capture:
planned, active, inactive, hidden, retired, or deadDo not assume every important future character already exists in full detail at chapter 1. Add or upgrade entries when the story actually reaches them.
series-state.md and chapter-registry.mdseries-state.md should capture the latest approved cross-chapter state:
chapter-registry.md should capture:
chapters/<chapter-id>/chapter-plan.mdBreak the project into the smallest useful production unit.
For each chapter or production unit, capture:
video-frame for video delivery unless another deliverable is explicitly primaryPrefer a tightly escalating pilot over a vague high-volume roadmap. Keep this file lightweight. It should help the storyboard director board the chapter fast, not replace the storyboard.
storyboard_director.chapter-plan.md once storyboard.md exists. The storyboard must become the operative chapter blueprint.voice_video_producer ran, read chapter-carry-forward.md first.character-registry.md with new debuts, status changes, latest appearances, design-lock versions, current voice mappings when relevant, pronunciation-note refs when relevant, and reusable asset links.character-bible.md only when the stable identity, design anchors, psychology, or forbidden-drift rules changed, not for routine roster-state churn.series-state.md with approved canon deltas and reusable assets.chapter-registry.md with the chapter status, folder path, and final outputs.character-registry.md, do not let that omission ride into later chapters.