Fixture Schema Sync Repair

The problem

Test suites pass locally but break in production because mocks, factories, and fixtures have drifted from the actual API schema. Manually keeping JSON samples, MSW handlers, and Storybook stories in sync with TypeScript types or OpenAPI specs is tedious and error-prone.

What it does

• Audits repository schemas, types, and validators against existing test fixtures and mocks.
• Identifies missing, renamed, or mismatched fields across the entire testing stack.
• Generates safe patches for stale JSON fixtures, test factories, and MSW handlers.
• Creates type-safe fixture helpers to prevent future contract drift.
• Updates README examples and documentation to match the canonical code contract.

Frameworks & tools

TypeScript, Zod, OpenAPI, GraphQL, MSW, Vitest, Jest, Cypress, Playwright, Storybook, and Prisma.

Why this beats prompting it yourself

Generic prompts often hallucinate field names or fail to trace the dependency chain from a database schema through to a frontend mock. This skill enforces a structured audit of every contract source in your repo to ensure patches are technically accurate and safe from production data leakage.

Use cases

• Syncing MSW handlers after a major GraphQL or REST API refactor.
• Repairing flaky Playwright tests caused by outdated JSON fixture files.
• Making test factories type-safe using satisfies or generated types.
• Cleaning production-like data out of test files before an open-source handoff.

Known limitations

This tool does not call live APIs or production databases. It cannot verify if a deployed backend matches the local schema, only if the local repo remains internally consistent.