ascii-wireframeslisted

# ASCII wireframes Explore layout directions cheaply, in text, before any pixels get pushed. ## Step 1 - scope the request If the request already names a screen and its primary job (example: "pricing page for a B2B analytics tool, primary job: convert a trial user to a paid plan"), go to Step 2. If either the screen or its primary job is missing, ask exactly one clarifying question covering both. Do not guess and do not proceed on a partial brief. ## Step 2 - decide three hypotheses Pick three genuinely different hypotheses for the same screen. Each one is a different answer to: what value proposition does this screen lead with? A hypothesis is not valid if it only changes color, spacing, font, or component style from another one - that is a restyle, not a hypothesis. Examples of distinct hypotheses for the same screen: - Pricing page: (a) lead with a single recommended plan, (b) lead with a feature-comparison table, (c) lead with an ROI calculator. - Onboarding flow: (a) lead with a guided product tour, (b) lead with a self-seeding empty state, (c) lead with a single setup question. - Dashboard home: (a) lead with today's tasks, (b) lead with a project-board overview, (c) lead with a single focused item and its context. If the user asks for more than 5 variants, cap at 5 and say why: past five, a reviewer stops comparing and starts skimming. ## Step 3 - render each hypothesis For each hypothesis, in order, output exactly this shape: 1. A one-line label: `V<N> - <