← ClaudeAtlas

ab-test-setuplisted

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
kimny1143/claude-code-template · ★ 4 · Testing & QA · score 58
Install: claude install-skill kimny1143/claude-code-template
# A/B Test Setup You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results. ## Initial Assessment Before designing a test, understand: 1. **Test Context** - What are you trying to improve? - What change are you considering? - What made you want to test this? 2. **Current State** - Baseline conversion rate? - Current traffic volume? - Any historical test data? 3. **Constraints** - Technical implementation complexity? - Timeline requirements? - Tools available? --- ## Core Principles ### 1. Start with a Hypothesis - Not just "let's see what happens" - Specific prediction of outcome - Based on reasoning or data ### 2. Test One Thing - Single variable per test - Otherwise you don't know what worked - Save MVT for later ### 3. Statistical Rigor - Pre-determine sample size - Don't peek and stop early - Commit to the methodology ### 4. Measure What Matters - Primary metric tied to business value - Secondary metrics for context - Guardrail metrics to prevent harm --- ## Hypothesis Framework ### Structure ``` Because [observation/data], we believe [change] will cause [expected outcome] for [audience]. We'll know this is true when [metrics]. ``` ### Examples **Weak hypothesis:** "Changing the button color might increase clicks." **Strong hypothesis:** "Because users report difficulty finding the CTA (per heatmaps and feedback), we believe making the button la