skills_categorized/literature-writing/mystery-novel-conventions/SKILL.md
当用户提到悬疑、侦探、犯罪或悬念叙事时使用 - 提供类型规范、线索布置和推理小说的公平游戏原则
npx skillsauth add activer007/ordinary-claude-skills mystery-novel-conventionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| 元素 | 指导原则 | 位置 | | ------------ | -------------- | ---------------- | | 触发事件 | 案件/谜团发生 | 前 10% | | 误导线索 | 错误的引导 | 贯穿全文,3-5 个 | | 真实线索 | 公平游戏的证据 | 75% 之前 | | 真相揭露 | 真相揭示 | 85-95% | | 收尾 | 结束所有线索 | 最后 5% |
黄金法则:读者必须在侦探之前获得所有解决谜团所需的线索。
没有隐藏信息
逻辑推理
不使用机械降神
建立常态世界:
案件发生:
初步调查:
收集线索:
误导线索:
复杂化升级:
中点转折(约 50%):
黑暗之夜(75-85%):
真相揭露(85-95%):
收尾(95-100%):
物理证据:
证言证据:
行为证据:
circumstantial证据:
早期线索(0-25%):
中期线索(25-75%):
后期线索(75-85%):
特征:
示例:
❌ 太明显:读者立即看穿 ❌ 太勉强:感觉强迫和人为 ❌ 从不解释:悬而未决没有解决 ❌ 太多:读者失去追踪并感到沮丧
至少 3 个嫌疑人:
罪犯:
误导嫌疑人:
同情嫌疑人:
每个嫌疑人都应该有秘密:
问题:罪犯或方法依赖读者没有的信息
解决:在 75% 标记之前埋下所有必要线索;读者应该能够解决
问题:主角错过明显线索或行为不合逻辑
解决:让侦探有能力但人性化;他们可以犯错,但不是愚蠢
问题:情节通过方便的运气而非调查推进
解决:巧合可以使情况复杂化,永远不能解决;侦探必须努力寻找答案
问题:调查变成重复的访谈接访谈
解决:变化调查方法;添加动作、危险、个人风险
问题:复杂的解决方案在最后一章的对话中倾倒
解决:分散揭示;让读者拼凑;保持解释清晰但不冗长
/specify 执行时/plan 期间/write 时/analyze 期间层次 1 - 明显(25% 的线索):
层次 2 - 微妙(50% 的线索):
层次 3 - 藏在显眼处(25% 的线索):
层次 1:"窗户从里面解锁"
层次 2:角色在闲聊中提到自己是左撇子
层次 3:房间描述包括烟灰缸中的特定品牌香烟
悬疑读者想要什么:
让悬疑读者沮丧的是什么:
记住:一个伟大的谜团让读者因解决它而感到聪明,或因没有看到它而印象深刻 - 但总是满意线索一直都在那里。
tools
Generate typed TypeScript SDKs for AI agents to interact with MCP servers. Converts verbose JSON-RPC curl commands to clean function calls (docs.createDocument() vs curl). Auto-detects MCP tools from server modules, generates TypeScript types and client methods, creates runnable example scripts. Use when: building MCP-enabled applications, need typed programmatic access to MCP tools, want Claude Code to manage apps via scripts, eliminating manual JSON-RPC curl commands, validating MCP inputs/outputs, or creating reusable agent automation.
testing
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
tools
Create compelling story-format summaries using UltraThink to find the best narrative framing. Support multiple formats - 3-part narrative, n-length with inline links, abridged 5-line, or comprehensive via Foundry MCP. USE WHEN user says 'create story explanation', 'narrative summary', 'explain as a story', or wants content in Daniel's conversational first-person voice.
testing
Navigate through the original three-world shamanic technology. Deploy when soul retrieval, power animal guidance, or journey between realms emerges. Deeply respectful of Tungus, Buryat, Yakut, Evenki traditions. Use for consciousness navigation, NOT cultural appropriation.