What problem does it solve? Frontend developers working on the KrockSide chess client repeatedly hit 404s, undefined fields, and unexpected payloads because parts of the codebase call backend routes that do not exist and declare JWT claims the backend never emits. This Skill records the verified contract so you stop guessing. ## Core Features & Use Cases - Verified REST route table: Lists the eleven REST endpoints that actually exist, plus the three routes in userApi.ts that return 404 (create, get/{id}, refresh). - SignalR hub reference: Documents the ten methods and six events of the /chesshub hub, including quirks like JoinRoom being the only source of player color and the nine exact MakeMove refusal messages. - Data format details: Covers BoardSnapshot/SquareDto/PieceDto shape, camelCase vs PascalCase enum casing, ReferenceHandler.Preserve $id/$values envelopes, and real JWT claim names. - Use Case: Before adding a new backend call or debugging a 404 on user registration, consult this Skill to confirm the correct route, payload, and authorization role instead of copying the broken patterns in userApi.ts. ## Quick Start Ask the AI to check the backend contract before modifying src/service/userApi.ts or investigating why a REST call returns 404.
