prototype-handoff

Package approved HTML/CSS/JS prototypes into stack-agnostic handoff bundles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents confusing handoffs by turning an explicitly approved prototype plus the final token snapshot into a single, stack-agnostic bundle that downstream developers can trust.

Core Features & Use Cases

  • Approved-prototype packaging: Builds a ready-for-development handoff bundle under .supervibe/artifacts/prototypes/<slug>/handoff/ using only verbatim, approved prototype files.
  • Evidence carry-forward: Includes component inventory, token inventory, viewport specification, and (for data-fed prototypes) mock and backend-integration evidence.
  • Fail-closed safety gates: Stops when approval, final tokens, inventory, contract evidence, confidence rubric thresholds, or Anti-AI-Slop evidence are missing.

Quick Start

Ask your AI tool to run the prototype handoff for the currently approved prototype in your project so it generates the stack-agnostic bundle and verification artifacts.

Frequently Asked Questions about prototype-handoff

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

FAQPage Schema
How do I package an approved HTML CSS JS prototype for developer handoff?

A stack-agnostic development handoff bundle packages verbatim approved native HTML, CSS, and JS prototype sources alongside final design-system tokens, component inventory, and viewport specifications into a single directory for downstream developers.

What is included in a stack-agnostic prototype handoff bundle?

A stack-agnostic prototype handoff bundle includes verbatim approved prototype sources, final design-system token snapshots, component inventory, viewport specifications, and optional mock or backend contract evidence for data-fed prototypes.

How do I prepare mock data and backend contract evidence for a prototype handoff?

Prepare mock data and backend contract evidence for prototype handoff by validating integration artifacts during the packaging process. The Skill applies fail-closed safety gates that stop generation if required contract evidence is missing for data-fed prototypes.

Why does my prototype handoff bundle fail to generate missing approval status?

Your prototype handoff bundle fails because the packaging process enforces fail-closed safety gates. It stops generation immediately when explicit approval status, final design tokens, inventory completeness, confidence rubric thresholds, or Anti-AI-Slop evidence are missing.

Can I use a prototype handoff bundle with any tech stack?

You can use a prototype handoff bundle with any tech stack because it is stack-agnostic. It isolates verbatim native HTML, CSS, and JS sources with final token snapshots, allowing downstream developers to implement them in their chosen framework.