What problem does it solve? Go services need consistent HTTP error responses, but ad-hoc error handling with fmt.Errorf bypasses status mapping and silently returns 500 for every failure. This Skill standardizes how domain and application error codes are declared, registered, and raised in a Go bounded context. ## Core Features & Use Cases - Typed Error Code Declaration: Declare constants as errors.ErrorCode in internal/<ctx>/errors/codes.go and register each one with an HTTP status via init() and errors.RegisterErrorCodes. - Startup Registration Wiring: Trigger init() through a mandatory anonymous import in module.go so the MapErrorToHTTP middleware resolves codes correctly. - Correct Error Raising: Raise failures with errors.NewBaseError instead of fmt.Errorf so the HTTP mapper can extract the code, and reuse core framework codes without re-declaring them. - Use Case: When adding a new transcoding context, define codes like CodeJobNotFound and CodeJobNotPending, map them to 404 and 409, and have every handler return the right status automatically. ## Quick Start Ask the AI to create the error codes file for a new Go bounded context, register each code with its HTTP status in init(), and add the blank import to module.go.