菜单
Use when a single file/class has grown into tightly coupled “spaghetti” (mixed UI, IO, state, input, gameplay), making changes risky, tests hard to write, and refactors frequently break behavior—especially under strict type/warning-as-error environments like Godot 4.x.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when implementing any non-trivial feature, integration, refactor, or bugfix in this repo where there is a risk of skipping analysis/design/planning or skipping tests due to time pressure, scope pressure, or sunk-cost pressure.
Use when starting a new repo or onboarding an AI agent and you need to create or overhaul an AGENTS.md so work stays safe, testable, and consistent across environments (e.g., Godot + SDK + demo apps), especially when the project has strict tooling, sandboxes, or multiple "products" in one codebase.
适用于需要 PRD/Spec + 版本化执行计划（docs/plan/vN-*）+ 端到端验证的项目。通过严格的 PRD ↔ 计划 ↔ 测试 ↔ 代码追溯链，防止文档漂移与返工，直到愿景与实现之间无差异、无保留、无妥协。
Use when Codex repeatedly prompts for the same safe actions (running tests, reading logs, git operations) and the user wants those already-approved actions persisted into Codex approval config (trust levels + allow rules) so future sessions don’t require re-approval.
Render and view webpages using a headless browser (Playwright) to fetch JS-rendered HTML, extract visible text, and optionally save full-page screenshots. Use when a user asks to “无头浏览器打开/查看网页”, needs the rendered DOM instead of raw curl HTML, or wants a screenshot of a page.
End-to-end source code repository deep dive and review. Use when you need to understand a repo’s architecture, core abstractions, entrypoints and execution flow, extension points, and operational/developer setup; and when you must deliver a structured report (Markdown + standalone HTML) with diagrams (Mermaid), actionable recommendations, and a scored evaluation.
| name | spaghetti-refactor |
| description | Use when a single file/class has grown into tightly coupled “spaghetti” (mixed UI, IO, state, input, gameplay), making changes risky, tests hard to write, and refactors frequently break behavior—especially under strict type/warning-as-error environments like Godot 4.x. |
目标不是“变优雅”，而是把“高风险的一坨代码”拆成可验证的小模块：保持行为稳定、保持对外 API 稳定、让后续功能可以“在边上加模块”而不是继续往中心堆。
这份技能来自 vr_offices/VrOffices.gd 的多轮重构经验（v7–v9，以及后续迭代的延续实践）。
符合任意 2 条就该触发：
不要用于：
把不会频繁变动的东西先抽走，收益最大、风险最小：
Data.gdWorldState.gdSaveController.gd要点：数据与 IO 从业务里剥离，否则每次改业务都在改 IO。
把“外设驱动”拆成 controller，主脚本只做 wiring：
原则：一个 controller 只负责一种变化维度。
主脚本（例如 VrOffices.gd）只做：
@onready 取节点这样后续功能（比如 workspaces）可以“新增模块 + 接线”，不会把主脚本再写回意大利面。
var x := null 让类型推断失败；用 var x: Node = null 或者不显式类型name, scale, floor 等）--verbose 查泄漏/资源释放。docs/plan/vN-index.md：写清楚目标、DoD、证据、验证命令