What problem does it solve? Shaping API request and response contracts in Litestar apps is error-prone when persistence models leak into wire payloads, field naming is inconsistent, or the generated OpenAPI schema drifts from the intended contract. This Skill guides DTO selection, field exclusion, renaming, and encoding so the /schema output matches the intended API contract. ## Core Features & Use Cases - DTO selection and configuration: Choose between MsgspecDTO, DataclassDTO, and SQLAlchemyDTO, then apply DTOConfig knobs like exclude, include, rename_fields, rename_strategy, partial, and max_nested_depth. - CamelCase wire naming: Use a CamelizedBaseStruct pattern so Python stays snake_case while the API ships camelCase field names. - OpenAPI contract validation: Verify request body schemas, response DTOs, RequestEncodingType, and /schema output against the intended contract. - Use Case: When building a user endpoint, exclude server-owned fields like id and created_at from the write DTO, rename fields to camelCase, and confirm the generated OpenAPI schema exposes only the intended fields. ## Quick Start Ask the assistant to create a Litestar write DTO for your model that excludes server-owned fields and uses camelCase wire names, then check the generated OpenAPI schema.
