Skip to content

slad-dev/AI-ShortVideo-Story-Engine / skills/douyin-script

douyin-script

Verified

Create and analyze story-first Douyin/TikTok-style short-video scripts for an 人生副本 account: cinematic character arcs, reversals, emotional payoffs, immersive second-person AI cartoon storyboards, golden 3-second hooks, 5–8-second image cadence, cautionary life stories, captions, subtitles, editing notes, and publishing prompts. Use when drafting or improving scripts about ordinary people, entrepreneurship traps, familiar-person risks, debt, guarantees, franchise scams, relationship costs, human-nature reversals, or other cautionary life-story videos.

references/story-engine.md

View on GitHub
# Story Engine Reference

Use this reference before drafting a cinematic, high-drama, or character-led 人生副本 episode. Its job is to make a viewer experience a chain of choices and emotions, not to decorate a conclusion with “story-like” lines.

## 1. Character bible: use pressure, not labels

For each key character, write only what will appear in a scene:

| Field | Question to answer | On-screen proof |
|---|---|---|
| Public face | Who do others think they are? | Clothing, workplace, who stands up, who waits |
| Private wound | What humiliation, fear, debt, loss, or longing do they hide? | A deleted message, worn object, avoided glance |
| Concrete desire | What must they get now? | A deadline, payment, invitation, empty seat |
| Blind spot/secret | What can be used against them? | A missing page, unanswered call, concealed receipt |
| Self-justification | What sentence lets them cross the next line? | Dialogue they repeat to themselves |
| Cost | What could they lose that cannot be replaced by a lecture? | Trust, dignity, health, a relationship, time |

Give the counterforce leverage. It may be a person, a family system, a contract, a status gap, an algorithm, a deadline, or a public secret. “Bad person” is not leverage; access to evidence, money, approval, information, or the protagonist’s need is leverage.

## 2. Build the engine

Write one sentence in this form:

`[public identity] wants [concrete desire], so they choose [reasonable shortcut]; the thing that seems to save them is actually [hidden transfer of cost], until [core reversal] forces [active choice and price].`

Then make these commitments:

- **One emotional promise.** Do not mix revenge, tragedy, healing, and a business lecture unless one clearly dominates.
- **One core reversal.** It must reverse the meaning of earlier action, not merely announce new information.
- **One recurring anchor.** Use an object, line, location, or ritual three times: desire, cost, then truth/safeguard.
- **Three planted details.** Plant them in active scenes; pay each off later. A planted detail must look ordinary the first time and inevitable after the reveal.
- **An active ending.** The protagonist accepts, exposes, walks away, pays, refuses, or gives something up. Avoid rescue by coincidence.

## 3. Pressure ladder and payoff choices

Use this causal chain, adapting the number of scenes to runtime:

`want → reasonable move → small win → warning the protagonist explains away → false safety → irreversible choice → reveal/reversal → chosen cost → new meaning`

The small win must be real. The warning must be visible before it is explained. The false-safety scene should be the point at which the viewer hopes the danger has passed. Put the reversal after the viewer has invested in the protagonist’s justification.

Choose a reversal that belongs to the premise:

| Reversal | What changes |
|---|---|
| Price reversal | The reward was payment for a larger sacrifice. |
| Identity reversal | The weak-looking person, relationship, or role actually controls the key resource. |
| Loyalty reversal | The “protector” needs the protagonist trapped; the ignored person planted the only warning. |
| Self-deception reversal | The antagonist did not force the final step; the protagonist’s own justification did. |
| Moral reversal | The apparent win is not revenge or success until the protagonist gives up the thing that made them vulnerable. |

Do not use a reversal just because it is shocking. It needs a prior clue, a causal mechanism, and a changed decision.

## 4. Convert explanation into cinema

Never write a character trait or mechanism first if a camera can show it.

| Flat explanation | Scene conversion |
|---|---|
| “He is powerful.” | At dinner, the principal rises to toast him; a waiter clears a chair before he asks; the protagonist’s phone stops ringing when he enters. |
| “She is trapped by debt.” | She counts coins at a pharmacy, then hides a collection call when her child enters. |
| “The deal was unfair.” | A page in the contract is folded under a coffee ring; later, the same crease is beside a payment reminder. |
| “He regretted it.” | He rehearses an apology in the car, then sees the returned key on the dashboard and cannot start the engine. |

Write scene beats as: `place/time → visible action → social reaction → self-justification → immediate reward/cost → next question`. One shot should usually carry one action, one evidence object, and one unresolved question.

## 5. Anti-exposition pass

Before delivering the script, remove or rewrite:

- opening biography, generic moralizing, and “today I will tell you” introductions;
- adjectives that replace behavior: “cruel”, “powerful”, “pitiful”, “smart”, “unfair”;
- narration that reveals a secret before the viewer can notice its clue;
- coincidences that solve the ending;
- repeated summaries between scenes;
- an ending that only says “so the lesson is…” without a final action/image.

Ask four questions: Does every false win change meaning later? Does each payoff have a prior visual seed? Does the protagonist make the final meaningful choice? Can the final image carry the emotion if narration is muted? If not, revise the engine before creating image prompts.

## 6. Safe use of real-world inspiration

When inspiration comes from a public event, extract the emotional mechanism—status gap, secrecy, a public image versus private cost, a late truth—not the unverified facts. Change names and identifiable private details, label the piece as fictionalized where appropriate, and do not claim allegations, motives, or legal conclusions as fact. For legal/financial themes, show lawful prevention and consequences; do not provide operational loopholes or evasion steps.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall