plugins/pokayokay/skills/api-design/SKILL.md
Use when designing new REST APIs, reviewing API designs, establishing API standards, designing request/response formats, pagination, versioning, authentication flows, or creating OpenAPI specifications.
npx skillsauth add srstomp/pokayokay api-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design clear, consistent, and developer-friendly REST APIs.
api-integration for building clients to call third-party services (Stripe, Twilio, etc.)testing-strategy for contract tests, integration tests, mocking strategiessecurity-audit for vulnerability scanning of live endpointssecurity-audit if reviewing, this skill if designing from scratch| Method | Purpose | Idempotent | Body | |--------|---------|------------|------| | GET | Read | Yes | No | | POST | Create | No | Yes | | PUT | Replace | Yes | Yes | | PATCH | Partial update | Yes* | Yes | | DELETE | Remove | Yes | No |
| Reference | Description | |-----------|-------------| | endpoints.md | URL design, HTTP methods, resource modeling | | requests-responses.md | Request/response formats, headers, content types | | status-codes.md | HTTP status codes, error handling patterns | | pagination-filtering.md | Pagination, filtering, sorting, searching | | versioning.md | API versioning strategies | | openapi.md | OpenAPI specification, documentation | | security.md | Authentication, authorization, rate limiting | | tdd-patterns.md | Test-first patterns for REST endpoints, supertest templates | | review-checklist.md | API design review checklist (validation, auth, performance, docs) |
development
Git worktree management for isolated task development
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
testing
Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.
development
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.