API Design & Integration

Use this skill for REST, GraphQL, and third-party integrations when you need stable contracts and operable behavior.

Priorities

1. Clear contract
2. Backward compatibility
3. Validation and safety
4. Observability
5. Performance

Contract Rules

1. Design the contract before the handler

• Start from the consumer-facing shape: paths, fields, mutations, errors, pagination, auth, and compatibility rules.
• If the repo uses OpenAPI, schema files, generated clients, or GraphQL SDL, update the contract source first.
• Keep the contract smaller than the implementation would naturally drift toward.