What problem does it solve? The ChessLobby component in the KrockSide React frontend contains known defects—silent returns, a broken getUser call, a navigation race condition, and a color selector the server ignores—that make joining a chess room unreliable. This Skill gives developers the full domain context, event contracts, and cataloged technical debt needed to fix or extend the lobby without rediscovering every trap. ## Core Features & Use Cases - Join-room flow documentation: Maps the exact seven-step handleJoinRoom sequence, including the three silent returns and the getUser route/field mismatch (DT-02/DT-03) that aborts the flow. - SignalR event contract reference: Details PlayerJoined, PlayerLeft, GameStarted, RoomFull, and RoomNotFound handling, including the empty GameStarted handler that should drive navigation (DT-08). - Prioritized fix roadmap: Orders remediation from correcting getUser, to replacing silent returns with setErrorMessage, to propagating joinResult.color to the board (DT-01). - Use Case: A developer investigating why the "Entrar na Sala" button appears to do nothing can consult this Skill to learn the click dies in a silent return after a 404 from the nonexistent get/{id} route. ## Quick Start Use the lobby-e-sala skill to explain why clicking join room in ChessLobby shows no error and how to fix the navigation race condition.
