prototype

Build minimal disposable artifacts to test specific product uncertainties.

Updated May 3, 2026

Search Tags:#validation #prototype #experimentation #decision-making #spike #mockup

Ready to run

npx skills add https://github.com/druejaramillo/skills --skill prototype-druejaramillo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/druejaramillo/skills/tree/main/project/prototype
Command: npx skills add https://github.com/druejaramillo/skills --skill prototype-druejaramillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill prevents the common mistake of building full features before verifying the underlying product or technical assumptions, saving development time and reducing wasted effort.

Core Features & Use Cases

Disposable Experimentation: Creates minimal, runnable artifacts designed to answer a single, specific question.
Evidence-Based Decision Making: Forces a clear definition of success and failure, ensuring that prototypes are used as evidence rather than production code.
Use Case: If you are unsure if a new UI layout will confuse users, use this skill to build a single-screen mockup that tests that specific interaction before committing to a full implementation.

Quick Start

Ask the prototype skill to create a disposable UI experiment to test if users can identify why an order is held.

Frequently Asked Questions about prototype

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

FAQPage Schema

How do I validate a UI interaction before full implementation?▼

You can validate product ideas by building a disposable prototype that tests specific technical uncertainties through isolated experiments. This approach requires defining a single named question and a one-command execution path to empirically verify UI interactions or state transitions before full-scale implementation.

What is a spike in product development and when do I need one?▼

A spike is a minimal, disposable experiment built to test specific product or technical uncertainties through isolated artifacts. You need one when you require empirical evidence for UI interactions or state transitions before committing to full-scale implementation.

How do I test if a new interface layout will confuse users?▼

You can test if a new interface layout confuses users by creating a single-screen disposable mockup. This prototype isolates the specific interaction in question, allowing you to gather empirical evidence and make evidence-based decisions before building the full feature.

Can I run prototype experiments without any external dependencies?▼

Yes, you can run prototype experiments without external dependencies. The skill operates independently to build minimal, runnable artifacts designed to answer a single specific question and verify product assumptions through a one-command execution path.

What is the best way to prevent building full features on unverified technical assumptions?▼

The best way to prevent building full features on unverified assumptions is to build disposable experiments that force a clear definition of success and failure. This ensures prototypes are used as empirical evidence rather than production code, saving development time and reducing wasted effort.

When should I not use a disposable prototype for experimentation?▼

You should not use a disposable prototype when you need production-ready code, as these artifacts are designed to be non-production and temporary. Avoid this approach if your task lacks a specific, single question or a defined observer to verify the empirical results.