prototype

Builds multiple divergent UI variants behind a keyboard-driven picker for live comparison and selection.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill prototype-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/prototype
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill prototype-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing a UI direction from a single static mockup or a verbal description is guesswork. This Skill builds several genuinely different working versions of one UI piece and renders them behind a floating picker, so you can flip through real, interactive variants and promote the one that feels right. ## Core Features & Use Cases - Divergent variant generation: Creates 3-5 fully working variants of a described component, each exploring a distinct axis such as layout, density, personality, motion, or interaction model. - Fixed picker harness: Renders variants full-size in realistic context behind a spec-locked dark pill picker with keyboard shortcuts (1-N, arrows, R to replay) and URL-persisted selection. - Isolated prototype surface: Works in an isolated route or standalone HTML file, never touching production code until you pick a winner to integrate. - Use Case: Ask for three versions of a hold-to-delete button; flip through Quiet, Editorial, and Playful directions live in the browser, then promote the winner into your codebase with project conventions intact. ## Quick Start Ask the assistant to prototype three variants of your pricing card so you can flip through them and pick a winner.

Frequently Asked Questions about prototype

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

FAQPage Schema
How do I compare multiple UI design directions before committing?

Describe one UI piece and the skill builds 3-5 fully working variants, each on a distinct axis like layout, motion, or density. You flip through them live with number keys or arrows in a floating picker, then promote the winner into your codebase.

How do I prototype a component without touching production code?

All variants live on an isolated prototype surface, either a dedicated route like /prototypes/<slug> or a standalone HTML file. Nothing imports into production code; integration happens only after you explicitly pick a variant.

Does the prototype picker work in plain HTML without a framework?

Yes. When no project or dev server exists, the skill produces a single self-contained HTML file with inline CSS and JavaScript that opens directly in a browser, using the same picker markup and keyboard wiring.

Can I run another round of variants after seeing the first set?

Yes. The riff command keeps the existing harness and generates a fresh set of variants diverging around the direction you gravitated toward, so each round narrows the exploration instead of restarting it.

What are the limitations of variant-based UI prototyping?

Each run covers exactly one component, so multi-piece screens require separate runs. Variant count is capped at five to keep comparisons meaningful, and the picker appearance is fixed by spec and cannot be restyled to match the project.