From supervibe
Use WHEN a prototype, frontend handoff, or backend integration needs realistic mock data TO create schema-tied mock contracts and scenario fixtures before frontend implementation. Triggers: 'mock data contract', 'prepare mocks', 'data-fed prototype', 'frontend before backend'.
npx claudepluginhub vtrka/supervibe --plugin supervibeThis skill is limited to using the following tools:
Create a contract-backed mock data bundle for data-fed prototypes and frontend-before-backend work. The output makes mock data useful for design, frontend implementation, API design, and backend integration without pretending local JSON is the backend.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Create a contract-backed mock data bundle for data-fed prototypes and frontend-before-backend work. The output makes mock data useful for design, frontend implementation, API design, and backend integration without pretending local JSON is the backend.
data-fed./supervibe-design reaches prototype or handoff with fake API responses.Do not invoke for purely visual prototypes, static marketing pages with no API state, or production seed data.
Follow docs/references/skill-expert-operating-standard.md: start from source
of truth, preserve retrieval evidence, apply scope safety, use real producers
with runtime receipts for durable delegated outputs, verify before completion
claims, and keep confidence below gate when evidence is partial.
Before writing fixtures, read the relevant available files:
.supervibe/artifacts/prototypes/<slug>/config.json.supervibe/artifacts/prototypes/<slug>/spec.md.supervibe/artifacts/prototypes/<slug>/content/copy.md.supervibe/artifacts/prototypes/<slug>/mocks/ if it already exists.supervibe/artifacts/prototypes/<slug>/.approval.json when handoff is requestedopenapi.yaml, openapi.json, schema.graphql, *.proto, or asyncapi.yamlIf no API/schema/data-model source exists, create a provisional contract with explicit backend questions. Do not mark it schema-backed.
Is interaction data-fed?
no -> stop; no mock-data contract needed.
yes -> continue.
Does an API/schema contract exist?
yes -> derive mock-contract.json schemaRefs from it.
no -> check data model / spec / API designer notes.
Only product/spec shape exists?
-> create contractStatus="provisional" and list backendQuestions.
Does the spec name states?
yes -> cover every named state in mock-scenarios.json.
no -> require baseline states: success, loading, slow, empty, error, permission, validation, partial, large-list where relevant.
Does any fixture include real PII, secrets, or production export data?
yes -> replace with synthetic values before handoff.
no -> continue.
Is handoff being produced?
yes -> copy mocks into handoff/mocks/ and add backend-integration.md.
no -> keep mocks under prototype root and record readiness state.
<slug> and target prototype root.contractStatus: api-backed, schema-backed, data-model-backed, or provisional..supervibe/artifacts/prototypes/<slug>/mocks/ if absent..supervibe/artifacts/prototypes/<slug>/mocks/mock-contract.json from templates/mock-data/mock-contract.json.tpl..supervibe/artifacts/prototypes/<slug>/mocks/mock-scenarios.json from templates/mock-data/mock-scenarios.json.tpl..supervibe/artifacts/prototypes/<slug>/mocks/api-fixtures/..supervibe/artifacts/prototypes/<slug>/mocks/README.md with data ownership, PII policy, backend questions, and replacement steps..supervibe/artifacts/prototypes/<slug>/handoff/mocks/ and write handoff/backend-integration.md from templates/mock-data/backend-integration.md.tpl.supervibe:confidence-scoring.Returns:
=== Mock Data Contract ===
Slug: <slug>
Contract: .supervibe/artifacts/prototypes/<slug>/mocks/mock-contract.json
Scenarios: .supervibe/artifacts/prototypes/<slug>/mocks/mock-scenarios.json
Fixtures: .supervibe/artifacts/prototypes/<slug>/mocks/api-fixtures/
Handoff copy: <pending | .supervibe/artifacts/prototypes/<slug>/handoff/mocks/>
Backend notes: <pending | .supervibe/artifacts/prototypes/<slug>/handoff/backend-integration.md>
Status: <api-backed | schema-backed | data-model-backed | provisional>
Confidence: <N>.<dd>/10
Override: <true|false>
Rubric: agent-delivery
mock-contract.json, mock-scenarios.json, api-fixtures/, and backend integration notes.This skill's output is verified by:
mock-contract.json includes contractStatus, owner, schemaRefs, endpoints, entities, piiPolicy, and driftRulemock-scenarios.json includes scenario ids for success and every applicable non-happy-path stateapi-fixtures/ includes one fixture file per scenario idbackend-integration.md exists in handoff for approved data-fed prototypessupervibe:_ops:mock-data-designer - specialist agent for producing this bundlesupervibe:_ops:api-designer - API contract ownersupervibe:_ops:data-modeler - data-model ownersupervibe:prototype - data-fed prototype consumersupervibe:prototype-handoff - packages mock data for stack developersrules/mock-data-contract.md - rule-level gate for frontend-before-backend workflows