What problem does it solve? Server-side work in this estate spans five very different stacks — a Go modular monolith, Django/DRF, two FastAPI services, a FastAPI+SQLite app, and Laravel — each with non-obvious conventions, known-unfixed bugs, and traps (silent test skips, spoofable client IPs, truthy string 'false' authorization flags) that cost real time to rediscover. ## Core Features & Use Cases - Per-stack conventions: Documents routing, migrations, session cookie rules, rate limiting, and testing practices for the Go Survey-Forms backend, Exam Studio services, CleverClass, and phd-monitoring. - Known-trap documentation: Records live issues like the retrieval engine's silent HashingEmbedder fallback, the lms-tutor X-Forwarded-For bug, and Laravel's broken can_* guards, so they are not reintroduced or misread. - Use Case: When adding an API endpoint to the Go backend, follow the documented stdlib ServeMux routing, goose migration workflow, and session cookie rules instead of introducing a router dependency or breaking the SameSite policy. ## Quick Start Ask the assistant to apply the backend skill conventions when writing or modifying an API handler, migration, or background job in any of these repositories.