What problem does it solve? Go APIs documented with swag often drift out of sync with the code: missing @Param entries, stale generated docs, unsecured endpoints lacking @Security, and general info silently dropped because it lives in the wrong file. This Skill enforces a complete annotation contract so the Swagger UI always matches the actual handlers. ## Core Features & Use Cases - Annotation authoring: Step-by-step guidance for @Summary, @Param, @Success, @Router, and @Security on every handler, plus general API info and security definitions in main.go. - Generation workflow: Covers swag init, swag fmt, framework wiring for Gin, Echo, Fiber, and net/http, and regenerating docs/ after every change. - Audit checklist: Verifies param kinds, response object types, security coverage, and that committed swagger.json matches the current code. - Use Case: You add a new endpoint to a Gin service and need the Swagger UI to show its parameters, responses, and Bearer auth requirement without breaking existing docs. ## Quick Start Annotate my Go handlers with swag comments and generate the Swagger docs for this API.