http-status-codes

Use when choosing, reviewing, correcting, or explaining HTTP response codes for APIs, OpenAPI specs, controllers, middleware, SDK/client retry logic, or error handling. Make sure to use this skill whenever a task touches status-code semantics, especially 400 vs 422, 401 vs 403, 404 vs 410, 405 vs 501, 409 vs 412 vs 428, 429 vs 503, 201 vs 202 vs 204, or redirect behavior like 303 vs 307 vs 308.