domains / families / software-engineering / api-designer

api-designer

combined

Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards. Generates complete, production-ready REST API endpoint specifications for any system or domain the user describes.

When to use

• Output only the endpoints
• Output complete design as the structure described in this skill.

When not to use

• Use this skill only when the task clearly matches its upstream source and local project context.
• Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
• Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Skill page

Conflict

The two copies overlap in scope (REST API design) but prescribe different procedures and artifacts. Jeffallan/claude-skills is an architect workflow that mandates OpenAPI 3.1, resource modeling, linting with Redocly, mocking with Prism, and RFC 7807 error schemas. sickn33/agentic-awesome-skills is a generation skill that asks the user to choose between endpoints-only or detailed design, then outputs a fixed Markdown/JSON endpoint template with a page/limit pagination envelope and /api/v1/ versioning. They disagree on output format (OpenAPI spec vs Markdown endpoint tables), pagination (cursor vs page/limit), and versioning (strategy vs /api/v1/ prefix), so crowning one would hide a real alternative.