菜单
Run and debug specify-poker end-to-end behavior against the docker-compose stack using Playwright (apps/ui/tests/e2e), including stack bring-up, readiness checks, and log/trace triage with docker compose and Grafana Loki/Tempo.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Integrate and troubleshoot Grafana Mimir as the Prometheus-compatible metrics backend in specify-poker’s docker-compose stack, including OTel Collector scraping + remote_write, Grafana datasource provisioning, PromQL validation, and diagnosing ring/remote-write startup issues. Use when replacing Prometheus, debugging missing metrics/service map, or fixing Mimir/otel-collector compose failures.
Triage and debug specify-poker issues using the LGTM stack (Grafana + Loki + Tempo + Mimir) and docker compose logs, centered on OpenTelemetry traceId correlation across gateway/game/balance/player/event/notify; use for failing E2E tests, runtime 5xx/gRPC INTERNAL errors, auth/join-seat failures, or production-like compose debugging.
Troubleshoot Grafana Tempo traces and the Tempo Service Map in specify-poker’s docker-compose LGTM stack. Use when Grafana shows empty traces/service map, service-map edges look slow, Tempo search errors like “invalid start … value out of range”, or trace panels are missing data.
Debug stalled poker hands and table UI issues in specify-poker (stuck on preflop, turn never advances, hand timers not firing, players can't see their own hole cards, duplicate seating, invalid hand.turn/seat status) using Gateway APIs, Game Service state, and docker-compose logs.
Create or expand consumer-centric test suites and coverage for microservices (gRPC/HTTP handlers, service flows, event consumers, caches, jobs, observability) while preserving behavior and hitting coverage targets. Use when asked to add tests, raise coverage, or validate consumer-facing behavior across services.
Reduce branching and nested control flow in TypeScript while preserving behavior; use when asked to simplify, flatten, or refactor conditional logic for testability/readability.
| name | specify-poker-e2e |
| description | Run and debug specify-poker end-to-end behavior against the docker-compose stack using Playwright (apps/ui/tests/e2e), including stack bring-up, readiness checks, and log/trace triage with docker compose and Grafana Loki/Tempo. |
docker compose up --build -dPLAYWRIGHT_EXTERNAL=1 npm --prefix apps/ui run test:e2eFollow this loop until tests pass (prefer fixing root causes, not test retries):
npm --prefix apps/ui run test:e2e -- <test-file> -g "<test name>"docker compose logs -f gatewaydocker compose logs --since 10m gateway player game balance event notifytraceId and spanId fields; use the traceId to correlate across services.{service="gateway"} | json | traceId="<traceId>"traceId to open the distributed trace.PLAYWRIGHT_EXTERNAL=1 to disable the Playwright webServer and run against docker-compose.PLAYWRIGHT_BASE_URL to target a non-default UI URL (default http://localhost:3000).PLAYWRIGHT_GATEWAY_URL, PLAYWRIGHT_KEYCLOAK_URL, PLAYWRIGHT_GRAFANA_URL, PLAYWRIGHT_LOKI_URL, PLAYWRIGHT_TEMPO_URL for non-default service URLs.PLAYWRIGHT_STACK_TIMEOUT_MS (default 120000) or PLAYWRIGHT_SKIP_STACK_WAIT=1 to control global stack readiness polling.{"error":"ACCOUNT_NOT_FOUND"} when joining a table: check Gateway table-join flow and Balance account provisioning.13 INTERNAL: Table ID is required from gateway: check WS session-event publishing includes a non-empty table_id.profiles_pkey duplicate key errors: check Player profile provisioning uses INSERT ... ON CONFLICT (avoid error-log spam).PREFLOP / “Current Turn” points at an empty seat: inspect hand.turn + seat statuses and look for duplicate seating; use .codex/skills/specify-poker-game-stall-triage/SKILL.md.scripts/stack_up.sh: Bring up the stack and print key URLs.specs/*.md and service specs in apps/*/spec/*.md as the source of truth for E2E behavior.