Litestar Exceptions

Use this skill for domain exception hierarchies, handler registration, and HTTP error response shape.

Code Style Rules

• Centralize domain-to-HTTP translation in exception handlers.
• Keep route handlers free of repetitive try/except blocks.
• Use domain exception classes when services need stable error contracts.
• Keep validation errors aligned with DTO and OpenAPI behavior.
• Use ProblemDetailsPlugin explicitly when the API contract requires RFC 9457. Native HTTPException responses are Litestar's JSON error envelope.

Quick Reference

• Exception patterns: exceptions.md
• Pair with litestar-auth-guards for permission failures.
• Pair with litestar-data-services for not-found and conflict behavior.