What problem does it solve? Structuring routes in a Litestar application becomes inconsistent as the codebase grows, leading to handlers grouped by HTTP method, fat controllers with business logic, and scattered authorization code. This Skill provides canonical patterns for organizing routes by business domain using Controllers, Routers, and DomainPlugin layout. ## Core Features & Use Cases - Controller Patterns: Group related routes under a Controller class with shared path, guards, dependencies, and tags, keeping handlers thin and async. - Domain-Clustered Layout: Organize code into domain folders where each domain owns its controllers, services, schemas, guards, and jobs, with shared infrastructure in lib/. - Router Composition: Wire Controllers into the app via Router composition or DomainPlugin auto-discovery, with a complete end-to-end vertical slice example. - Use Case: When adding a new tasks feature to a Litestar API, use this Skill to scaffold the Controller with typed path parameters, guard placement, filter dependencies, and app wiring following the canonical fullstack layout. ## Quick Start Ask the AI to design a Litestar Controller for a new domain with list, get, create, update, and delete endpoints following domain-clustered routing conventions.
