메뉴
WebSocket message type constants (frontend MsgType enum vs backend MSG_TYPE_* in ws.py) must stay in sync. Trigger when editing src/stankbot/web/ws.py, src/stankbot/web/frontend/src/lib/ws.ts, or src/stankbot/web/frontend/src/lib/ws.test.ts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Browser automation, UX review, frontend debugging, E2E test writing, mock endpoint catalog. Trigger when asked to review UX, debug the dashboard, write E2E tests, take screenshots, or inspect pages. Also trigger when `stank-frontend-patterns` fires and introduces new components/pages/test-ids.
Enforces Alembic migration conventions when creating or editing migrations, models, or running alembic commands. Trigger when touching migrations/versions/, db/models.py, or adding/removing columns.
Enforces stank-bot scoring invariants when editing scoring_service.py, chain_service.py, or scoring-related settings. Trigger when modifying SP/PP formulas, position bonuses, finish bonus, Team Player, or ScoringConfig.
Conventions for stank-bot's per-guild embed templates (board, record, session-start/end, points, cooldown). Trigger when editing src/stankbot/services/template_engine.py, board_renderer.py, template_store.py, embed_builders.py, default template strings, or dashboard routes that author templates.
Enforces stank-bot's SvelteKit frontend conventions — component hierarchy, store barrel, shared utilities, testing patterns. Trigger when editing any file under src/stankbot/web/frontend/src/ or creating new Svelte/TS modules there.
Enforces stank-bot's event-sourcing invariants when writing code that mutates domain state. Trigger when adding/editing any code path that changes player totals, chain state, sessions, records, or achievements — i.e. anything in src/stankbot/services/* or repositories that writes to the DB. Also trigger when writing rebuild/backfill scripts that touch totals.
| name | stank-ws-protocol |
| description | WebSocket message type constants (frontend MsgType enum vs backend MSG_TYPE_* in ws.py) must stay in sync. Trigger when editing src/stankbot/web/ws.py, src/stankbot/web/frontend/src/lib/ws.ts, or src/stankbot/web/frontend/src/lib/ws.test.ts. |
The frontend MsgType enum in ws.ts and the backend MSG_TYPE_* constants in ws.py define the same numeric values for every message sent over the WebSocket. Translations happen in ws.ts (handleMessage switch) and ws.py (the msg_type == MSG_TYPE_PING .. MSG_TYPE_VERSION_RESPONSE handler).
Every numeric type in the enum MUST have a matching constant on the backend.
src/stankbot/web/frontend/src/lib/ws.ts — MsgType enum.src/stankbot/web/ws.py — top-level MSG_TYPE_* module constants.If you insert a new message type ID in the middle of the enum, you MUST shift all subsequent types. Inserting does not just append — it renumbers everything after it. The original VERSION_MISMATCH bug (108 → 109) happened precisely because GAME_EVENT = 107 was inserted between SESSION (106) and ERROR (107), shifting ERROR→108 and VERSION_MISMATCH→109, but the backend never got the memo.
When adding a new message type, update ALL of these:
ws.ts — MsgType enum + interface + ServerMsg union + handleMessage case.ws.py — MSG_TYPE_* constant + handler or broadcast_json call.ws.test.ts — it('should have correct server message types') block.test_ws.py — TestMessageTypes.test_msgtype_values + relevant broadcast test.board.spec.ts or events.spec.ts — if the new type has a visible effect, add an E2E case for it.No hardcoded numbers. Backend broadcast helpers must use the named constants (MSG_TYPE_CHAIN_UPDATE, not 103). Frontend message handling must use the enum (MsgType.CHAIN_UPDATE, not 103).
When intercepting WS frames in Playwright E2E tests, use ws.on('framereceived', handler) — not ws.on('frames'). The latter receives a batch array; framereceived fires for each individual message and gives access to frame.payload (Buffer for binary msgpack frames).
broadcast_json or send_bytes call that could be replaced with a MSG_TYPE_* constant.ws.ts with no corresponding MSG_TYPE_* in ws.py.ws.test.ts values that disagree with the current MsgType enum — they tend to drift when types shift but tests aren't updated.