ab-test-designlisted

# ab-test-design — New Scenario Design > **Language:** Output always matches the language you write in (CLAUDE.md rule 7). `${CLAUDE_PLUGIN_ROOT}/CLAUDE.md` rules are binding. The format is defined in `${CLAUDE_PLUGIN_ROOT}/knowledge/methodology.md` — read it before producing anything. ## Flow 1. Understand the page/feature the user shared (screenshot, URL, description), in **two passes**: **First, the problem gets clarified.** If a page was shared, which problem to solve is determined with the single multiple-choice question (CLAUDE.md rule 13); ask it here if the router didn't. If the user stated a solution directly ("let's make the button bigger"), clarify which problem it solves with the same question; if the stated solution doesn't solve the stated problem, say so and suggest a variant that fits the problem — don't silently design what they asked for. If no answer comes, proceed anyway but mark the hypothesis's basis as "intuition" (rule 10). **Then candidates are drawn from three axes at once**, don't look only at the first: - **Change:** the form, copy, position or visual weight of an element that already exists on the page. - **Remove:** an element that exists on the page but blocks the flow. - **Add:** information or an action the user needs at that step that the page does **not** have — this often carries the biggest gain and is the easiest one to skip (e.g. a delivery date or installment option at the payment step; an action button matching an