design-api
Design API contracts before implementation — endpoints, models, status codes (Daniel Okoye's workflow)
npx skills add majiayu000/claude-skill-registry --skill design-api-g-zenr-relay-api --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Design the API contract for: $ARGUMENTS Design BEFORE implementing. This produces a specification that /add-endpoint or /add-feature will implement. ## Step 1 — Requirements - What problem does this API solve? - Who are the consumers? (frontend, mobile, external integrators, automation) - What data flows in and out? - What error conditions exist? ## Step 2 — Endpoint Design For each endpoint, define: ```markdown ### `METHOD /api/<version>/<path>` **Summary:** <one-line description> **Auth:** Required / Public **Request Body:** ```json { "field": "type — description (constraints)" } ``` **Response 200:** ```json { "field": "type — description" } ``` **Error Responses:** | Status | Condition | Response | |--------|-----------|----------| | 401 | Missing/invalid API key | Uniform auth error message | | 404 | Resource not found | Error response model | | 422 | Validation error | Pydantic validation error | | 503 | External resource unavailable | Error response model | ``` ## Step 3 — Pydantic Models Define request/response schemas: ```python class FeatureRequest(BaseModel): field: type = Field(..., description="...", ge=0) class FeatureResponse(BaseModel): field: type ``` - Explicit ty
- Step 1 — Requirements
- Step 2 — Endpoint Design
- Step 3 — Pydantic Models
- Step 4 — Route Organization
- Step 5 — Auth & Security
- Step 6 — Backwards Compatibility
- Output
What does the design-api skill do?
Design API contracts before implementation — endpoints, models, status codes (Daniel Okoye's workflow)
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill design-api-g-zenr-relay-api --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.