Use when adding or changing features that affect lifecycle phases, service startup/shutdown, EventBus/IPC boundaries, shared state ownership, background processes, or cross-module responsibilities.
MANDATORY rules for adding or changing any AppConfig field (data layer only — independent of whether a settings-screen UI is involved). Covers AppConfig type, CONFIG_METADATA, CONFIG_KEYS, DEFAULT_CONFIG registration and persistence model.
Pipeline instructions for creating events, subscribing via EventBus, and syncing with the Renderer (React) via IPC.
Use when changing anything under src/main/kakao/ (login/launch automation, PageHandler selectors, SecurityCenter, visibility policy, page dumps, maintenance detection) or the KakaoGames starter/UAC path (src/main/utils/uac/kakao-game-starter.ts, uac-migration.ts). Third-party-DOM selector policy and real-user blast radius rules.
Use when a user says a feature, bug fix, experiment, or follow-up can wait, should be done later, belongs on the roadmap/backlog, or asks to add/update roadmap items. Two tracks — user-visible product changes go to docs/Roadmap.md (CI-synced to GitHub Issue
Declarative pipeline for rendering and wiring settings-SCREEN UI items (settings-config.ts items, Context API hooks, no-hardcoding rule). For the underlying AppConfig data-layer registration, use config-management first.
Use this skill whenever debugging or visually verifying the POE2 launcher UI, Electron runtime errors, Vite dev-server behavior, Chrome DevTools attachment, screenshots, or CDP capture. This project is Windows-first; this skill prevents WSL/mock-browser verification mistakes by forcing pwsh npm run dev, launcher terminal logs, Chrome remote debugging, and real Electron screenshots.
Use whenever running GitHub CLI (`gh`) or GitHub HTTPS git push from this repo, including PR creation, PR merge, PR checks, issues, Actions, or branch publishing. Enforces repo-local `.env` `GH_TOKEN` injection into the child process without mutating global `gh` auth state.