prototype

Create throwaway logic and UI prototypes for design decisions.

1|Updated May 20, 2025
One-click install
npx skills add https://github.com/vessux/dotfiles --skill prototype-vessux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/vessux/dotfiles/tree/main/umbel/skills/pocock/prototype
Command: npx skills add https://github.com/vessux/dotfiles --skill prototype-vessux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams validate design decisions quickly by producing throwaway prototypes that can explore both logic (state machines) and UI variations without risking production code.

Core Features & Use Cases

  • Two prototype branches: logic-focused prototypes for state machines and UI-focused variants that can be toggled from a route.
  • Contextual placement: prototype code lives near the target module with an explicit "prototype" mark and in-memory state only.
  • Decision documentation: capture outcomes in a NOTEs.md or ADR after exploration.

Quick Start

Run the prototype from the project using the existing task runner to open a throwaway route that exposes either a logic prototype or a UI variation.

Frequently Asked Questions about prototype

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

FAQPage Schema
How do I create throwaway prototypes to validate UI variations and state machine logic?

Throwaway prototypes validate design decisions by generating either a runnable logic prototype for state machines or multiple UI variants switchable from a single route, using in-memory state only.

What is the best way to explore UI variations without risking production code?

Use throwaway prototypes to explore UI variations without risking production code by placing prototype code near the target module with an explicit prototype label and in-memory state only.

Can I prototype a state machine and toggle between different UI variants from one route?

Yes, you can prototype a state machine and toggle UI variants because the skill supports two branches: logic-focused prototypes for state machines and UI-focused variants switchable from a single route.

How do I start a prototype using my existing project task runner?

Start a prototype by running it from your project using the existing task runner to open a throwaway route that exposes either a logic prototype or a UI variation for rapid feedback.

How should I document design decisions after exploring throwaway prototypes?

Document design decisions after exploring throwaway prototypes by capturing the exploration outcomes in a NOTEs.md file or an Architecture Decision Record (ADR) to finalize the validated design.

Are there limitations to using throwaway prototypes for design exploration?

A key limitation is that throwaway prototypes use in-memory state and explicit prototype labeling, meaning they are strictly for rapid feedback and design validation rather than production deployment.