This skill should be used when the user needs to "design the API", do "endpoint design", pin down a "request/response shape", choose a "pagination" strategy (cursor vs offset), add an "idempotency key" to a write, plan "API versioning", an "error contract", or pick between "REST vs gRPC vs GraphQL" or "WebSocket vs polling". Use it whenever a design has reached the interface — the concrete request, response, primary access path, and how clients page, retry, and version — even if the user only said "the boxes talk to each other".
$npx -y skills add proyecto26/system-design-skills --skill api-designInstalls into the current project.
Run `npx skills use "https://github.com/proyecto26/system-design-skills" --skill "proyecto26/system-design-skills/api-design"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/proyecto26/system-design-skills" that are relevant to the current task. Run `npx skills add "https://github.com/proyecto26/system-design-skills"` and select the relevant skills, then follow their instructions.