api-design

Define framework-agnostic GraphQL schema and operation design principles.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AlexDevFlow/Claude10XD --skill api-design-alexdevflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design
Source: https://github.com/AlexDevFlow/Claude10XD/tree/main/skills/api-design
Command: npx skills add https://github.com/AlexDevFlow/Claude10XD --skill api-design-alexdevflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GraphQL API design is complex and error-prone without a clear contract; this skill provides framework-agnostic guidance to design scalable schemas, consistent operation patterns, and maintainable backends.

Core Features & Use Cases

  • Schema design best practices for type safety, nullability, pagination, and error modeling.
  • Patterns for queries, mutations, subscriptions, and their evolution across versions.
  • Compatibility guidance for major GraphQL servers and clients (Apollo, Hasura, Relay, urql) and Rust backends.
  • Use cases include building a new GraphQL API, reviewing existing schemas, and guiding schema evolution.

Quick Start

Describe a new GraphQL API design plan for a project including schema structure, pagination strategy, and error handling guidelines.

Frequently Asked Questions about api-design

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

FAQPage Schema
How do I design a GraphQL schema with proper pagination and error handling?

GraphQL schema design requires framework-agnostic principles for type safety, nullability, and structured error modeling. This skill provides standardized patterns to define scalable schemas, consistent operation structures, and clear pagination strategies for robust API backends.

Does this GraphQL API design guidance work with Apollo, Hasura, and Relay?

Yes, this GraphQL API design guidance applies across major servers and clients including Apollo, GraphQL Yoga, Hasura, Relay, and urql. It provides compatibility guidance and standardized patterns for schema evolution, operation patterns, and backend practices across these platforms.

What's the best way to structure mutations and subscriptions in a GraphQL API?

The best way to structure GraphQL mutations and subscriptions is through standardized operation patterns that support schema evolution. This skill defines framework-agnostic patterns for queries, mutations, and subscriptions to ensure maintainable and consistent API operations.

Can I use these GraphQL API design patterns for a Rust backend?

Yes, these GraphQL API design principles include specific compatibility guidance and standardized patterns for Rust backends. The skill specifies modular sub-skills and Rust practices to help you build robust schemas and clear operation patterns in Rust environments.

When should I evolve my GraphQL schema versus creating a new version?

GraphQL schema evolution should be guided by framework-agnostic design principles that maintain type safety and backward compatibility. This skill provides patterns for evolving schemas across versions, ensuring consistent operation structures and clear error modeling during transitions.