Stats
Actions
Tags
From dotclaudefiles
Esta skill debe usarse cuando el usuario pide "documenta los sockets", "documenta los eventos", "documentar websockets", "document the sockets", "document socket events", "necesito la doc de los sockets para el frontend", o cuando menciona documentar eventos de socket.io para consumo desde el frontend. Tambien activar cuando el usuario menciona pasar eventos al frontend, compartir contratos de sockets, o preparar documentacion de eventos en tiempo real. No usar para endpoints HTTP REST (usar document-endpoints en su lugar).
How this skill is triggered — by the user, by Claude, or both
Slash command
/dotclaudefiles:document-socketsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Determine scope from conversation context -- identify which socket handlers/gateways were created or modified. If the user names specific events or namespaces, limit to those. If ambiguous, use `AskUserQuestion` to confirm which events to document.
AskUserQuestion to confirm which events to document.chat, notifications). If unclear, ask with AskUserQuestion..claude/docs/api/ directory if it does not exist..claude/docs/api/<prefix>-SOCKETS.md.references/socket-template.md for every event.npx claudepluginhub diegopherlt/dotclaudefiles --plugin dotclaudefilesGenerates API documentation from code, covering endpoints, parameters, request/response examples, authentication, error handling, and usage guidelines. Supports REST, GraphQL, and WebSocket APIs.
Generates API docs from code or OpenAPI specs with examples, schemas, interactive Swagger UI/Redoc, and exports to Markdown, PDF, Postman, SDKs.
Generates interactive API docs from OpenAPI specs with runnable examples in curl/JS/Python/Go, auth guides, error references, versioning, and deployment-ready sites.