sdxc-http

What problem does it solve? Writing HTTP handlers by hand means memorizing status codes, hand-writing Cache-Control directives, and reimplementing ETag and conditional-request logic for every endpoint. This Skill documents the @sdxc/http package, which provides status-named response builders, Accept-header content negotiation, and a complete HTTP caching layer so handlers return correct responses with minimal boilerplate. ## Core Features & Use Cases - Status-named response builders: Functions like ok, badRequest, and notFound write JSON or HTML bodies with the right status and content type, so each handler outcome reads as the status it answers with. - Content negotiation: accepts, AcceptList, and respond parse the Accept header and dispatch to the right format handler, answering 406 when nothing matches. - HTTP caching layer: policy/Policies build Cache-Control values from intent, while etag, conditional, precondition, and vary handle 304 revalidation, If-Match writes, and cache variance. - Use Case: A route serving JSON, HTML, and CSV from one URL uses respond for negotiation, vary to keep shared caches correct, and conditional so repeat GET requests answer 304 instead of resending the body. ## Quick Start Add @sdxc/http as a workspace dependency and use the sdxc-http skill to write a handler that returns status-named JSON responses with proper cache headers.