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/competitor-teardown.md

View on GitHub
# Competitor Teardown

Use this when the user provides a video URL, screenshots, transcript, or asks to learn from a high-performing same-lane video.

## Teardown Checklist

Record:

- URL/source:
- Video length:
- Topic:
- First frame:
- First 3 seconds text:
- First 10 seconds plot promise:
- First visible number:
- Main contradiction:
- Protagonist identity:
- Trust shortcut:
- Disaster preview:
- Subtitle style:
- Color/style:
- BGM and sound effects:
- Cut frequency:
- Transition types, duration, and semantic purpose:
- Opening montage flashes and later callbacks:
- Tension peaks, valleys, false wins, and temporary reliefs:
- Exact numbers, dates, countdowns, and visible/hidden scoreboards:
- Comment triggers:
- CTA:

## Opening Analysis

Classify the opening:

- Number hook
- Disaster preview
- Familiar-person trap
- False bargain
- Reverse-identity hook
- Moral warning
- Cliffhanger

Then explain:

- Why the viewer keeps watching.
- Which emotion is activated: greed, fear, regret, anger, recognition, sympathy, justice.
- What information is intentionally withheld.
- Which opening images preview later consequences.
- When the opening stabilizes into the main story.

## Optional Transition Analysis

Use this only when transitions materially contribute to retention or when the user specifically asks about editing.

For each important transition, record:

- outgoing scene and incoming scene;
- approximate duration;
- hard cut, dissolve, double exposure, match cut, wipe, glitch, or other effect;
- semantic reason: time, place, causality, contrast, irreversible turn, or emotional aftermath;
- whether the next shot stabilizes or continues unnecessary motion.

Reject a transition insight if it is only “this effect looks cool.” Extract the causal reason it works.

## Optional Tension Analysis

Use this only when the story is long or its rises and falls are difficult to explain in concise prose. Do not require every sample to have a false win or temporary relief.

Map the story as a pressure wave:

`desire -> reward -> hidden cost -> relief -> worse baseline -> deadline -> collapse`

Identify the viewer question opened at each beat. Note callbacks, exact balances, payment dates, public/private contrasts, and the moment an apparent win changes meaning.

## Adaptation Rules

- Imitate: structural beat, pacing, hook mechanism, subtitle density, emotional contrast.
- Do not copy: exact story, exact phrasing, unique character design, creator name/watermark, proprietary music.
- Transform into our lane by changing industry, relationship, cost, protagonist, and lesson.

## Output Template

```markdown
## 竞品拆解
- 视频:
- 账号/赛道:
- 可见数据:

### 开头3秒
- 第一帧:
- 第一嘴:
- 字幕:
- 情绪:
- 钩子类型:

### 留存结构
1. ...
2. ...
3. ...

### 转场语法(按需)
- 转场:
- 时长:
- 前后画面关系:
- 为什么有效:

### 剧情关键起伏(按需,不强制画曲线)
- 欲望:
- 第一次奖励:
- 隐形代价:
- 暂时缓解:
- 更高压力:
- 倒计时/截止日:
- 崩塌:
- 商业机制与防护动作:

### 可借鉴点
- ...

### 需要避开的点
- ...

### 改造成我们账号的方案
- 新主题:
- 新黄金3秒:
- 上集断点:
- 下集开场:
- 封面字:
```
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: 472kUpdated 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