alti3/litestar-cli
plugins/litestar/skills/litestar-cli/SKILL.md
Use Litestar CLI for app autodiscovery, explicit app targeting, operational commands, schema generation workflows, and CLI extension points. Use when standardizing local/dev/ops command workflows around Litestar. Do not use for runtime app design decisions that belong in application code.
$ install --global
skillsauthnpx skillsauth add alti3/litestar-skills litestar-cliInstall 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 3, 2026, 4:00 PM4.8s2 files scanned
SKILL.md
- name:
- litestar-cli
- description:
- Use Litestar CLI for app autodiscovery, explicit app targeting, operational commands, schema generation workflows, and CLI extension points. Use when standardizing local/dev/ops command workflows around Litestar. Do not use for runtime app design decisions that belong in application code.
CLI
Execution Workflow
- Ensure app autodiscovery works (canonical module layout) or define explicit app import path.
- Standardize
litestarcommands in project scripts and team docs. - Separate local development commands from production runtime commands.
- Extend CLI only when command reuse materially improves team workflows.
Implementation Rules
- Keep one canonical entrypoint for commands and deployment.
- Avoid hidden env assumptions; make required env vars explicit.
- Pin command flags in scripts to avoid accidental behavior drift.
- Prefer explicit app targets in CI/CD for reproducibility.
Example Pattern
# Autodiscovery mode
litestar run
# Explicit app target mode
litestar --app path.to.app:app run
Validation Checklist
- Confirm
litestar runand other core commands resolve the correct app. - Confirm schema-related CLI commands run in CI without manual steps.
- Confirm command aliases/scripts behave consistently across environments.
Cross-Skill Handoffs
- Use
litestar-app-setupwhen autodiscovery or app factory layout is broken. - Use
litestar-openapifor schema generation quality, not just CLI invocation.
Litestar References
- https://docs.litestar.dev/latest/usage/cli.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