What problem does it solve? When exploring a design idea for a CLI, dashboard, visualization, or workflow, it is easy to accidentally contaminate canonical research outputs with unvalidated prototype artifacts. This Skill enforces a strict sandbox discipline so prototypes answer design questions without ever being mistaken for research evidence. ## Core Features & Use Cases - Disposable Prototyping: Sketch CLI designs, figure layouts, dashboards, and task-state machines in scratch or prototype directories. - Evidence Isolation: Enforces the rule that prototypes never write into canonical results trees and are never cited as paper claims. - Promotion Discipline: Defines what a prototype must go through (task brief, contract, tests, provenance) before becoming production code. - Use Case: You want to compare two result-browser layouts before committing to an implementation. Build both as marked exploratory prototypes under a scratch path, record what was learned, then route the winner through the formal task-brief and contract-first workflow. ## Quick Start Ask the agent to prototype a new dashboard layout idea in a disposable scratch directory and record what design question it answers.
