pocock-prototype

Build throwaway prototypes that answer design questions about logic, state models, or UI layouts.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill pocock-prototype-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pocock-prototype
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/ai/shared/skills/mattpocock/pocock-prototype
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill pocock-prototype-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state machines, data models, or page layouts are hard to settle on paper. This Skill produces throwaway, runnable prototypes — an interactive terminal app for logic questions or multiple switchable UI variants for visual questions — so you can validate an idea before committing real code. ## Core Features & Use Cases - Logic prototypes: Build a lightweight TUI that drives a pure reducer, state machine, or function set through edge cases, re-rendering full state after every keystroke. - UI prototypes: Generate 3-5 structurally different variants of a page on one route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key navigation. - Capture workflow: Fold validated decisions into real code and preserve the prototype on a throwaway branch as a primary source, keeping main clean. - Use Case: You're unsure whether a state machine handles an edge case like "cancel during pending payment". The Skill builds a small terminal app where you press keys to push the machine through that exact sequence and watch the state change. ## Quick Start Ask the AI to build a throwaway prototype that tests whether your state model handles a specific edge case, or to generate three UI variants of a page switchable via a URL parameter.

Frequently Asked Questions about pocock-prototype

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

FAQPage Schema
How do I prototype a state machine before writing production code?

Build a small interactive terminal app around a pure reducer or state machine. Each keystroke dispatches an action, and the full state re-renders after every tick, letting you push the model through edge cases by hand.

How to compare multiple UI design variants on one page?

Render structurally different variants on the same route gated by a ?variant= URL search param, with a floating bottom bar to cycle between them. Keep existing data fetching intact and only swap the rendered subtree.

Should a prototype include tests and error handling?

No. A prototype that needs tests is no longer a prototype. Skip tests, persistence, and polish; the goal is to answer one design question fast, then rewrite the validated decision properly in real code.

When should I use a logic prototype versus a UI prototype?

Use a logic prototype when the question is whether a state model or data shape feels right under real cases. Use a UI prototype when the question is what a page or component should look like.

What happens to prototype code after the question is answered?

Fold the validated decision into the real module, then commit the full prototype to a throwaway branch outside main as a primary source. Leave a pointer to that branch on the implementation issue.