Skip to content

LeoYeAI/agent-master-skills / skills/ai-drama-prompt-factory

ai-drama-prompt-factory

Verified

AI短剧提示词工厂 - 端到端将小说/故事创意转化为结构化提示词包(角色立绘+场景+道具+分镜图片+视频+音频)的完整流水线。一个入口启动全流程,内部自动按阶段推进:策划→设计→剧本→诊断→提示词组装→API JSON输出。支持小说改编和原创短剧两条路径。触发词:AI短剧、短剧制作、小说转短剧、短剧提示词、提示词工厂、短剧全流程、小说改编短剧、生成短剧、AI视频剧本、短剧项目、分镜提示词、视频提示词、prompt factory。

references/continuity-guide.md

View on GitHub
# 连贯性管理指南 (Continuity Guide)

## 跨集状态追踪

每集完成后输出 `continuity/ep{N}-state.json`:

```json
{
  "episode": 3,
  "character_states": {
    "角色名": {
      "variant": "当前外观变体",
      "location": "当前位置",
      "emotion": "当前情绪",
      "injuries": "伤势状态",
      "carrying": ["随身道具"]
    }
  },
  "relationship_changes": [
    { "chars": ["A", "B"], "change": "从敌对转为暂时合作" }
  ],
  "planted_threads": [
    { "thread": "伏笔描述", "planted_at": "ep02_sh15", "expected_payoff": "ep05" }
  ],
  "resolved_threads": [
    { "thread": "已回收的伏笔", "resolved_at": "ep03_sh08" }
  ],
  "props_status": {
    "道具名": "状态描述"
  },
  "next_hook": "下集开场钩子描述"
}
```

## 续写检查清单

开始新一集前必须验证:

1. **角色服装**:与上集末尾一致(除非有换装场景)
2. **角色位置**:与上集末尾一致(除非有转场说明)
3. **角色情绪**:延续上集情绪状态
4. **钩子回应**:上集钩子在前3个镜头内有回应
5. **道具状态**:道具位置和状态延续
6. **伏笔检查**:超过5集未回收的伏笔需安排回收

## 角色变体切换规则

角色外观变体切换必须有剧情触发:

```
陈易(觉醒前)→ 陈易(觉醒后)
触发事件:被雷劈后获得超能力
切换镜头:ep02_sh12(觉醒特写镜头)
从此集开始:所有后续镜头使用"觉醒后"变体
```

切换点必须在剧本和连贯性状态中明确标记。

## 多集情绪曲线

```
集1: ████░░░░ (压抑→微光)
集2: ██████░░ (挑战→初胜)
集3: ████░░░░ (挫折→低谷)
集4: ████████ (爆发→高潮)
集5: ██████░░ (余韵→新篇)
```

全剧情绪走向应有整体弧线设计,避免每集都在最高点或最低点。
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall