prototype

Create disposable logic or UI prototypes to answer design questions.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill prototype-leocosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/leocosta/octopus/tree/main/skills/prototype
Command: npx skills add https://github.com/leocosta/octopus --skill prototype-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Disposable code that answers a design question without committing to a full feature, enabling quick validation before investing in implementation.

Core Features & Use Cases

  • One-question, smallest-possible prototype for both logic/state questions and UI explorations.
  • No-persistence by default; capture the final decision in NOTES.md or ADR before deletion.
  • Guided bifurcation of work (logic vs UI) with references documented in REFERENCE.md.

Quick Start

Identify the design question, implement the smallest working prototype for that question (logic/state or UI), and capture the final decision in NOTES.md before deleting.

Frequently Asked Questions about prototype

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

FAQPage Schema
How do I validate a design question with throwaway code before full implementation?▼

You validate a design question by building the smallest possible throwaway prototype that directly answers the query, enabling rapid validation before committing to full feature implementation.

What is the best way to structure a rapid prototype for UI explorations versus logic questions?▼

The best way to structure a rapid prototype is through guided bifurcation, splitting work into UI variant explorations or logic/state prototypes based on the question type, while documenting references in REFERENCE.md.

How do I document validation notes before deleting disposable code?▼

You document validation notes by capturing the final design decision in NOTES.md or an ADR (Architecture Decision Record) before deleting the throwaway prototype to ensure no-persistence by default.

Can I use rapid prototyping for both state management logic and UI variant testing?▼

Yes, rapid prototyping covers both logic/state prototypes and UI variant explorations depending on the question type, allowing you to test state management logic or visual design alternatives quickly.

When should I not use throwaway prototypes for software design validation?▼

You should avoid throwaway prototypes when you need persistent implementation features, as they enforce no-persistence by default and require capturing decisions in NOTES.md or ADR before deletion.

Does rapid prototyping require any specific dependencies or components to run?▼

No, rapid prototyping requires no specific dependencies or components, allowing you to create disposable code quickly with minimal setup to answer focused design questions.