Stats
Actions
Tags
From dotclaudefiles
Esta skill debe usarse cuando el usuario pide "documenta los endpoints", "documenta la API", "documentar las rutas", "document the endpoints", "document the API", "necesito la doc de los endpoints para el frontend", o cuando menciona documentar endpoints HTTP para consumo desde el frontend. Tambien activar cuando el usuario menciona pasar endpoints al frontend, compartir contratos HTTP, o preparar documentacion de rutas REST. No usar para WebSockets ni socket.io (usar document-sockets en su lugar).
How this skill is triggered — by the user, by Claude, or both
Slash command
/dotclaudefiles:document-endpointsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Determine scope from conversation context -- identify which routes/controllers were created or modified. If the user names specific resources, limit to those. If ambiguous, use `AskUserQuestion` to confirm which endpoints to document.
AskUserQuestion to confirm which endpoints to document.auth, payments). If unclear, ask with AskUserQuestion..claude/docs/api/ directory if it does not exist..claude/docs/api/<prefix>-ENDPOINTS.md.references/endpoint-template.md for every endpoint.npx claudepluginhub diegopherlt/dotclaudefiles --plugin dotclaudefilesGenerates API documentation for endpoints including HTTP methods, parameters, request bodies, responses, error codes, and curl examples. Outputs Markdown or OpenAPI/Swagger.
Generates API documentation from codebases, including endpoints, parameters, examples, auth, errors, and OpenAPI specs for REST, GraphQL, and WebSocket APIs. Use for new APIs, updates, or onboarding.
Transforms raw API specs, endpoint descriptions, or Postman collections into clean developer-facing documentation with endpoint summaries, parameters, request/response examples, and error codes.