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