What problem does it solve? Runtime mismatches between database schemas, GraphQL responses, and TypeScript types cause undefined or null field bugs in the UI that are often discovered only after merge. This Skill catches those contract drifts early by systematically validating the entire data flow from source to presentation layer. ## Core Features & Use Cases - Schema-to-Type Alignment: Checks that queries only select fields existing in the latest Supabase Database types and flags schema drift with a resync recommendation. - GraphQL Mapping Validation: Verifies mappers handle optional and null fields safely and produce output matching the domain types consumed by components. - Server Boundary & Cache Contract Review: Confirms data fetching stays on the server boundary with explicit cache strategies (revalidate/no-store) and request deduplication. - Error Contract Audit: Ensures early-return patterns, stable fallback data shapes, and no sensitive error leakage to the UI. - Use Case: Before merging a PR that changes a Supabase query, run this Skill to receive a pass/warning/fail report listing every contract mismatch per file with prioritized patch recommendations. ## Quick Start Validate the data contracts for the files changed in my current pull request and report any schema, mapping, or error handling mismatches.
