Litestar middleware
Skill litestar-org/litestar-skills/skills/litestar-middleware
Opinionated first-party agent skills, plugins, subagents, slash commands, and MCP servers for the Litestar framework ecosystem — publishable to Claude Code, Gemini CLI, Codex CLI, Cursor, OpenCode, and VS Code/Copilot from a single repo.
npx -y skills add litestar-org/litestar-skills --skill litestar-middlewareAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Auto-activate for ASGIMiddleware, DefineMiddleware, middleware=, CORSConfig, CSRFConfig, AllowedHostsConfig, CompressionConfig, request IDs, or ASGI scopes. Not for route logic.
SKILL.md
2.2 KB, as published. Nobody here has run it
Litestar Middleware
Use this skill for built-in middleware config, custom ASGI middleware, request lifecycle hooks, and auth user loading.
Code Style Rules
- Use built-in middleware configs before custom middleware.
- Keep middleware focused on cross-cutting request behavior.
- Filter by ASGI scope when middleware applies only to HTTP or WebSocket.
- Keep business policy in Guards and services.
Quick Reference
- Middleware patterns: middleware.md
- Pair with litestar-auth-guards for permission checks.
- Pair with litestar-deployment for proxy and platform concerns.
Workflow
- Decide whether a built-in config solves the need.
- Choose custom middleware only for cross-cutting behavior.
- Set ordering deliberately.
- Verify HTTP and WebSocket behavior separately when both apply.
Guardrails
- Do not put business workflows in middleware.
- Do not apply HTTP-only middleware to WebSocket scopes.
- Do not mutate request state without documenting the key.
- Do not duplicate Guard policy in middleware.
Validation Checkpoint
- Middleware order is intentional.
- Scope filtering is correct.
- Built-in configs are used where available.
- Tests cover the request path affected by middleware.
Example
from litestar.middleware import ASGIMiddleware
middleware = [RequestIDMiddleware()]
References Index
Official References
- https://docs.litestar.dev/ - Litestar documentation
- https://docs.litestar.dev/latest/reference/ - Litestar API reference