菜单
Apply XP Simple Design principles when refactoring code — reduce duplication, improve clarity, and keep the fewest elements needed. Use when the user asks to clean up, improve, or refactor existing code.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dimanu-py/object-mother --skill xp-refactor命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Reviews technical proposals and architectural decisions against 30 complexity dimensions. Use when user proposes technical solutions, designs systems, or evaluates architectural choices. Questions necessity of scale, consistency, resilience, and other complexity drivers. Pushes for simplest viable approach. Use when: - User proposes specific technologies (Kafka, microservices, event sourcing, etc.) - Designing new systems or features - Evaluating architectural trade-offs - Someone says "we need" followed by complex infrastructure Do NOT use when: - Simple feature implementation (use hamburger-method or story-splitting instead) - Work is already planned and simple - User asks "how to" implement something specific (use micro-steps-coach instead)
Applies the Hamburger Method to slice features into vertical deliverable pieces. Use when user asks how to slice work, break down features into layers, or wants to deliver incrementally. Helps generate 4-5 options per layer and compose minimal vertical slices. Use when: - Feature feels large but not obviously splittable with story-splitting heuristics - User asks "how to slice" or "how to deliver incrementally" - Need to generate multiple implementation options - Want to compose end-to-end vertical slices Do NOT use when: - Story has obvious "and", "or", "manage" indicators (use story-splitting instead) - User is asking HOW to implement (use micro-steps-coach instead) - Feature is already small (< 1 day work)
Breaks down ANY work into 1-3 hour micro-steps with zero downtime. Use for large refactorings, technical improvements, debugging, research, migrations, or any work that feels too big or risky. Automatically applies expand-contract pattern for risky changes. Forces smallest safe increments for all work types. Use when: - Work feels too big or risky (refactoring, migrations, performance fixes) - Database schema changes, API changes, service replacements - User asks "how do I implement" after deciding what to build - Work will take more than 1 day Do NOT use when: - User is still deciding WHAT to build (use story-splitting or hamburger-method first) - Work is already small (< 3 hours) - User asks for architectural review (use complexity-review instead)
基于 SOC 职业分类
正在显示 SKILL.md
| name | xp-refactor |
| description | Apply XP Simple Design principles when refactoring code — reduce duplication, improve clarity, and keep the fewest elements needed. Use when the user asks to clean up, improve, or refactor existing code. |
Act as a Senior XP Developer applying XP Simple Design principles:
Analyze the code and identify refactorings that:
Prioritize refactors by ROI, considering:
Implement the highest-ROI refactor using:
Explain briefly:
The final result must be simpler and more maintainable than before.