将中文小说、短剧或漫剧想法、梗概、改编材料或已有系列笔记发展成可追溯的改编方案、戏剧方向、创作简报、导演阐述、故事引擎与分集地图,并按题材与制作形态(画风)选择写法。用户提出“导入小说做短剧”“开发短剧/漫剧”“做故事设定/系列大纲/分集规划”“写导演阐述”“这个题材怎么写”“定画风/制作形态”“把这个点子变成短剧”或需要梳理人物冲突与集间交接时使用;已有剧本可直接进入写作、资产或审查流程,不强制补开发文件。
npx skills add https://github.com/worldwonderer/drama-skills --skill short-drama-develop
把创作者的意图变成能持续制造选择、代价与状态变化的故事系统。保留创作者的题材、结局和尺度选择;不要把流行套路当成剧情答案。
从本技能目录读取 suite-ref.json,按其中相对 core_manifest 定位唯一同级主技能与
套件清单;确认声明的 core、contract、recipe 和清单 hash 一致后再读写项目。
随后执行 阶段契约 的运行时预检:先恢复事务、读取状态,再进入本阶段。
该文件同时给出本阶段的所有权边界、需要从制作形态取得哪些输入,以及本阶段规则表;本技能不读取其他技能的文件。
来源片段与待确认项。长材料先做语义分段、功能账本和候选分集,不用正则人名/名词命中
直接发布剧集或资产;不要偷换原意。
$short-drama-write;拆资产或后续制作可从相应技能直接进入。信息足够时直接工作。只有会改变主角、冲突引擎、结局承诺或改编边界的缺口才需要提问。
读取创作者输入和已接受文件,区分:
新项目复制 creative-brief.md。若改动已接受事实,先展示语义差异与下游影响,不直接覆盖。
方向未定时,提出少量机制不同的候选:改变主角策略、对抗来源、代价或持续冲突方式,而不只是换标题、职业和措辞。方向明确时直接深化,不为凑选项制造伪差异。
每个候选都说明:戏剧承诺、主角追求、对抗机制、反复回报、可升级的状态、长线终止条件、主要制作负担。让创作者选择或组合,并记录取舍理由;未选方案不进入既定事实。
需要完整方法时读取 story-craft.md。题材已经确定时,可从
genre-cards.md 按索引取一张题材卡,用来校准该题材更常用的
压力来源、场面颗粒与制作负担;它是可被创作者一句话覆盖的参考,不替代方向选择,也不进入交付物。
若设定里主角带着一段已经发生过的经历,或获得了一套外部授权的能力,那是叠加在题材之上的
前提装置,另读 premise-devices.md——装置取消阻力,
必须先给它边界与代价。装置不替代题材卡,也不为它单独建题材。
复制 story-engine.md,写清:
连续剧、长篇改编或人物纵向变化较重时,再读取
serial-character-and-memory.md:先建立只供
作者决策的前史储备,选择旧策略开始付出代价的叙事切入窗口,再记录人物被捍卫的
信念、压力测试、信息权限和跨集记忆。不要把前史储备直接倒进首集对白。
读取 episode-design.md,再复制 episode-map.jsonl。每一集记录进入状态、当集追求、阻力、因果升级、方向性转折、已兑现回报、出去的压力以及下一集必须继承的事实。
先保证每集产生局部戏剧结果、相邻集能精确交接,再讨论外部压力/情感负荷的双轨
节奏。集数、钩子类型、是否反转和高潮位置由创作者与项目决定。
在提交预览前检查:
这些是所有者自检,不是终审。展示创作者可读的新增/修改摘要,请创作者接受后再作为下游来源;需要质量结论时交给独立的 $short-drama-review。本技能不得批准自己的产物。
若项目需要导演阐述,本技能只产出 项目开发/director-brief.md 候选,并标明它准备
写入的 visual_direction / production_profile 语义差异。创作者接受后,由
$short-drama 路由把选择提升到 creator authority;开发技能不直接改写该权威配置。
structural_invariant:本地可证明的引用、ID、显式状态矛盾;可由校验器阻断。reviewed_invariant:升级是否真实、承诺是否兑现等语义义务;只能由独立审查者引用证据判断。craft_default:通常有帮助的做法;创作者说明理由后可覆盖。taste_option:钩子、弧线、视角、结局气质等选择;不得单独阻断。不要用固定的情节点、转折时刻、篇幅比例或数量配方替代因果判断。
本技能只拥有:
项目开发/creative-brief.md项目开发/story-engine.md项目开发/director-brief.md(项目需要时;仅为 creator authority 候选)项目开发/adaptation-map.jsonl(长材料改编时;只保留输入 locator/span/hash、去引用的功能摘要、候选去向与未决项,不复制原文;例见
adaptation-map.example.jsonl)
项目开发/series-arc.json(项目需要时)项目开发/episode-map.jsonl它不写场景动作与台词,不拆资产,不写图片/视频提示词,不生成媒体,也不签发终审结论。剧本语义由 $short-drama-write 接管。
serial-character-and-memory.md
adaptation-craft.md
creative-reference-intake.md
reveal-reversal-payoff.md
genre-and-hook-playbook.md
genre-cards.md(索引与召回规范;一次只读一张卡)
premise-devices.md(装置层,叠加在题材卡之上)
director-brief-craft.md
Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Translate visa application documents (images) to English and create a bilingual PDF with original and translation
Write, review, and edit documentation files with consistent structure, tone, and technical accuracy. Use when creating docs, reviewing markdown files, writing READMEs, updating `/docs` directories, or when user says "write documentation", "review this doc", "improve this README", "create a guide", or "edit markdown". Do NOT use for code comments, inline JSDoc, or API reference generation.
Real-time Constitution compliance checker for devflow documents. Blocks partial implementations and hardcoded secrets during file editing.
Write self-documenting code with minimal, evergreen comments that explain complex logic without describing recent changes or temporary fixes. Use this skill when writing code comments, documentation strings, explaining complex algorithms, clarifying business logic, or deciding whether code needs comments. Apply when working with any source code files where comments or documentation might be added, ensuring comments remain relevant, helpful, and focused on explaining why rather than what the code does, while preferring clear code structure and naming over excessive commenting.
Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.
Draft a structured investment committee memo for PE deal approval. Synthesizes due diligence findings, financial analysis, and deal terms into a professional IC-ready document. Use when preparing for investment committee, writing up a deal, or creating a formal recommendation. Triggers on "write IC memo", "investment committee memo", "deal write-up", "prepare IC materials", or "recommendation memo".
Take worldwonderer/short-drama-develop from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.