CommunityWriting & Editinggithub.com

Vertical Short-Drama Storyboard

Decompose finalized, validated episode scripts into two-level storyboards (segments → shots) with spoiler briefs, minimal visual asset entries, continuity tracking, and automated storyboard validation. Use when asked to storyboard an episode, break a script into shots, cut segments, or sync storyboards after script edits.

What is Vertical Short-Drama Storyboard?

This skill implements a complete, professional storyboard workflow specifically for vertical short dramas (9:16 aspect ratio). It takes a finalized and validated episode script and decomposes it into a structured two-level storyboard: segments (each representing one video generation unit) and shots (individual cuts within a segment). The workflow enforces rigorous quality gates: it first verifies script finalization, mapping completeness, and automated validation passes; then builds minimal visual asset entries for characters, locations, and props that appear on screen; and finally writes the storyboard itself with strict rules for dialogue claiming (verbatim from script), action basis (original action line fragments in `依据`), vertical framing guidance, and single-instant shot descriptions. The skill also maintains cross-episode continuity tracking, runs automated script and storyboard checks, handles script revision synchronization, and produces a clear handoff summary for downstream prompt-writing. It is designed to integrate seamlessly with companion skills `fiction-short-drama` (for script writing/editing) and `fiction-visual-prompts` (for writing image/video prompts and asset locking), and it explicitly refuses to perform their functions, ensuring clear separation of concerns.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/interjc/create-fiction-skills/tree/HEAD/skills/fiction-storyboard

Installed? Explore more Writing & Editing skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

What does Vertical Short-Drama Storyboard do?

Decompose a finalized, validated episode script into a two-level storyboard (segments → shots) that is ready to shoot and audit, while maintaining minimal visual asset entries and cross-episode continuity tracking.

When to Use / Not Use

  • Use this skill: Decompose drama/{series}/episodes/ep{NNN}.md into storyboard shots; create minimal asset entries or variants for characters, locations, and props appearing in this episode; maintain cross-episode continuity status; synchronize existing storyboards after script revisions are finalized.
  • Writing or editing episode scripts (including dialogue changes, completing mapping lines, finalization): Delegate to fiction-short-drama. This skill will never modify script text or dialogue; it will return to upstream if the script is not finalized, mapping lines are missing, validation checks have blocking items, or actions are unshootable. If fiction-short-drama is not installed, list the unfinalized status, missing mapping lines, or specific errors with line numbers and ask the author to fix them manually before proceeding.
  • Completing full asset appearance and lock terms, writing reference image slots, writing image/video prompts, confirming before paid generation: Delegate to fiction-visual-prompts. This skill will never write 锁定词 (lock terms), write prompts or model parameters in the storyboard, or call any generation interface.
  • Determining the project stage: Delegate to fiction-workflow; if not installed, ask the author directly for the target series and episode number.

If the downstream fiction-visual-prompts is missing, deliver the checked storyboard, asset library, and continuity table, clearly noting prompt-check not run (this skill does not run it) and provide a downstream manual checklist: complete full asset appearances and 锁定词, write reference image slots and episode image/video prompts under drama/{series}/prompts/, and confirm by segment and shot number before the author decides whether to generate.

Before Starting

First read AGENTS.md (especially the "Series Scope" section), .fiction/config.json, and bible/sources.md (main writing entry registry, see SB §5) from the book root. Then read in the minimal required order for the task (SB §4.1):

  • Storyboarding: The script for the episode drama/{series}/episodes/ep{NNN}.md → storyboard-check.mjs --brief output → drama/{series}/visual/assets.md → drama/{series}/visual/continuity.md; optionally read the last segment of the previous episode's storyboard and the bible/characters.md entries for appearing characters; for original series (series.md has 来源:原创), also read drama/{series}/series.md's ## 悬念账 (mystery ledger).
  • Creating/modifying visual assets: drama/{series}/series.md → bible/characters.md (main characters and those appearing in this episode) → drama/{series}/visual/assets.md → locations and props that appear in the written script; optionally read bible/inventory.md, bible/foreshadows.md, bible/timeline.md, bible/world-rules.md if foreshadowing, objects, or period specificities are involved.

