aibdd.auto.ts.it.schema-analysis

Validate Zod schemas, API clients, and MSW handlers against api.yml contracts.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-auto-ts-it-schema-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aibdd.auto.ts.it.schema-analysis
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/aibdd.auto.ts.it.schema-analysis
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-auto-ts-it-schema-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend projects often suffer from schema drift between UI expectations and backend reality. This skill analyzes the API contract definitions (.feature, api.yml) and frontend typings to confirm Zod schemas, API client signatures, and MSW handlers align with intended behaviour.

Core Features & Use Cases

  • Schema alignment: Verify that Zod schemas under src/lib/types/ match api.yml definitions and API client typings under src/lib/api.
  • End-to-end consistency: Ensure MSW handlers under src/mocks/handlers (or src/test/mocks/handlers) cover defined endpoints and responses.
  • Automation path: If mismatches exist, delegate to /aibdd-auto-frontend-msw-api-layer to auto-generate missing layers and regenerate stubs.

Quick Start

Run the schema analysis on your React IT project to verify that Zod schemas, API clients, and MSW handlers match api.yml definitions.

Frequently Asked Questions about aibdd.auto.ts.it.schema-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent schema drift between my React frontend and backend API contracts?

To prevent schema drift, you need to validate frontend Zod schemas and API client functions against backend contract definitions. This schema analysis confirms your UI expectations match the backend reality defined in api.yml.

How do I validate Zod schemas against api.yml definitions in a React project?

You validate Zod schemas by analyzing API contract definitions in api.yml and comparing them against frontend typings under src/lib/types. This verifies Zod schemas and API client signatures under src/lib/api align with intended backend behavior.

How do I ensure MSW handlers cover all endpoints defined in my api.yml?

To ensure MSW handlers cover defined endpoints, analyze handlers under src/mocks/handlers against your api.yml. This verifies end-to-end consistency by confirming mock responses and endpoints match the backend contract definitions.

Does this schema analysis work with tests driven by .feature files?

Yes, this schema analysis works across .feature and api.yml driven workflows. It validates Zod schemas, API client signatures, and MSW handlers align with API contracts defined within those testing and specification formats.

What happens when mismatches are found between Zod schemas and api.yml?

When mismatches are found between Zod schemas and api.yml, the analysis delegates to aibdd-auto-frontend-msw-api-layer to auto-generate missing layers. This automation path regenerates necessary stubs and applies automated fixes to restore alignment.