context-api-contracts

Type mismatches occur when frontend and backend API definitions diverge. This Skill ensures consistency across TypeScript contracts, request/response types, and database schemas, preventing runtime errors by aligning data flow definitions across your stack before integration.

When adding endpoints, verify the route definition, request/response type contracts, TypeScript definitions on both sides, middleware alignment (auth, CORS), and client integration. This Skill maps your full API surface and contract dependencies to catch misalignments early.

404 errors signal route definition gaps or client misconfiguration. This Skill provides immediate context on backend API route definitions, endpoint versions, client implementations, and middleware setup to identify whether the issue is missing routes, incorrect paths, or integration problems.

Yes. This Skill navigates backend API routes across versions (v1, v2) and frontend clients, exposing the full API surface and design patterns. You can explore how contracts evolve and maintain consistency across service versions.

API contracts define what data flows; middleware enforces it (authentication, CORS); tests validate it. This Skill locates contract definitions, middleware configurations, and integration/E2E tests together, showing how each layer ensures API consistency and correctness.

This Skill works within a single codebase. It's designed for monorepos or integrated projects where frontend TypeScript types, backend routes, and API clients are colocated or share type definitions, enabling cross-stack consistency checks.