More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Fixture Schema Sync Repair

    1

    Repair stale test fixtures and mocks in a repo using Cursor.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Fixture Schema Sync Repair

    Fixture Schema Sync Repair

    Example session with this skill installed

    My Cypress fixtures are stale after renaming the user profile fields in our Zod schema. Sync the fixtures and MSW handlers without using real data.

    • Read your context and instructions
    • Compiled the fixture schema sync

    1. Fixture Sync Decision

    Decision: FIXTURE SCHEMA DRIFT FOUND
    The Zod schema in src/schemas/user.ts now uses fullName, but cypress/fixtures/user.json and src/mocks/handlers.ts still use displayName. Safe patches prepared.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    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.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Operates only on repository files. Does not call live APIs or production databases. Cannot verify backward compatibility of deployed services.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    Software
    tscNode.js

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Permissions are limited to the active local workspace and are used to inspect user-supplied or local workspace files; create or modify bounded local fixes, tests, documentation, or review artifacts; run repository-supported local tests, checks, builds, or parsing commands. The skill package does not require bundled credentials, unrestricted external network access, or automatic production changes.

    Listed3 months ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill is specifically optimized for use within the Cursor code editor. It leverages Cursor's indexing capabilities to accurately map the relationships between your source schemas and your distributed test mocks.

    The skill analyzes your 'canonical' sources (like OpenAPI specs, Zod schemas, or Prisma models) and cross-references them with your JSON fixtures, MSW handlers, and test factories to identify and fix structural drift.

    Setup is minimal: simply add the skill to your Cursor environment and point it at your schema definitions. It is designed to work out-of-the-box with standard TypeScript and JavaScript project structures.

    No, this tool operates strictly on local repository files to ensure internal consistency. It does not require access to live production environments or external API endpoints to perform its repairs.

    You receive the specialized skill instructions optimized for Cursor, along with a guide on best practices for automating your schema-to-mock workflow across different testing frameworks.

    While it supports any JSON or JS-based mocking, it is most effective with TypeScript-heavy stacks using tools like Zod, GraphQL, MSW, and Vitest where it can enforce type-safety.

    New in Agents & Orchestration