Menü
Use for X01 checkout route logic, finish suggestions, checkout targets, score pulse, TV Board Zoom checkout interactions, bull semantics, and route/target regression analysis.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | analyze-x01-checkout-routing |
| description | Use for X01 checkout route logic, finish suggestions, checkout targets, score pulse, TV Board Zoom checkout interactions, bull semantics, and route/target regression analysis. |
Keep X01 checkout routing, finish visibility, and target semantics correct without mixing route rules with rendering concerns.
dist/**src/**docs/** unless wording is in scopeConsult references/checkout-regression-cases.md before changing checkout rules or target selection.
Require focused regression coverage for cases such as:
10 -> D522 -> D1150 where route S10 -> D20 is visible and finish-only zoom must not incorrectly prefer BULLA valid result must state whether route rules, target selection, board zoom, or score pulse behavior changed, and which focused regression cases cover it.
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.