Design REST and GraphQL APIs with OpenAPI 3.1 specifications.
npx skills add https://github.com/grasberg/sofia --skill api-designer-grasberg
Please help me install this Agent Skill. Skill: api-designer Source: https://github.com/grasberg/sofia/tree/main/workspace/skills/api-designer Command: npx skills add https://github.com/grasberg/sofia --skill api-designer-grasberg
Inconsistent API design and fragmented developer experience slow down integrations; this Skill provides a guided approach to REST and GraphQL design with clear patterns, open standards, and maintainable schemas.
Create a starter API design brief applying REST and GraphQL patterns to define endpoints, schemas, and auth strategy.
High-intent search queries and answers about installing and using this skill.
Designing a REST API with OpenAPI 3.1 involves defining consistent URL structures, HTTP methods, and standardized RFC 7807 error formatting. This approach ensures maintainable schemas, clear endpoint conventions, and robust versioning for backward compatibility.
Structuring GraphQL schemas requires defining proper types, relationships, and pagination. Applying federation considerations during GraphQL design ensures scalable query handling and consistent data fetching patterns across distributed services.
RFC 7807 standardizes API error handling by defining a consistent problem details format for HTTP APIs. Applying this format in REST API design provides developers with predictable, machine-readable error responses across all endpoints.
Yes, you can implement OAuth 2.0, API keys, and JWT for API authentication. Applying these multiple auth schemes within OpenAPI specifications secures endpoints while maintaining flexible authorization patterns for different client access levels.
Improving API developer experience requires generating comprehensive documentation, practical examples, and getting-started guides. Applying OpenAPI standards ensures the documentation remains synchronized with the schema, accelerating client integrations.
Apply REST for standardized resource manipulation using OpenAPI 3.1, and choose GraphQL for flexible data fetching with nested relationships. Both approaches support distinct pagination, authentication, and versioning strategies tailored to specific data requirements.
myrtlepnDesign database schemas, ERDs, and migration plans for software features.
AI-Foundry-CoreGenerate OpenAPI 3.1 specifications from code and design artifacts.
camilooscargbaptistaDesign API gateway architectures with rate limiting, authentication, routing, and circuit breaking.
aexol-studioGenerate type-safe GraphQL models and resolver boilerplates from a schema.
