���频爱情 ���纯多平台母稿 Agent Skill
用于【女频爱情】题材下的多平台母稿提纯任务。作为题材包装层、兼容入口与路由层，负责保留女频爱情入口，补充情绪锚定、成长线优先、关系拉扯、柔爽感与现实共鸣边界，并明确要求优先强制加载并使用 `通用-提纯多平台母稿`。
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/lornshrimp/Lorn.NovelWriteSkills --skill 女频爱情-提纯多平台母稿The instruction itself
1 sections, as written by the author<!-- ===== Layer 1: 永久缓存 ===== -->
女频爱情-提纯多平台母稿
这是题材包装层、兼容入口与路由层。
<!-- ===== Layer 3: 场景缓存 ===== -->
对应通用 Skill
通用-提纯多平台母稿
本层职责
- 保留“女频爱情-提纯多平台母稿”这一题材入口名。
- 将该能力的共性骨架路由到
通用-提纯多平台母稿。 - 补充女频爱情题材在“多平台母稿提纯”上的情绪锚定、成长线优先、关系拉扯、柔爽感与现实共鸣边界。
- 在补写本题材 Skill 时，持续识别新增内容里哪些其实属于题材无关的通用能力，并将其回收到
通用-提纯多平台母稿或对应通用 Skill。
题材补充边界
- 默认按“前 300 字情绪钩子 + 身份锚定”处理起手，不接受慢热铺垫。
- 默认要求“成长线 > 爱情线”，关系推进必须反向供血人物成长，而不是让恋爱线吃掉主线。
- 女主必须有真实短板、现实代价与选择压力，拒绝悬浮完人和无痛强势。
- 情绪要优先落在动作、感官、物件、空间反常与对话错位上，避免抽象总结句。
- 默认服务手机端阅读：短句、短段、中段回报清晰、章末留追更驱动。
- 母稿优先稳住情绪主轴、成长逻辑与关系张力，避免改平台前源稿就先失温。
建议组合调用
通用-提纯多平台母稿
强制要求
- 命中本技能时，必须优先强制加载当前题材 Skill 与
通用-提纯多平台母稿。 - 当前题材 Skill 负责女频爱情题材的边界、补充口径与裁判要求，
通用-提纯多平台母稿负责共性能力本体与通用流程。 - 不得绕过
通用-提纯多平台母稿在本文件里恢复一整套平行共性规则。 - 引用通用能力时只按名称引用，不写路径。
- 若在编写或修改本题材 Skill 时新增了题材无关的规则、流程、模板或检查项，必须同步提取并沉淀到
通用-提纯多平台母稿或对应通用 Skill。
禁止事项
- 不要把女频爱情写成只有恋爱推进、没有成长承重的空心甜宠稿。
- 不要把情绪写成口号、把关系拉扯写成误会拖延、把爽点写成无代价碾压。
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take lornshrimp/女频爱情-提纯多平台母稿 from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.