Litestar DTO and OpenAPI

Use this skill for DTO selection, msgspec-first schemas, request/response typing, and OpenAPI shape.

Code Style Rules

• Prefer msgspec DTOs in Litestar apps unless the project is already Pydantic-led.
• Keep persistence models separate from API DTOs.
• Use camelCase wire names while Python stays snake_case.
• Exclude server-owned fields from write DTOs.
• Treat nullability and requiredness separately: T | None permits null; only a default value makes a field optional.

Quick Reference

• DTO patterns: dto.md
• Pair with litestar-data-services when mapping service results.
• Pair with msgspec for deeper Struct modeling.