[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMHHRSS2SCZN6HWSANBJ35":3,"skill-same:01M7DMHHRSS2SCZN6HWSANBJ35":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7DMHHRSS2SCZN6HWSANBJ35","unslop",null,"从任意写作中剔除 AI 痕迹。","fenfenxu\u002Fpstack-zh","fenfenxu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2194243?v=4","01M7DMDSWBASX3NXC18FPHDJ8G","01M7DMDSWV8ASCZ4PH6YFXHPSJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unslop\ndescription: 从任意写作中剔除 AI 痕迹。\ndisable-model-invocation: true\n---\n\n# Unslop\n\n编辑文本，去除 AI 模式。扫描下列模式，然后重写。保留含义，匹配预期语气。\n\n## 应检测并修复的模式\n\n规则编号是其他 skill 引用的稳定 id。删除的规则留空号。\n\n### 内容\n\n3. **肤浅的 -ing 短语。** 「highlighting...」「ensuring...」「reflecting...」「showcasing...」「fostering...」。删除或展开并给出真实来源。\n5. **模糊归因。** 「Experts believe」「Industry reports suggest」「Some critics argue」。点名来源或删除。\n\n### 语言\n\n7. **AI 词汇。** Additionally、crucial、delve、enduring、enhance、fostering、garner、interplay、intricate、landscape（抽象）、pivotal、showcase、tapestry（抽象）、testament、underscore、vibrant。换成平实词。\n8. **「是」的花式说法。** 「serves as」「stands as」「boasts」「features」。说「是」或「有」。\n9. **「Not just X, but Y.」** 直接陈述要点。\n10. **规则三。** 不要硬凑成三组。用自然数量。\n11. **同义轮换。** 一段里 protagonist、main character、central figure、hero 轮换。选一个，重复它。\n12. **假范围。** 「from X to Y」而 X、Y 不在有意义尺度上。直接列主题。\n\n### 风格\n\n13. **滥用 em dash。** 完全避免 em dash。只用句号或逗号（不用括号、en dash、连字符冒充破折号）。需要分隔就结束句子或用逗号。\n14. **滥用冒号。** 冒号在列表或示例前可以，不作句中连接词。「If you're coming from traditional automation: instead of...」里冒号无增益。重写让要点独立，不要比较 framing。\n15. **滥用粗体。** 不要每个专有名词或缩写都 bold。\n16. **行内标题列表。** 特征是 bold 标签加冒号复述同一行：「**Performance:** Performance improved...」。改成散文。bold 引导以句号结尾、命名条目且后跟真正新细节的（「**Schema in TypeScript.** Tables live in one file.」）可以，不是 tell。\n17. **标题 Title Case。** 用句首大写（sentence case）。\n18. **装饰 emoji。** 从标题与 bullet 删除。\n19. **弯引号。** 用直引号。\n\n### 沟通 artifact\n\n20. **聊天机器人套话。** 「I hope this helps!」「Let me know if...」「Of course!」「Certainly!」「Found the smoking gun!」删除。\n22. **谄媚语气。** 「Great question! You're absolutely right!」直接回应。\n\n###  filler\n\n23. ** filler 短语。** 「In order to」→「To」。「Due to the fact that」→「Because」。删掉「It is important to note that」。\n24. **过度 hedge。** 「could potentially possibly be argued that it might」→「may」。\n25. **泛化结论。** 「The future looks bright.」陈述具体计划或事实。\n\n###  jargon\n\n26. **抽象隐喻名词。** Substrate（base）、wedge、wedge in（add）、vector（way、method）、locus、vantage、nexus、primitive 作名词、harness 作隐喻、surface（如「API surface」）、bedrock、scaffolding 作隐喻、modality、paradigm、gold-plating（more than the job needs）、ratchet 作隐喻（机制真名，或 a limit that only tightens）、evacuate 指搬代码（move out）、endgame（the last phase）、north star、flywheel。读起来像技术词，通常有更平实的具体词。选具体词。\n\n### 平实表达\n\n27. **说做什么，不说感觉。** 「the database stays close at hand」「SQL you can read」「types that follow your schema」命名的是感觉。修复应命名机制或数字：「`.toSQL()` returns the exact string sent to the database」「a column rename fails the build」。问这句告诉读者做什么或知道什么，然后写那个。若无法 restate 为具体指令、事实或数字，删掉。再检查：若句原封不动可出现在别的项目文档，它对本项目什么也没说。删掉。\n28. **缩短或拆分密句。** 读者须回溯才能 parse 就拆两句或删从句。一句一思。\n29. **主动语态。** 优先。抓「is\u002Fare\u002Fwas\u002Fwere + past participle」并点名 actor：「queries are validated」→「the compiler validates queries」。仅 actor 未知或无关时被动可接受。\n30. **删副词或用更强动词。** 「runs quickly」→「is fast」或数字，「significantly improves」→实测 delta。副词撑弱动词说明动词选错了。\n31. **优先平实词。** 「utilize」和「leverage」→「use」，「facilitate」→「help」，「numerous」→「many」，「in the event that」→「if」。花哨同义词很少更清晰。\n32. **矫饰 prose。** 有字面说法处用隐喻或 flourish：格言（「wire it or delete it」）、为效果的修辞碎片、拟人代码（「the plan holds it」）、比喻动词（「rides along」「stands on」）、stock framing。 「A dial worth turning」→「a parameter worth varying」。说本意。规则 26 覆盖隐喻名词。\n33. **过度压缩。** 丢冠词、无动词碎片、符号语、缩写让读者解码而非阅读。「Parser rejects bad date → exit 2, no write」→「The parser rejects a bad date, exits with code 2, and writes nothing.」写完整句，有冠词动词，展开箭头与缩写。\n","# Unslop\n\n编辑文本，去除 AI 模式。扫描下列模式，然后重写。保留含义，匹配预期语气。\n\n## 应检测并修复的模式\n\n规则编号是其他 skill 引用的稳定 id。删除的规则留空号。\n\n### 内容\n\n3. **肤浅的 -ing 短语。** 「highlighting...」「ensuring...」「reflecting...」「showcasing...」「fostering...」。删除或展开并给出真实来源。\n5. **模糊归因。** 「Experts believe」「Industry reports suggest」「Some critics argue」。点名来源或删除。\n\n### 语言\n\n7. **AI 词汇。** Additionally、crucial、delve、enduring、enhance、fostering、garner、interplay、intricate、landscape（抽象）、pivotal、showcase、tapestry（抽象）、testament、underscore、vibrant。换成平实词。\n8. **「是」的花式说法。** 「serves as」「stands as」「boasts」「features」。说「是」或「有」。\n9. **「Not just X, but Y.」** 直接陈述要点。\n10. **规则三。** 不要硬凑成三组。用自然数量。\n11. **同义轮换。** 一段里 protagonist、main character、central figure、hero 轮换。选一个，重复它。\n12. **假范围。** 「from X to Y」而 X、Y 不在有意义尺度上。直接列主题。\n\n### 风格\n\n13. **滥用 em dash。** 完全避免 em dash。只用句号或逗号（不用括号、en dash、连字符冒充破折号）。需要分隔就结束句子或用逗号。\n14. **滥用冒号。** 冒号在列表或示例前可以，不作句中连接词。「If you're coming from traditional automation: instead of...」里冒号无增益。重写让要点独立，不要比较 framing。\n15. **滥用粗体。** 不要每个专有名词或缩写都 bold。\n16. **行内标题列表。** 特征是 bold 标签加冒号复述同一行：「**Performance:** Performance improved...」。改成散文。bold 引导以句号结尾、命名条目且后跟真正新细节的（「**Schema in TypeScript.** Tables live in one file.」）可以，不是 tell。\n17. **标题 Title Case。** 用句首大写（sentence case）。\n18. **装饰 emoji。** 从标题与 bullet 删除。\n19. **弯引号。** 用直引号。\n\n### 沟通 artifact\n\n20. **聊天机器人套话。** 「I hope this helps!」「Let me know if...」「Of course!」「Certainly!」「Found the smoking gun!」删除。\n22. **谄媚语气。** 「Great question! You're absolutely right!」直接回应。\n\n###  filler\n\n23. ** filler 短语。** 「In order to」→「To」。「Due to the fact that」→「Because」。删掉「It is important to note that」。\n24. **过度 hedge。** 「could potentially possibly be argued that it might」→「may」。\n25. **泛化结论。** 「The future looks bright.」陈述具体计划或事实。\n\n###  jargon\n\n26. **抽象隐喻名词。** Substrate（base）、wedge、wedge in（add）、vector（way、method）、locus、vantage、nexus、primitive 作名词、harness 作隐喻、surface（如「API surface」）、bedrock、scaffolding 作隐喻、modality、paradigm、gold-plating（more than the job needs）、ratchet 作隐喻（机制真名，或 a limit that only tightens）、evacuate 指搬代码（move out）、endgame（the last phase）、north star、flywheel。读起来像技术词，通常有更平实的具体词。选具体词。\n\n### 平实表达\n\n27. **说做什么，不说感觉。** 「the database stays close at hand」「SQL you can read」「types that follow your schema」命名的是感觉。修复应命名机制或数字：「`.toSQL()` returns the exact string sent to the database」「a column rename fails the build」。问这句告诉读者做什么或知道什么，然后写那个。若无法 restate 为具体指令、事实或数字，删掉。再检查：若句原封不动可出现在别的项目文档，它对本项目什么也没说。删掉。\n28. **缩短或拆分密句。** 读者须回溯才能 parse 就拆两句或删从句。一句一思。\n29. **主动语态。** 优先。抓「is\u002Fare\u002Fwas\u002Fwere + past participle」并点名 actor：「queries are validated」→「the compiler validates queries」。仅 actor 未知或无关时被动可接受。\n30. **删副词或用更强动词。** 「runs quickly」→「is fast」或数字，「significantly improves」→实测 delta。副词撑弱动词说明动词选错了。\n31. **优先平实词。** 「utilize」和「leverage」→「use」，「facilitate」→「help」，「numerous」→「many」，「in the event that」→「if」。花哨同义词很少更清晰。\n32. **矫饰 prose。** 有字面说法处用隐喻或 flourish：格言（「wire it or delete it」）、为效果的修辞碎片、拟人代码（「the plan holds it」）、比喻动词（「rides along」「stands on」）、stock framing。 「A dial worth turning」→「a parameter worth varying」。说本意。规则 26 覆盖隐喻名词。\n33. **过度压缩。** 丢冠词、无动词碎片、符号语、缩写让读者解码而非阅读。「Parser rejects bad date → exit 2, no write」→「The parser rejects a bad date, exits with code 2, and writes nothing.」写完整句，有冠词动词，展开箭头与缩写。\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","e4477188d43269545432a83e4ac5d0733a812d09","skills\u002Funslop",0,"https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh","http:\u002F\u002Fpstack.ganhai.cloud","https:\u002F\u002Fgithub.com\u002Ffenfenxu","2026-10-21 12:14:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":23},[34,37,40],{"tool":35,"command":36},"npx","npx skills add fenfenxu\u002Fpstack-zh --skill unslop",{"tool":38,"command":39},"bunx","bunx skills add fenfenxu\u002Fpstack-zh --skill unslop",{"tool":41,"command":42},"pnpm","pnpm dlx skills add fenfenxu\u002Fpstack-zh --skill unslop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7DMHJV7QMEE1F43FFW98FV8","why","用于「为什么 X 是这样实现的」「为什么选了 Y」、设计理由、回归、事后复盘，或数据支撑的阈值问题。发现可用 MCP 并并行查询各证据类别（源码控制、工单跟踪、长文文档、实时聊天、基础设施可观测性、错误跟踪、产品分析数仓），然后返回带引用的决策与权衡解读。运行时行为请用 how。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7DMHGFGH2YT86WQ6A53693W","typescript-best-practices","TypeScript 最佳实践。读取或编辑任意 .ts 或 .tsx 文件时使用。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DMHEA1EGG2D9XQ33N66GDS","technical-writing","分层技术写作标准：Diátaxis 结构、Google 开发者风格句子、STE 指令规则、Global English 句法。用于 \u002Ftechnical-writing，或撰写\u002F审查文档、RFC、README、PR 描述、commit message 时。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7DMHCEXE1YRDR6XC1RXBG76","teach","用平实语言解释一段工作，让人真正理解。运行 how 与 why skill，把发现织成一份清晰说明。用于「teach me this」「help me really understand X」「explain this change or subsystem to me」。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7DMH9KNBP83SHAW4TGZ4713","tdd","仅当用户明确要求 TDD、失败测试或回归测试时使用，或 bug 有明显且廉价的本地测试目标时使用。测试路径不清、昂贵、偏集成或未要求时跳过。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7DMH7VJ55VC39J4K0SNXSA1","swarm","扇出 N 个并行 worker，收齐后返回一份报告。用于 \u002Fswarm、「swarm this」，或并行覆盖、race、gauntlet 与探索。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Fswarm\u002FSKILL.md",[],[]]