api-design-principles

Provide design principles and architectural patterns for REST and GraphQL API development.

7|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Cobalt-Money/Cobalt --skill api-design-principles-cobalt-money
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design-principles
Source: https://github.com/Cobalt-Money/Cobalt/tree/main/.agents/skills/api-design-principles
Command: npx skills add https://github.com/Cobalt-Money/Cobalt --skill api-design-principles-cobalt-money

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexity of designing robust API architectures by providing standardized patterns for REST and GraphQL, preventing common pitfalls like over-fetching, inconsistent error handling, and poor versioning.

Core Features & Use Cases

  • REST & GraphQL Standards: Provides clear guidelines for resource-oriented architecture, schema-first development, and N+1 problem prevention.
  • Best Practice Templates: Includes production-ready templates for FastAPI and GraphQL schema design to ensure consistency across team projects.
  • Use Case: Use this Skill when you are architecting a new microservice, performing a code review on an API specification, or refactoring an existing endpoint to improve developer experience and performance.

Quick Start

Ask the api-design-principles skill to review your current API schema and suggest improvements based on the provided design patterns.

Frequently Asked Questions about api-design-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for REST and GraphQL API design to prevent over-fetching and inconsistent errors?

API design principles provide standardized patterns for REST and GraphQL architectures, preventing over-fetching and inconsistent error handling through resource-oriented guidelines and schema-first development.

How do I structure a scalable FastAPI schema and endpoints for a new microservice?

Structure scalable FastAPI schemas using production-ready templates that enforce resource-oriented architecture, schema-first development, and consistent endpoint structuring for maintainable microservice interfaces.

When do I need to use GraphQL schema-first development instead of standard REST?

GraphQL schema-first development is needed when your API requires precise data fetching to prevent the N+1 problem, contrasting with standard REST resource-oriented architectures for different scaling requirements.

How do I review an existing API specification to improve developer experience and performance?

Review existing API specifications by evaluating them against architectural patterns and design templates for REST and GraphQL, identifying areas to improve developer experience, versioning, and performance optimization.

Can I use these API design patterns to refactor endpoints and fix poor versioning?

Yes, you can use these API design patterns to refactor endpoints and fix poor versioning by applying standardized architectural templates that ensure consistency and improve maintainability across team projects.

What is the best way to handle API error handling and prevent the N+1 problem in GraphQL?

The best way to handle API errors and prevent the GraphQL N+1 problem involves applying standardized architectural patterns that enforce schema-first development and consistent error handling strategies.