zenstory-ai/oh-story-claudecode / skills/story-setup
story-setup
Flagged网文写作工具集基础设施部署与检查。为 Claude Code / OpenCode / Codex / Google Antigravity / ZCode / OpenClaw / Reasonix 提供内置适配;Web AI / 通用 Agent 可走 skills + AGENTS.md 文件模式。触发方式:/story-setup、$story-setup、「准备写书」「帮我搭一下环境」「配置写作项目」「检查写作环境」。
references/agent-references/genre-prose-cards/都市脑洞.md
View on GitHub---
genre: 都市脑洞
aliases: [都市脑洞, 都市系统, 听劝文, 规则奖励, 生活脑洞]
platform: 长篇通用
confidence: high
source: local_longform_sample_derived
---
# 都市脑洞正文提示卡
## 正文提示词
写都市脑洞时,先让读者看见一个具体的现实窘境,再让核心脑洞立刻改变这件事。系统、面板、听劝、绑定、吹牛成真、异常能力都不能悬空展示,必须落到手机消息、账单合同、家庭关系、学校公司、围观评价这些现实场面上。爽点优先写“别人按现实常识判断错了,主角用新规则当场翻盘”。
## 开场切入点
- 用欠钱、离婚、退队、被嘲、求职失败、亲戚压力、手机消息等低门槛困境切入。
- 金手指不要先讲说明书,先给一次能被现实场景验证的小结果。
- 若有系统面板,面板只给目标、奖励、限制三件事,立刻回到角色反应。
## 冲突发动机
现实身份被看轻 + 新规则介入 + 旁人误判。冲突要围绕“谁不信、谁阻拦、谁要付账、谁会被公开打脸”推进,别让主角一个人看面板自嗨。
## 爽点与情绪释放
小爽点是现实收益到账,钱、形象、技能、关系位置改变;中爽点是围观者态度反转;大爽点是旧秩序被主角的新规则改写。奖励到账后必须有外部反馈。
## 对话与声线
都市脑洞的对话要带生活口吻:吐槽、急眼、装镇定、嘴硬都可以。系统提示冷一点,人说话热一点,别让角色替系统解释设定。
## 章尾钩子
适合用新任务、新奖励到账、手机热搜、陌生来电、检测结果、下一位误判者登场收尾。钩子要指向下一章的现实麻烦,而不只是“系统又响了”。
## 场景颗粒
现实场面优先:手机通知、账单、合同、体检表、监控、门禁、直播间、公司群、亲戚饭桌。脑洞规则必须在现实场面上被验证。
## 节奏密度
每章至少有一次规则生效的小结果和一次外部反馈。面板信息越长,现实反应越要具体,否则会变成自嗨。
## 取舍原则
系统信息压短,现实反馈放大;设定用到哪写到哪。跨题材时,都市脑洞只承担“新规则改写现实”的主干,别抢走情感线或悬疑线的主节奏。
## 禁止漂移
不要写成纯系统说明书;不要连续贴面板;不要只罗列奖励;不要让主角没有主动选择。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |