dmlin7777777

江南（杨治）写作技法视角 Skill —— 叙事协议版。 给每个人的龙族一个结局。 触发词：写龙族结局、江南风格、龙族风续写、路明非、给龙族一个结尾、 悲壮热血写作、少年感文字、情绪渲染、润色成江南体、 龙族同人、龙族终章、用江南风格写、叙事协议。

求职教练，不是润色器。针对 JD 交互式定制简历，编造阻断门确保每条经历经得起面试追问。HTML + Markdown 双交付。

Use when the user needs to write, improve, or review a README.md for an Agent Skill. Triggers: "write a README for my skill", "improve my skill's README", "review this README", "帮我写 README", "优化 README", "怎么写 skill 的 README", "README 不够好". Covers 8 skill types, each requiring a different README strategy because each answers a different human decision question. NOT for traditional project READMEs (Install/Usage/Contributing) — those are a different format.

When a new idea arrives mid-development, classify it, assess destructiveness, audit consumers, and choose the lowest-impact integration path instead of rewriting.

用户用 vibe coding 方式(Claude Code/OpenClaw/Cursor 等 AI agent 写代码)开发产品时,agent 必须遵守的执行铁律。Use this skill whenever the user is building/modifying any software project with agent assistance — including UI changes, refactors, new features, bug fixes, or any code editing task. Especially trigger when user mentions 项目名(如观复)、modifying components, adding features, 'help me implement X', '改一下这个', 'optimize the Y'. Even if user doesn't explicitly invoke this skill, you should consult it before ANY non-trivial code change to a real project. Three core rules: (1) follow five-section prompting structure, (2) never expand scope beyond what user asked, (3) reject premature architecture in 0→1 stage. Pair with ideas-inbox skill for handling drift.

管理开发/测试/体验产品时冒出来的新想法,防止'测试时一个想法直接变成开发计划修改'这种节奏被打断的情况。Use this skill whenever: (1) user is testing/experiencing a product they're building and mentions new ideas, (2) agent itself encounters bugs/improvements/extensions outside current task scope, (3) user says 'I just thought of...', '冒出来一个想法', '顺便也...', or any similar phrasing that suggests scope creep. Also trigger at end of dev sessions for inbox review. The skill enforces a three-class taxonomy (A-bugs/B-optimization/C-extension) and a 24-hour cooling rule for C-class ideas.