菜单
Keep user-facing wording aligned with shipped behavior in autodarts-xconfig. Use when feature names, config labels, defaults, README sections, menu descriptions, or module wording need to stay in sync. Do not use for pure internal refactors with no user-facing text impact.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Package or verify an autodarts-xconfig userscript release. Use only for explicit release, finalize, package, ship, publish, version bump, `dist/` refresh, or publication-state verification work. Do not use for ordinary code changes.
Use for explicit SonarQube issue cleanup, Sonar code smells, low-risk static-analysis fixes, and touched-scope Sonar remediation. Do not use for normal validation unless cleanup is explicitly requested.
Use for live browser, DOM inspection, Playwright MCP, Chrome DevTools MCP, Autodarts page inspection, reproduction, console/network checks, and UI verification tasks. Do not use for ordinary static code review.
Choose and report the smallest sufficient local validation for an autodarts-xconfig change. Use after meaningful source changes, when validation scope is unclear, or when final reporting must include residual risk. Do not use for Tier 0-only edits unless needed to document skipped validation.
Recover known-good behavior from `.oldrepo` without reintroducing the old structure. Use when the current modular implementation diverges from proven legacy behavior and the task is to recover that behavior in the right modern layer. Do not use for greenfield features with no legacy predecessor.
Use when adding, fixing, or reviewing xConfig administration previews for feature effects, especially hover/focus previews that must reflect the real runtime effect without leaking timers, classes, DOM state, or fake CSS-only behavior.
| name | docs-config-sync |
| description | Keep user-facing wording aligned with shipped behavior in autodarts-xconfig. Use when feature names, config labels, defaults, README sections, menu descriptions, or module wording need to stay in sync. Do not use for pure internal refactors with no user-facing text impact. |
Keep user-facing wording, config naming, and documentation aligned with actual shipped behavior.
For each changed feature, identify:
Describe:
A valid result from this skill must:
