litestar-org Litestar Routing Hub
Use this skill to choose the right focused Litestar skill and keep app-level choices coherent. For implementation details, open the narrow skill that matches the task.
This guidance targets the released Litestar 2.24.0 contract. Do not copy
unreleased main APIs into consumer examples.
Code Style Rules
- Prefer first-party Litestar ecosystem packages and patterns.
- Match the project's existing stack for data access, serialization, DI, settings, background jobs, and deployment.
- Keep app setup thin: compose routes, plugins, dependencies, middleware, exception handlers, and settings from domain modules.
- Use async I/O for request handlers, service methods, background integration, and external clients.
Quick Reference
| Task | Skill |
|---|---|
| Controllers, route decorators, Routers, domain folders | litestar-routing |
| DTOs, request bodies, response schemas, OpenAPI | litestar-dto-openapi |
| Authentication, authorization, Guards | litestar-auth-guards |
| Provide, dependency maps, Dishka wiring | litestar-di |
| Repositories, services, filters, pagination | litestar-data-services |
| Settings, env loading, app state | litestar-settings |
| Domain exceptions and exception handlers | litestar-exceptions |
| Built-in or custom middleware | litestar-middleware |
| Plugin protocols and app plugin composition | litestar-plugins |
| WebSockets, SSE, Channels | litestar-realtime |
| Google ADK / agent HTTP serving | litestar-ai-serving |
| Tests | litestar-testing |
| Build artifacts | litestar-build |
| Deployment targets | litestar-deployment |
Workflow
- Inspect the project for concrete signals: route decorators, DTO classes, guards, dependency maps, service classes, settings modules, plugin lists, realtime handlers, tests, build files, or deploy files.
- Select the narrow skill from the table above. Use the hub only while routing the task or composing app-level architecture.
- If the task crosses boundaries, combine the minimum needed skills. Example: route plus service plus DTO means routing, data-services, and DTO/OpenAPI.
- Keep the selected stack consistent across the app. Do not mix two persistence or DI patterns in one feature unless the existing code already does.
Guardrails
- Do not use this hub as a substitute for a focused skill when the task has a clear owner.
- Do not infer a new stack from examples. Match the current project first.
- Do not move auth checks, data queries, settings parsing, or background work into route handlers.
- Do not add generic ASGI guidance when Litestar has a first-party pattern.
Validation Checkpoint
- The focused skill selection matches the files being edited.
- Cross-cutting work names every involved skill explicitly.
- The app setup stays compositional: controllers, plugins, middleware, DI, settings, and handlers remain separated.
- Validation commands use Make targets from this repo when editing skills.
Example
User asks: "Add a users endpoint backed by the existing service and return an OpenAPI schema."
Use:
- litestar-routing for Controller shape.
- litestar-data-services for service injection and filters.
- litestar-dto-openapi for request and response DTOs.
References Index
This hub has no deep references. Open the focused skill that owns the topic.
Official References
- https://docs.litestar.dev/ - Litestar documentation
- https://docs.litestar.dev/latest/reference/ - Litestar API reference
- https://github.com/litestar-org/litestar/tree/v2.24.0 - Audited Litestar 2.24.0 source