Short Drama and AI Reels Production

Create an original, high-retention short drama and move it from research to production without losing narrative or visual continuity. Support any positive episode count requested by the user; never impose a fixed total or an artificial maximum.

Start Here

Identify the user's current job and enter at that stage. Do not make them study the whole workflow first.

For copy-ready prompts, a worked example, and common questions, read references/quickstart-examples.md. For parameter choices or failures, read references/configuration-troubleshooting.md.

Preserve User Intent

Honor the requested genre, exclusions, live-action versus animation, orientation, language, duration, model, platform, and episode count. If the user gives no count, choose a story-appropriate count or present a concise range based on the episode engine; do not stretch an idea merely to fill a preset number.

Do not force reincarnation, domineering-CEO romance, identity concealment, horror, or revenge formulas merely because they are common. Novelty should come from a simple explainable premise, a fresh social or emotional contradiction, and a repeatable episode engine.

End-to-End Workflow

1. Define the research scope and metric meanings. Do not claim to have found "all" high-play dramas when platforms lack a unified public database.
2. Extract transferable techniques instead of copying plots, dialogue, signature scenes, names, or relationship structures.
3. Score several distinct premises for instant comprehension, emotional stakes, episode engine, reversal capacity, differentiation, and production feasibility.
4. Select one premise and lock the series bible: logline, theme, protagonist, antagonistic force, relationships, reveal ladder, fixed assets, and ending.
5. Scale the season architecture proportionally to the requested total. Every episode must change knowledge, power, relationship, possession, safety, reputation, or deadline.
6. Draft production-ready episodes with stable character, scene, wardrobe, and prop identifiers. Each episode needs an opening disruption, objective, escalation, meaningful reversal/payoff, emotional beat, and final hook.
7. Run scripts/audit_production.py. Fix errors; review warnings rather than blindly suppressing them.
8. Create the Word production稿 and run scripts/package_episodes.py for per-episode text files and ZIP packaging.
9. When asked to operate a website, verify the current model, style, orientation, episode count, prompt mode, duration, attached script, and credit implications before submission.

Quality Bar

• The premise is understandable in one sentence and demonstrated visually near the beginning.
• The protagonist makes consequential choices; coincidence may trigger the story but must not solve it.
• Reversals change meaning, allegiance, cost, or power. Withholding an obvious fact is not a reversal.
• Emotional depth comes from incompatible values and accumulated consequences, not long speeches.
• Fast pacing means high information density and irreversible decisions, not constant shouting.
• Reusable locations and fixed wardrobe improve generated-video consistency without making episodes visually static.
• The prior episode's final hook is acknowledged promptly in the next episode.
• Never promise virality. Give an evidence-based potential assessment and identify audience and execution risks.

Deliverables

For a complete project, normally produce:

1. Research and topic-selection report with dated sources and metric caveats.
2. Full production script in .docx with navigation-friendly headings.
3. Import ZIP containing global rules, asset libraries, prompt templates, a manifest, and one UTF-8 text file per episode.
4. Audit report showing episode continuity, scene structure, title uniqueness, hook markers, and packaging integrity.

Validate numbering, title order, scene presence, ZIP CRC, and Word heading structure. Render Word pages when the document toolchain is available; disclose clearly when visual rendering cannot be performed.

Failure Handling

Return actionable recovery steps, not only an error message. For every blocker, state:

• What succeeded
• The exact failing stage
• Likely cause supported by evidence
• What the user can change
• What the skill will retry
• The stopping condition that prevents duplicate projects or credit consumption

Use the detailed recovery table in references/configuration-troubleshooting.md. Do not repeat the same submission after the same server response.

External Actions

Uploading files, creating projects, or consuming generation credits are separate external actions. Preserve narrow authorization already given, but confirm immediately before a new credit-consuming generation when authorization is absent or ambiguous. A request to write a script does not authorize uploading or spending credits.