Agent skill · Backend & API

designing-apis

Design APIs that are secure, scalable, and maintainable using RESTful, GraphQL, and event-driven patterns. Use when designing new APIs, evolving existing APIs, or establishing API standards for teams.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill designing-apis-ancoleman-ai-design-components --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/api/designing-apis-ancoleman-ai-design-components/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Designing APIs Design well-structured, scalable APIs using REST, GraphQL, or event-driven patterns. Focus on resource design, versioning, error handling, pagination, rate limiting, and security. ## When to Use This Skill Use when: - Designing a new REST, GraphQL, or event-driven API - Establishing API design standards for a team or organization - Choosing between REST, GraphQL, WebSockets, or message queues - Planning API versioning and breaking change management - Defining error response formats and HTTP status code usage - Implementing pagination, filtering, and rate limiting patterns - Designing OAuth2 flows or API key authentication - Creating OpenAPI or AsyncAPI specifications Do NOT use for: - Implementation code (use `api-patterns` skill for Express, FastAPI code) - Authentication implementation (use `auth-security` skill for JWT, sessions) - API testing strategies (use `testing-strategies` skill) - API deployment and infrastructure (use `deploying-applications` skill) ## Core Design Principles ### Resource-Oriented Design (REST) Use nouns for resources, not verbs in URLs: ``` ✓ GET /users List users ✓ GET /users/123 Get user 123 ✓ POST /users Create user ✓ PATCH /users/12

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Core Design Principles
  3. Resource-Oriented Design (REST)
  4. HTTP Method Semantics
  5. HTTP Status Codes
  6. API Style Selection
  7. Decision Matrix
  8. Quick Selection
  9. API Versioning
  10. URL Path Versioning (Recommended)
  11. Alternative Strategies
  12. Breaking Change Management
  13. Error Response Standards
  14. RFC 7807 Problem Details (Recommended)
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the designing-apis skill do?

Design APIs that are secure, scalable, and maintainable using RESTful, GraphQL, and event-driven patterns. Use when designing new APIs, evolving existing APIs, or establishing API standards for teams.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill designing-apis-ancoleman-ai-design-components --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.

Keep going