What problem does it solve? Building interactive web UIs with HTMX inside a Litestar application requires correctly wiring HTMXPlugin, returning partial HTML instead of full pages, and managing server-driven response headers like HX-Trigger and HX-Push-Url, which is error-prone without guidance. ## Core Features & Use Cases - HTMXRequest integration: Detect HTMX requests via headers and branch between full-page and partial responses using request.htmx properties. - Server-driven responses: Use TriggerEvent, PushUrl, Reswap, Retarget, HXLocation, and ClientRefresh to control client behavior from Python handlers. - Partial templates and OOB swaps: Render Jinja2 fragments and out-of-band updates, with optional client-side JSON templating via the hx-ext="litestar" extension. - Use Case: Build an items page where a form posts via hx-post, the server returns a TriggerEvent, and the item list refreshes automatically with an OOB notification update. ## Quick Start Ask the AI to create a Litestar app with HTMXPlugin registered and an HTMX-driven items page that returns Jinja partials and triggers a client event on create.