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 |