litestar

Routes Litestar project tasks to the appropriate focused Litestar subskill.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/renjianguo666/litecms --skill litestar-renjianguo666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: litestar
Source: https://github.com/renjianguo666/litecms/tree/main/.agents/skills/litestar
Command: npx skills add https://github.com/renjianguo666/litecms --skill litestar-renjianguo666

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Litestar projects span routing, DTOs, auth, DI, data services, settings, middleware, plugins, realtime, testing, and deployment, making it hard to know which guidance applies to a given task. This hub skill orients a Litestar project and selects the correct focused subskill so app-level architecture stays coherent. ## Core Features & Use Cases - Task Routing: Maps concrete project signals (route decorators, DTO classes, guards, dependency maps, settings modules) to the right narrow Litestar skill via a quick-reference table. - App-Level Composition Guidance: Enforces thin app setup that composes controllers, plugins, middleware, DI, settings, and exception handlers from domain modules. - Cross-Boundary Coordination: Defines how to combine the minimum set of skills when a task spans routing, services, and DTOs. - Use Case: When asked to add a users endpoint backed by an existing service with an OpenAPI schema, the hub directs work to litestar-routing, litestar-data-services, and litestar-dto-openapi. ## Quick Start Ask the assistant to orient your Litestar project and choose the right Litestar subskill for the task you are about to implement.

Frequently Asked Questions about litestar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Litestar skill for my task?

Inspect the project for concrete signals such as route decorators, DTO classes, guards, or settings modules, then match them to the quick-reference table. Controllers map to litestar-routing, DTOs to litestar-dto-openapi, and so on.

When should I use the Litestar hub skill instead of a focused skill?

Use the hub only when orienting a project, scaffolding app-level structure, or when a task crosses boundaries. If the task has a clear owner like routing or auth, go directly to that focused skill.

How do I handle a Litestar task that spans multiple concerns?

Combine the minimum needed skills and name each one explicitly. For example, adding an endpoint backed by a service with an OpenAPI schema uses litestar-routing, litestar-data-services, and litestar-dto-openapi together.

Does Litestar support async request handlers and dependency injection?

Yes. The hub's style rules require async I/O for request handlers, service methods, and external clients, and dependency injection is handled through Provide and dependency maps covered by the litestar-di skill.

What are the limitations of the Litestar hub skill?

The hub contains no deep implementation references and is not a substitute for focused skills. It should not be used for detailed routing, DTO, auth, DI, data, settings, middleware, plugin, realtime, AI, deployment, or testing work.