debug-live-autodarts-dom

Estrellas10

Forks0

Actualizado19 de junio de 2026 a las 12:46

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

thomasasen

thomasasen/autodarts-xconfig

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

2 archivos

SKILL.md

readonly

name	debug-live-autodarts-dom
description	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.

Goal

Use live browser evidence safely when DOM behavior, hydration, overlays, or page state cannot be proven from static code alone.

Browser rules

use only the currently active browser tab unless the user explicitly asks otherwise
do not switch tabs automatically
do not open new tabs unless explicitly required
do not navigate away from the active task context unless required
keep browser-side changes minimal and limited to debugging, reproduction, verification, or UI tests
use extra caution before destructive actions
if browser access is unavailable, continue static analysis where possible and state exactly what could not be verified

Local Chrome connection

expect Chrome CDP at http://127.0.0.1:9222
the persistent MCP profile is %LOCALAPPDATA%\Chrome-MCP-Profile
verify the endpoint through http://127.0.0.1:9222/json/version
prefer Chrome DevTools MCP for the existing active tab; use Playwright MCP when the task specifically requires it
if the endpoint responds but no browser page is visible to the MCP tool, report the MCP connection mismatch instead of opening another browser

Context budget

inspect browser state and the smallest relevant owner files
search first, then open nearest tests or helpers only when static context is needed
avoid dist/**
avoid docs/** unless task-relevant
stop expanding once live evidence explains the issue

Autodarts Scenarios

Consult references/live-dom-scenarios.md when choosing a live reproduction target.

Relevant scenarios include:

original match page without Tampermonkey for baseline DOM inspection
X01 page with no checkout
X01 page with visible checkout
virtual board
live board
Checkout Board Targets
TV Board Zoom
reload/F5 overlay hydration behavior

Output requirements

A valid result must separate observed browser facts from static-code inference and state any browser scenario that could not be verified.

Más de este repositorio

mismo repositorio

package-userscript-release

thomasasen/autodarts-xconfig

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.

2026-07-1610

clean-sonar-findings

thomasasen/autodarts-xconfig

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.

2026-07-1410

validate-repo-change

thomasasen/autodarts-xconfig

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.

2026-06-1810

oldrepo-parity-recovery

thomasasen/autodarts-xconfig

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.

2026-06-0410

xconfig-effect-preview-contract

thomasasen/autodarts-xconfig

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.

2026-05-1310

dart-asset-normalization

thomasasen/autodarts-xconfig

Normalize and verify bundled Dart marker PNG assets in autodarts-xconfig. Use when a file under `src/assets/darts/` is added, changed, replaced, visually misaligned, or when Dart marker tips no longer sit exactly on the board marker. Also use when updating Dart image geometry constants or asset tests.

2026-05-0110

name	debug-live-autodarts-dom
description	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.

Goal

Use live browser evidence safely when DOM behavior, hydration, overlays, or page state cannot be proven from static code alone.

Browser rules

use only the currently active browser tab unless the user explicitly asks otherwise
do not switch tabs automatically
do not open new tabs unless explicitly required
do not navigate away from the active task context unless required
keep browser-side changes minimal and limited to debugging, reproduction, verification, or UI tests
use extra caution before destructive actions
if browser access is unavailable, continue static analysis where possible and state exactly what could not be verified

Local Chrome connection

expect Chrome CDP at http://127.0.0.1:9222
the persistent MCP profile is %LOCALAPPDATA%\Chrome-MCP-Profile
verify the endpoint through http://127.0.0.1:9222/json/version
prefer Chrome DevTools MCP for the existing active tab; use Playwright MCP when the task specifically requires it
if the endpoint responds but no browser page is visible to the MCP tool, report the MCP connection mismatch instead of opening another browser

Context budget

inspect browser state and the smallest relevant owner files
search first, then open nearest tests or helpers only when static context is needed
avoid dist/**
avoid docs/** unless task-relevant
stop expanding once live evidence explains the issue

Autodarts Scenarios

Consult references/live-dom-scenarios.md when choosing a live reproduction target.

Relevant scenarios include:

original match page without Tampermonkey for baseline DOM inspection
X01 page with no checkout
X01 page with visible checkout
virtual board
live board
Checkout Board Targets
TV Board Zoom
reload/F5 overlay hydration behavior

Output requirements

A valid result must separate observed browser facts from static-code inference and state any browser scenario that could not be verified.