API Contract Diff
Compare two API or schema revisions and surface behavioral breakage, migration steps, and compatibility risk.
Collection
Contracts, integrations, data flow, failure handling, and API correctness.
27 skills in this lane
Compare two API or schema revisions and surface behavioral breakage, migration steps, and compatibility risk.
Normalize tool input and output schemas so multi-agent tool calling becomes more reliable, typed, and retry-safe.
Sunset APIs with clear migration windows, explicit headers, and communication paths that reduce client breakage.
Create unified API entry points with routing, transformation, rate limiting, and security
Replace offset-heavy APIs with cursor pagination that scales cleanly and remains client-friendly.
Set up contract testing so API consumers and providers fail safely before incompatible releases ship.
Introduce safe API versioning with compatibility lanes, deprecation notices, and migration guidance.
Create backend-for-frontend services that optimize APIs for specific client needs
Structure applications with dependency rule that keeps frameworks, UI, and database as details
Implement Conflict-free Replicated Data Types for automatic conflict resolution in distributed systems
Implement Domain-Driven Design tactical patterns: aggregates, entities, value objects, and domain services
Implement patterns for maintaining data consistency across distributed systems and microservices
Design systems by modeling events, commands, and views to capture complete system behavior
Introduce outbox-driven cross-service communication with reliable publication and eventual consistency safeguards.
Design systems that maintain consistency through asynchronous propagation with conflict resolution
Compose multiple GraphQL services into a unified schema with seamless cross-service queries
Protect GraphQL services from expensive queries with depth, complexity, and resource-aware limits.
Build high-performance bidirectional streaming APIs with Protocol Buffers and HTTP/2
Design loosely-coupled applications with clear separation between business logic and infrastructure
Make mutation endpoints safely retryable with idempotency keys and conflict-aware persistence patterns.
Modernize session flows with rotating refresh tokens, revocation, and secure cookie handling.
Generate OpenAPI documentation from typed routes and schemas without drifting from implementation.
Isolate application core from external concerns through well-defined ports and pluggable adapters
Implement distributed rate limiting with token buckets, predictable headers, and production-safe behavior under load.
Implement saga orchestration patterns that coordinate distributed transactions with centralized control
Expose backend bottlenecks through Server-Timing instrumentation that separates compute, database, and remote call cost.
Harden webhook handlers with signature verification, replay prevention, and idempotency discipline.