What problem does it solve? Scattered try/except blocks and inconsistent error payloads make Litestar APIs hard to maintain. This Skill centralizes domain-to-HTTP error translation through a single exception hierarchy and app-level handlers, so route handlers stay clean and error responses stay consistent. ## Core Features & Use Cases - Domain Exception Hierarchy: Define a project-local hierarchy rooted in an ApplicationError base class with stable status codes for validation, not-found, conflict, and permission failures. - App-Level Handler Registration: Register exception handlers on the Litestar app config so exceptions bubble up and map cleanly to HTTP responses. - Consistent Response Shape: Control the wire format (detail, status_code, optional field-level errors) from one handler instead of per-route logic. - Use Case: A service layer raises NotFoundError when a task lookup fails; the registered handler automatically returns a 404 JSON response without any try/except in the route handler. ## Quick Start Ask the AI to design a Litestar exception hierarchy with an ApplicationError base class and register an app-level handler that maps domain exceptions to HTTP responses.
