mock-data-contract

Generate schema-tied mock data contracts and scenario fixtures for frontend handoffs.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill mock-data-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mock-data-contract
Source: https://github.com/vTRKA/supervibe/tree/main/skills/mock-data-contract
Command: npx skills add https://github.com/vTRKA/supervibe --skill mock-data-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents frontend-before-backend handoffs from drifting by turning informal mock JSON into a schema- or data-model-aligned, scenario-complete contract with explicit evidence and blockers.

Core Features & Use Cases

  • Creates mock-contract artifacts: generates a concrete mock-contract bundle (contract status, schema references, endpoints/entities, PII policy, and drift rules) suitable for handoff workflows.
  • Builds scenario fixtures: produces mock-scenarios plus one synthetic JSON fixture per scenario to cover loading, empty, error, permission, validation, partial, pagination, and large-list states.
  • Supports frontend-before-backend: uses provisional contracts with explicit backend questions when no API/schema exists, and blocks completion when required proof is missing.

Quick Start

Tell your AI tool: create mock data contract fixtures for your data-fed prototype handoff, covering all specified UI states and returning blockers if schema, approval, or receipts are missing.

Frequently Asked Questions about mock-data-contract

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

FAQPage Schema
How do I create mock data contracts for frontend handoff before the backend API is ready?

Mock data contracts are generated by reading your prototype spec, selecting a contract status, and producing a schema-tied mock-contract.json with endpoints, entities, and drift rules. This ensures your frontend handoff has durable, scenario-complete data fixtures before backend availability.

What is the best way to cover all UI states with scenario fixtures during a prototype-to-handoff workflow?

Scenario fixtures cover UI states by generating a mock-scenarios.json file plus individual synthetic JSON fixtures for each case. These fixtures explicitly handle loading, empty, error, permission, validation, partial, pagination, and large-list states to prevent frontend drift.

How does PII safety work when generating synthetic JSON fixtures for data-fed prototypes?

PII safety is enforced during mock data contract generation by applying a strict PII policy within the mock-contract.json artifact. This ensures all synthetic JSON fixtures and scenario data used for frontend handoffs contain no real personally identifiable information.

Can I use a provisional contract if no API schema exists for my frontend prototype?

Provisional contracts are supported when no API or schema exists, allowing you to generate mock data with explicit backend questions attached. The Skill blocks completion and emits blockers if required proof, schema approval, or receipts are missing.

Why do my frontend handoffs drift when using informal mock JSON instead of a schema-aligned contract?

Frontend handoffs drift because informal mock JSON lacks schema ties, scenario completeness, and drift rules. Generating a bounded mock data contract with explicit evidence, confidence levels, and blockers prevents this misalignment between the prototype and the final API.