pragman-prototypelisted

# Pragman Prototype Turn uncertainty into something the user can inspect, click, and decide on. A prototype is a decision artifact, not an early production implementation. ## Use this skill when - A product, workflow, or UI direction is hard to evaluate from prose alone. - You need to compare one or two meaningful alternatives before paying the cost of production code. - Feedback, accessibility, responsive behavior, or a local-only safety boundary must be exercised early. ## Acceleration payoff It replaces speculative implementation with a fast, reversible decision artifact that exposes wrong assumptions before they become rework. ## Workflow 1. State the decision the prototype must unlock, the intended user, the riskiest assumptions, and the smallest flow that can test them. Ask only questions whose answers materially change the flow or safety boundary. 2. Load only the approved project taste, brand, accessibility, and workflow references. Preserve their sensitivity. Do not embed confidential text, credentials, private URLs, analytics, third-party scripts, or remote assets in a shareable artifact. 3. Decide whether a specialist adds value. Route through `pragman-router` when design systems, visual exploration, browser QA, or another installed capability is useful. Keep the route bounded to the stated decision. 4. Create one self-contained HTML flow by default. Add variants only when each represents a meaningful decision alternative; label the hypothesis and trade-off