prototype

Build throwaway terminal or UI prototypes to validate logic and design decisions.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill prototype-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/core/prototype
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill prototype-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state machines, data models, or UI layouts are hard to answer on paper. This Skill produces throwaway, runnable prototypes that let you press buttons, flip between variants, and discover flaws in an idea before committing to real implementation. ## Core Features & Use Cases - Logic prototypes: Build a small interactive terminal app with a pure reducer, state machine, or function set behind a thin TUI shell, so you can drive state transitions by hand and spot edge cases. - UI prototypes: Generate 3-5 structurally different UI variants on one route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key cycling. - Use Case: You are unsure whether a state machine handles an edge case where event X fires before event Y. The Skill builds a one-command terminal app that renders current state and keyboard shortcuts, letting you replay the sequence and capture the answer in a NOTES.md before deleting the prototype. ## Quick Start Ask the agent to prototype the state machine or page design you are unsure about so you can interact with it and validate the idea before writing production code.

Frequently Asked Questions about 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 terminal app where a pure reducer or state machine holds the logic and a thin TUI shell renders current state plus keyboard shortcuts. Drive it by hand through edge cases, then lift the validated logic module into the real codebase and delete the shell.

How to create multiple UI design variations on one page?

Render 3-5 structurally different variant components on the same route, gated by a ?variant= URL search param. Add a floating bottom bar with arrows that cycles variants via the framework router, keeping existing data fetching intact.

Should a prototype connect to a real database?

No. Prototypes use in-memory state by default because persistence is usually the thing being checked, not a dependency. Only hit a scratch database or clearly marked local file when the question explicitly involves persistence.

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 behaves correctly under real cases. Use a UI prototype when the question is what a page or component should look like, comparing radically different layouts.

What are the limitations of prototype code?

Prototype code skips tests, error handling, and abstractions, so it must never ship directly to production. Once it answers its question, either delete it or rewrite the validated decision properly in the real module.