What problem does it solve? Writing HTTP handlers in a clean-architecture Go codebase often leads to inconsistent patterns: business logic leaking into handlers, ad-hoc error responses, and wrong status codes. This Skill enforces a single authoritative style for Gin handlers in internal/infrastructure/api/*_api.go so every endpoint parses input, calls a usecase, and shapes responses the same way. ## Core Features & Use Cases - Handler scaffolding: Generates a complete *_api.go file with a narrow usecase interface declared in-file, a handler struct, and a New{Feature}V2Handlers constructor that registers all routes under a /v2/{feature} group. - Convention enforcement: Applies strict rules for input parsing (uuid path params, optional query params guarded on empty string, JSON bound directly into domain types), error handling via HandleErr, and status-code selection (201 for creation, 200 for returned resources, 204 for no body). - Use Case: When adding a new endpoint like POST /v2/widgets/:id/pay, the Skill produces a handler closure that parses the path param and optional date query param, delegates to the usecase, and returns the mapped output with the correct status code. ## Quick Start Ask the AI to add a new Gin endpoint to an existing feature API file following the go-api-handlers conventions.
