What problem does it solve? Setting up and verifying the GameHub platform locally involves a multi-service stack (.NET backend, two Angular frontends, PostgreSQL via Docker) with several known pitfalls such as EAF 9.4.3 tenant-registration issues, ng serve binding problems, and source-map BOM errors. This Skill provides the exact steps and workarounds to get the full stack running and verify it works. ## Core Features & Use Cases - Local stack setup: Step-by-step commands to start Docker infrastructure, run EF migrations, launch the .NET backend on port 8001, and serve both the public UI (port 4200) and admin UI (port 8000). - Known workarounds: Fixes for the devtools-ignore-plugin BOM error, IPv6-only ng serve binding, m-switch toggle duplication, and the commonlookupmodal blocking the UI after login. - EAF 9.4.3 tenant-registration notes: Explains how TenantJoinRequest endpoints, public UI registration, and admin bootstrap were fixed and how to approve tenant requests via Swagger. - DevTools verification checklist: What to check for SignalR WebSocket negotiation, font decoding errors, and aria-hidden warnings. - Use Case: A developer clones the GameHub repo and needs to smoke-test the admin and public UIs locally, including registering a user and confirming SignalR chat connects. ## Quick Start Use the testing-gamehub skill to walk me through starting the local GameHub stack and verifying the admin UI login and SignalR connection.