parallel-prototypes

Compare 2-3 UX variants under a common hypothesis and log outcomes.

16|3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/YehudaFrankel/clankbrain --skill parallel-prototypes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-prototypes
Source: https://github.com/YehudaFrankel/clankbrain/tree/main/.claude/skills/parallel-prototypes
Command: npx skills add https://github.com/YehudaFrankel/clankbrain --skill parallel-prototypes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instead of choosing a single approach and iterating serially, this skill enables running 2-3 UX variants in parallel to accelerate decision-making and reduce cycle time.

Core Features & Use Cases

  • Build 2-3 distinct versions of the same screen or flow to compare how different design choices affect user behavior.
  • Evaluate all variants against the same hypothesis at the same time to ensure a fair comparison.
  • After selecting a winner, log the outcome to a prototype log and clean up losers to keep the codebase focused.

Quick Start

State your hypothesis, create 2-3 variant files, and run the parallel-prototypes workflow to compare results.

Frequently Asked Questions about parallel-prototypes

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

FAQPage Schema
How do I compare multiple UX design variants in parallel to decide faster?

To compare UX design variants in parallel, define 2-3 separate prototype files for a screen or flow, evaluate them against a shared hypothesis, and log outcomes to identify the winning design decision while cleaning up losers.

What is parallel prototype testing and when should I use it?

Parallel prototype testing is running 2-3 interface approaches simultaneously to accelerate decision making. Use it when deciding between distinct layouts, copy variations, or user flows and when a clear test hypothesis can be articulated.

How do I evaluate different layout or flow options against the same hypothesis?

You evaluate different layout or flow options by building 2-3 separate variant files and running them through a parallel comparison workflow. This ensures all design choices are tested fairly under identical hypothesis conditions simultaneously.

Do I need to define a hypothesis before comparing interface approaches?

Yes, a clearly articulated test hypothesis is required before comparing interface approaches. The workflow evaluates all 2-3 variants against this specific hypothesis to ensure a fair comparison and accurate design decision.

What happens to the losing variants after a UX comparison is completed?

After a UX comparison is completed and a winner is selected, the losing variants are cleaned up to keep the codebase focused. The evaluation outcome is also logged to a prototype log for future reference.