What problem does it solve?
Building Litestar applications often requires correctly composing plugins, selecting appropriate first-party plugins over custom boilerplate, and avoiding common pitfalls like scattering plugin config or hiding route logic in plugin setup that break app readability and startup behavior.
Core Features & Use Cases
- Guided Plugin Composition: Prioritizes first-party Litestar ecosystem plugins for common integrations including databases, task queues, and frontend tooling.
- Custom Plugin Authoring: Provides patterns for building reusable plugins using InitPlugin and standard plugin protocols for app initialization, CLI extensions, and lifespan management.
- Best Practice Enforcement: Includes guardrails and validation checkpoints to ensure plugin config is settings-backed, lifecycle behavior is tested, and route logic remains separate from plugin concerns.
- Use Case: When building a production Litestar app that needs PostgreSQL access, background task processing, and Vite-powered frontend assets, this skill guides you to wire the correct first-party plugins instead of writing custom, hard-to-maintain glue code.
Quick Start
Use the litestar-plugins skill to wire the appropriate first-party plugins for my new Litestar app that uses PostgreSQL for data storage, SAQ for background tasks, and Vite for frontend asset management.