Before writing or modifying any machine-readable file, first open the corresponding format excerpt from the reference document table at the end of this document, and write exactly according to the original, not from memory.

The short-drama visual chain is resolved by upstream priority over downstream (SB §3): characters.md stable traits > visual/assets.md > storyboard > prompts; script > storyboard > prompts. If an upstream error is found, fix it upstream first, do not create alternative descriptions in the storyboard.

If the project skeleton is missing, prompt to use fiction-init first; if fiction-init is not installed, ask the author to manually supplement AGENTS.md (including ## 本书口径), .fiction/config.json, bible/sources.md, bible/characters.md, and the required files under drama/{series}/ according to SB §2, SB §5, and SB §8. If only .fiction/config.json is missing, scripts will run with contractual default values (SB §8), and the author should be informed.

Path conventions: paths starting with bible/, drama/{series}/ are relative to the book root; shorthand visual/..., storyboards/..., episodes/... in the text are relative to drama/{series}/. All scripts run from the book root; enclose paths with spaces in quotes.

Seven-Step Workflow

1. Pre-Work Check: Confirm Finalization and Mapping, Then Run Script Check and Brief

Before starting breakdown (including subsequent script revision synchronization), verify three entry gates one by one:

  1. Script finalized: Open drama/{series}/episodes/ep{NNN}.md (SB §9.3) and confirm metadata is - 状态:定稿 (set by author).
  2. Mapping lines complete: Open drama/{series}/adaptation-map.md (SB §9.2) and confirm the target episode has a corresponding line with character and foreshadowing columns filled for this episode (missing lines only report map-missing as a suggestion, but will cause the brief to miss the mapped characters and their secrets for this episode).
  3. Script validation all green: Run (see drama-check.mjs --help for usage):
node <path-to-this-skill-dir>/scripts/drama-check.mjs <series> --ep <N>

Must have exit code 0, and zero blocks at both series level and for the target episode (exit code 2 indicates argument, configuration, or reading errors, not a pass); also confirm that fiction-short-drama has reported exit code 0 for the latest lint --series on this drama. If any condition is not met, stop and return to fiction-short-drama; if the lint report is missing, ask it to run and report (if not installed, list the gaps and error line numbers and ask the author to fix manually). If there are unshootable, dialogue-run or other suggest items, continue if resolvable through breakdown; if truly unshootable, ask the author to modify the script first.

After the entry gates are passed, run the storyboard brief (see storyboard-check.mjs --help for usage):

node <path-to-this-skill-dir>/scripts/storyboard-check.mjs <series> --ep <N> --brief

Read through all five sections section by section: ## 来源 (Source), ## 本集不得画出的真相 (Truths that must not be depicted in this episode, derived from any line in adaptation-map.md or any asset's 揭示伏笔 that haven't been revealed earlier), ## 人物秘密 (Character secrets, from this episode's mapping 人物 column and series.md 主要人物 entries that have 作者真相 filled), ## 尚不可用的资产 (Assets not yet available), ## 连戏现状 (Continuity status). If series.md has 来源:原创, the brief does not scan original clues, so manually read drama/{series}/series.md's ## 悬念账 and incorporate it into the spoiler avoidance checklist.

2. Build Minimal Visual Assets and Record Continuity Net Changes

Update drama/{series}/visual/assets.md according to SB §9.4 and SB §6.1 (for first-time creation, refer to Visual Asset Template):

  • Minimal entry principle: Only create ### {asset_key} and one visible - 外观: line for characters, locations, and props that need to be on screen in this episode (for locations, optionally add 锚点; for props with a corresponding entry in bible/inventory.md, add - 物品:Ixxx; for confidential entries, add - 揭示伏笔: or - 揭示集:). Do not write 锁定词; leave complete appearance polishing and reference image slots for fiction-visual-prompts. For first-time creation, only write 画幅 if it differs from config visual.aspect_ratio, and confirm the series basic 画风 with the author.
  • Standard names and variants: Use the standard name from bible/characters.md under ## 人物; do not create entries for extras without character files; do not repeat the same name across groups; use name@variant for costume or state changes (a base entry must exist first in the same group). Do not mix the three layers; see Visual Asset Writing Guide for details.
  • Refresh the brief: If any 揭示伏笔 / 揭示集 field is added or modified in this step, immediately re-run node <path-to-this-skill-dir>/scripts/storyboard-check.mjs <series> --ep <N> --brief to synchronize newly included foreshadowing truths and restricted assets into this episode's verification checklist.

If this episode has state changes that will continue into subsequent episodes (costume changes, persistent injuries/dirt, prop transfer/destruction/exit, persistent location changes), according to SB §9.5, directly write the net changes for this episode into drama/{series}/visual/continuity.md (for first-time creation, refer to Cross-Episode Continuity Table Template), so that step 6's automated check can verify them in one pass. When encountering inconsistencies between the brief's continuity.md and bible/inventory.md, except for adaptation scopes already approved by the author and recorded in adaptation-map.md, list all other differences and ask the author to decide; never write back to the novel's bible/inventory.md; see Cross-Episode Continuity Guide for details.

3. Divide into Segments First, Then Cut into Shots

Open SB §9.6 and SB §6.1, write drama/{series}/storyboards/ep{NNN}.md following the Storyboard Template, initially with - 状态:初稿.

  1. Segment first (## SEG01|Scene 1): One segment = one video generation, never cross scenes. Usually divide into 9–15 second segments based on plot units (short transitions can be shorter than 9 seconds if shot individually); total duration must not exceed storyboard.segment.max_seconds (default 15 seconds, see SB §8). 地点 is required; 站位, 环境声, 配乐 are optional.
  2. Cut shots within segment (### SH001|3s): Aim for around 3 seconds per shot, within storyboard.shot.seconds (default 2–5 seconds); duration must not be 0. 景别 (6-item closed set) and 画面 are required; 运镜 (8-item closed set, default 固定), 转场 (4-item closed set, default 切), 人物, 道具, 依据, 声音, 备注 are optional.
  3. Verbatim claiming of dialogue and actions:
    • Dialogue: Copy each line of dialogue from the scene block in script order, exactly as written (including punctuation and applicable (OS) / (VO)), do not change words, do not delete words. If a single dialogue line cannot fit into one shot when converted to seconds using drama.chars_per_minute (default 250 code points/minute, not rounded), split it into valid dialogue rows for adjacent shots; after combination, they must match the original sentence character by character.
    • Actions and shot lines: Extract original text fragments from △ action lines and 【…】 shot lines directly into - 依据: (at least 4 code points per segment, separate multiple segments with ;), and ensure that 画面 truly performs the action.
  4. Shot language and vertical framing: The first shot of the entire episode must have a moving subject; alternate between close and wide shots, short and long durations; use shot-reverse-shot for dialogue and leave reaction shots, insert short close-ups for key actions; cut in the middle of action (match on action); within a segment, at most 1–2 non-fixed camera movements, default 固定; for 9:16 vertical screen, avoid empty wide shots, build depth with foreground/midground/background, use character actions to reveal the environment; write camera position, angle, and focal length into 画面. See Segment and Shot Grammar and Vertical Framing and Shot Writing for details.
  5. Maintain stable numbering: Insert new shots using new numbers or letter suffixes (e.g., SH003a); do not shift existing numbers, do not reuse deleted numbers.

4. Write 画面 Under the Single-Instant Principle

Organize each shot's 画面 as **

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

fiction-chapter

网文单章写作六步闭环:查前文和设定、摘资料、定章纲、写正文、机检审改、回写追踪表。作者说“写新章”“接着写”“出下一章”“重写这一章”或要求重排单章结构时就用。重排卷纲或设计连载节拍用 fiction-planner;审校及已有章节获授权的局部回修、润色和去 AI 味用 fiction-review。 Write, continue, rewrite, or restructure one web novel chapter, from continuity checks and outlining through drafting, validation, and story bible updates. Use when asked to write a new chapter, pick up where the draft left off, write the next installment, or rewrite a chapter. Use fiction-planner for volume planning and serial cadence, and fiction-review for editorial review or authorized local fixes, polishing, and removing AI-like prose in an existing chapter.

fiction-craft

小说与网文写作技法库及风格指南构建工具:提供场景构建、场景-反应节奏、欲扬先抑、对话潜台词、信息分层、双线结构、氛围营造、混搭题材写法及准备/行动/分赃/交易/规则册子等章型剧本,并指导新建或从样章反向提炼项目 bible/style-guide.md。当用户询问具体怎么写某类场景、解决对话像话剧/节奏发闷/信息说太满/氛围不够等问题、设计题材混搭口径、或制定本书文风指南时使用,即使没提“技法”二字。只提供技法与风格校准:完整写新章用 fiction-chapter,技法问答或示范用本 skill,具体已有稿件的回修用 fiction-review,卷纲与爽点规划用 fiction-planner,设定与伏笔维护用 fiction-continuity。Web-novel craft library and style-guide builder: covers scene craft, scene-sequel pacing, dialogue, layered information, dual-line structure, atmosphere, genre-blend voice, chapter playbooks, and building bible/style-guide.md. Use for technique questions, demos, or codifying a book's voice. Use fiction-chapter for drafting, fiction-review for fixes to an existing draft, plotting to fiction-planner, and bible tracking to fiction-continuity.

fiction-planner

网文创意孵化、开篇定位与卷级规划:收敛模糊点子为卖点与金手指边界、起草书名简介标签(publish/blurb.md)、设计黄金三章、编排全书大纲与明暗双线节奏、制定卷纲与章节规划表、排布爽点节拍/欲扬先抑/情绪波形/S-A-B-C钩子/日更与爆更分组及区域循环结构,并结合伏笔扫描排期。当作者构思新书、拟书名写简介、磨开篇、列全书大纲、开新卷、重排卷次或调节奏钩子时触发。只管单章以上规划:建书与冻结交给 fiction-init,单章 outline 与写正文交给 fiction-chapter,文案与正文审校交给 fiction-review,平台提交交给 fiction-publish,改短剧交给 fiction-short-drama。 Web-novel ideation, positioning, and volume-level planning: turn vague ideas into marketable hooks, draft publish/blurb.md, design golden first three chapters, whole-book and volume outlines, beat/emotion waves, S-A-B-C hook and daily groupings, region cycles, and foreshadow schedules. Use when brainstorming a book, drafting titles/blurbs, planning volumes, pacing, or scheduling payoffs; hand setup/freezing to fiction-init, chapter outlines/drafting to fiction-chapter, review to fiction-review, submission to fiction-publish, and adaptation to fiction-short-drama.

fiction-short-drama

竖屏短剧改编与原创剧本闭环:立项、分集大纲与章集映射、分批写分集剧本、前 3 秒钩子与付费卡点设计、机检与映射回写。涉及改编短剧、把小说改成竖屏短剧、写短剧剧本 / 分集剧本、分集大纲、章集映射、付费卡点、前 3 秒钩子、断章、原创短剧、续写下一集短剧、检查短剧格式与时长时使用。建项目用 fiction-init;小说策划用 fiction-planner;写小说用 fiction-chapter;改共享档案用 fiction-continuity;润色用 fiction-review;转分镜用 fiction-storyboard;路由用 fiction-workflow。 Vertical short-drama adaptation and original scripting workflow: series setup, episode outlines, chapter-to-episode mapping, batched episode scripts, first-3-second hooks, cliffhangers, paywall breaks, and script checks. Use when adapting a novel into a vertical short drama, writing or continuing short-drama episodes, planning episode outlines or maps, placing paywalls, or checking script format and duration. Use fiction-init for setup, fiction-planner for novel planning, fiction-chapter for novel chapters, fiction-continuity for shared bible edits, fiction-review for polish, fiction-storyboard for storyboards, and fiction-workflow for routing.

Related Skills