references/short-drama

Orchestrates AI short-drama production through six verifiable control contracts and QC gates.

38|4|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/6174/recut --skill references-short-drama-6174
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: references/short-drama
Source: https://github.com/6174/recut/tree/main/service/skills/recut-director/references/short-drama
Command: npx skills add https://github.com/6174/recut --skill references-short-drama-6174

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated short dramas, comic dramas, and narrative short videos often suffer from drifting character appearances, inconsistent spaces, unmotivated lighting, and unverifiable story beats. This Skill turns a story intent into a traceable, inspectable production chain of control contracts so every generation step can be checked, handed off, and rolled back instead of relying on repeated re-generation. ## Core Features & Use Cases - Six Control Contracts: Defines narrative beat contracts, asset registries (Cxx/Sxx/Pxx with versioned approval), blocking maps, lighting plans, action ledgers, and sketch-to-shot briefs, each with JSON templates and QC criteria. - Fixed Production Pipeline: Enforces a linear gated sequence from script reading, asset approval, blocking, genre parameters, and specialized contracts through ten-part prompt assembly to an eight-item pre-generation QC gate. - Use Case: When producing an AI short-drama episode, use this Skill to decide what must be approved before generation: verify the beat contract is visually observable, confirm all character/scene/prop assets are human-reviewed, and route any QC failure back to the responsible stage rather than regenerating blindly. ## Quick Start Ask the AI to orchestrate the production plan for your short-drama scene, building the beat contract, asset registry, blocking map, and pre-generation QC checklist before any video is generated.

Frequently Asked Questions about references/short-drama

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep AI-generated characters consistent across short drama episodes?▼

Use a versioned asset registry where every character, scene, and prop (Cxx/Sxx/Pxx) is human-approved before storyboarding. Versions evolve with suffixes like C01b and never overwrite approved versions, so later shots reference locked features instead of re-rolling video generation.

What is a blocking map for AI video generation?▼

A blocking map fixes screen orientation, left/mid/right and foreground/background anchors, actor positions and facing, prop start and end positions, camera placement, and the 180-degree axis on one plan. Movement is staged as numbered T0 to T2 phases so spatial relationships stay verifiable.

How many action beats can one AI video shot contain?▼

Each shot should carry only one to two readable causal beats structured as wind-up, movement, contact or miss, reaction, and end frame. Action density is judged by causal steps times duration times actor count times camera motion; over-budget sequences must be split or implied offscreen.

Can I use a sketch directly as the final AI video frame?▼

No. A sketch only locks composition and relationships such as horizon, camera angle, subject scale, eyeline, and key light direction. Character identity, wardrobe, and textures must be resolved from approved assets and style parameters, preventing sketch faces from overriding approved character designs.

What happens when a generated shot fails the QC gate?▼

Failures are routed back to the owning stage: story or beat issues return to the storyboard director, asset drift to the art stage, spatial or axis problems to blocking, field compilation to prompt assembly, and picture mismatches to QC. Simply regenerating the same prompt is explicitly forbidden.