alti3/litestar-contrib
plugins/litestar/skills/litestar-contrib/SKILL.md
Integrate Litestar contrib modules (for example HTMX, Jinja, Mako, JWT, OpenTelemetry, Pydantic, SQLAlchemy, Piccolo) with explicit scope and compatibility checks. Use when adding optional Litestar contrib features to an app. Do not use for core framework features that do not require contrib integrations.
$ install --global
skillsauthnpx skillsauth add alti3/litestar-skills litestar-contribInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 3:21 PM1.8s1 file scanned
SKILL.md
- name:
- litestar-contrib
- description:
- Integrate Litestar contrib modules (for example HTMX, Jinja, Mako, JWT, OpenTelemetry, Pydantic, SQLAlchemy, Piccolo) with explicit scope and compatibility checks. Use when adding optional Litestar contrib features to an app. Do not use for core framework features that do not require contrib integrations.
Contrib
Execution Workflow
- Identify the exact contrib module required for the user task.
- Install and configure only that module (avoid broad optional dependency sprawl).
- Verify compatibility with existing middleware, DTO, auth, and plugin stack.
- Add focused regression tests at integration boundaries.
Implementation Rules
- Keep contrib usage isolated behind clear adapters.
- Validate defaults before adding custom hooks/configuration.
- Treat each contrib add-on as an explicit architecture decision.
- Document operational implications (extra services, env vars, runtime dependencies).
Example Pattern
# Pattern: wire one contrib integration at app creation.
from litestar import Litestar
app = Litestar(
route_handlers=[...],
plugins=[...], # add only the contrib plugin you need
)
Validation Checklist
- Confirm contrib integration loads correctly at app startup.
- Confirm failure behavior is explicit when optional dependencies are missing.
- Confirm integration does not silently alter unrelated routes.
Cross-Skill Handoffs
- Use
litestar-pluginsfor plugin-system-focused integrations. - Use
litestar-metrics,litestar-authentication,litestar-databases, orlitestar-templatingfor topic depth after contrib setup.
Litestar References
- https://docs.litestar.dev/latest/usage/contrib.html
- https://docs.litestar.dev/latest/reference/contrib/index.html
Related Skills
alti3/litestar-websockets
development
VerifiedTrustedCommunity
Build Litestar WebSocket endpoints with low-level websocket handlers, websocket listeners, websocket streams, dependency injection, custom websocket classes, transport-mode control, and graceful connection lifecycle handling. Use when implementing bidirectional real-time communication, reactive websocket message handling, or proactive server push over WebSockets. Do not use for server-side pub/sub fanout that is better expressed with channels alone.
5SKILL.mdUpdated Apr 3, 2026
alti3/litestar-testing
tools
VerifiedTrustedCommunity
Test Litestar applications with TestClient, AsyncTestClient, create_test_client, websocket test helpers, dependency overrides, mocked dependencies, lifecycle-aware fixtures, and deterministic success and failure assertions. Use when adding or fixing Litestar test coverage, including exception contracts, override precedence, websocket behavior, event-bus side effects, or live-server-only response patterns. Do not use as a substitute for production observability or runtime debugging strategy.
5SKILL.mdUpdated Apr 3, 2026
alti3/litestar-templating
development
VerifiedTrustedCommunity
Configure Litestar templating with `TemplateConfig`, Jinja/Mako/MiniJinja engines, file-or-string `Template` responses, request and CSRF-aware context, template callables, and custom engine integration. Use when implementing or fixing server-rendered HTML in Litestar. Do not use for static asset serving or pure JSON API endpoints.
5SKILL.mdUpdated Apr 3, 2026
alti3/litestar-stores
development
VerifiedTrustedCommunity
Configure Litestar stores and the store registry for caching, server-side sessions, rate limiting, and other key-value state with explicit backend selection, bytes-safe data handling, TTL and renewal policy, namespacing, registry wiring, and lifecycle cleanup. Use when a Litestar app depends on `MemoryStore`, `FileStore`, `RedisStore`, `ValkeyStore`, or `StoreRegistry`. Do not use for relational persistence, domain repositories, or response-caching policy details that belong in database or caching-focused skills.
5SKILL.mdUpdated Apr 3, 2026