novel-style-hotblood
Skill3 starsChanged 12 days agoMITView on GitHub
作品属于男频热血爽文(升级流、打脸、金手指、爽点驱动),或作者要求按热血爽文风格写作时使用:该风格下的续写、润色、开篇、大纲细纲、情节推演、评阅改稿等一切任务动笔前加载。定义爽点密度与升级链、期待感管理、打脸写法、金手指规则、战斗突破写法与节奏铁律。其他风格不加载。
In this repository17 other files it gives its agents.
- novel-ai-lexiconSkill
- novel-ai-structureSkill
- novel-analysisSkill
- novel-chapter-planSkill
- novel-continuitySkill
- novel-craftSkill
- novel-human-touchSkill
- novel-plottingSkill
- novel-profilesSkill
- novel-projectSkill
- novel-prose-standardsSkill
- novel-revisionSkill
- novel-style-lightnovelSkill
- novel-style-mysterySkill
- novel-style-romanceSkill
- novel-style-scifiSkill
- novel-style-xianxiaSkill
The file
Files
热血爽文风格
定位与适用范围
- 加载本 skill 即表示当前作品按男频热血爽文处理:升级流、打脸四拍、爽点升级链与期待感管理是本风格的骨架,人设与产出都向这个定位对齐。
- 风格覆盖一切产出:正文、大纲、细纲、书名简介、评阅意见都要对齐本风格,不允许正文一个风格、大纲另一个风格。
- 优先级:下列要求在本风格下优先级最高,与通用方法论冲突时以本文件为准;工程内存在作者维护的《文风卡.md》时,以文风卡为准(作者显式约定优先)。
- 切换:作者中途换风格或明确要求换写法时,停用本文件,改加载对应的 novel-style-* skill;长篇换风格要同步修订大纲与文风卡,防止前后割裂。
文风要求(本风格下优先级最高)
- 爽点密度与升级链:每章至少一个清晰爽点(打脸/突破/获得/扬名),爽点沿"憋屈—蓄力—爆发—余韵"四拍展开;主角能力与地位沿升级链爬升,每一环都要兑现上一环埋下的期待,不空许诺。
- 期待感管理:每章结尾必须留钩子(新危机/新目标/新悬念/即将打脸),断章断在情绪最高点前一步;下一章开头迅速接住,不注水。
- 打脸要打得响:反派立得住(够嚣张、够具体),铺垫足(让读者憋到位),打脸过程干脆利落有围观视角,事后有余韵(旁人反应、地位变化)。禁止主角自证,让事实与旁人反应替他说话。
- 金手指有代价有成长:金手指的使用要有规则与限制,随剧情解锁新用法;禁止一键无敌解决一切冲突。
- 战斗与突破写法:战斗写策略与应对,不写招式名词堆砌;突破写身体感受与天地异象的具体画面,篇幅克制不拖沓。
- 节奏铁律:开篇三行内进入冲突或事件;每 500 字左右要有一个信息增量或情绪增量;连续两段没有推进就删一段。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

