alti3/litestar-custom-types
plugins/litestar/skills/litestar-custom-types/SKILL.md
Add custom type decoding/encoding and schema compatibility in Litestar for domain-specific values that are not handled by default serializers. Use when handlers need strongly typed custom inputs or outputs. Do not use when built-in scalar/model types already satisfy request and response contracts.
$ install --global
skillsauthnpx skillsauth add alti3/litestar-skills litestar-custom-typesInstall 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.9s1 file scanned
SKILL.md
- name:
- litestar-custom-types
- description:
- Add custom type decoding/encoding and schema compatibility in Litestar for domain-specific values that are not handled by default serializers. Use when handlers need strongly typed custom inputs or outputs. Do not use when built-in scalar/model types already satisfy request and response contracts.
Custom Types
Execution Workflow
- Define the domain type and its canonical wire representation.
- Register type decoders/encoders at the appropriate layer.
- Ensure OpenAPI schema generation remains accurate for custom values.
- Add round-trip tests for decode, business usage, and encode output.
Implementation Rules
- Keep serialization behavior stable and backward compatible.
- Fail fast with actionable error messages on invalid input.
- Avoid ambiguous representations that vary by locale/timezone.
- Keep custom type support centralized to prevent drift.
Example Pattern
from datetime import datetime
from litestar import Litestar, get
def parse_timestamp(value: str) -> datetime:
return datetime.fromisoformat(value)
@get("/echo-ts/{value:str}")
async def echo_timestamp(value: datetime) -> dict[str, str]:
return {"value": value.isoformat()}
app = Litestar(route_handlers=[echo_timestamp], type_decoders=[(datetime, parse_timestamp)])
Validation Checklist
- Confirm valid payloads decode to the intended Python types.
- Confirm invalid payloads return deterministic client errors.
- Confirm encoded responses and generated schemas match actual runtime behavior.
Cross-Skill Handoffs
- Use
litestar-openapiif schema customization is substantial. - Use
litestar-requestsandlitestar-responseswhen custom types appear at API boundaries.
Litestar References
- https://docs.litestar.dev/latest/usage/custom-types.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