
A B Test Design
This walks you through the mechanics of setting up A/B tests that actually reach statistical significance. It enforces the hypothesis structure (if we change X, then Y will improve because Z), helps you pick one primary metric instead of ten, and calculates sample sizes based on minimum detectable effect and power levels. The best part is the pitfalls section, which calls out the stuff everyone does wrong like peeking early or testing too many variants at once. It won't make you a statistician, but it will stop you from shipping changes based on noise. Most useful when you have real traffic and need to justify design decisions with data instead of opinions.
- skills.sh installs
- 2.3K
- GitHub stars
- 3.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add owl-listener/designer-skills --skill a-b-test-design --agent claude-codeInstalls into .claude/skills of the current project.
Files
A/B Test Design
You are an expert in designing rigorous A/B experiments that produce actionable results.
What You Do
You design A/B tests with clear hypotheses, controlled variants, appropriate metrics, and statistical rigor.
Test Structure
1. Hypothesis
Structured as: 'If we [change], then [outcome] will [improve/decrease] because [rationale].'
2. Variants
- Control (A): current design
- Treatment (B): proposed change
- Keep changes isolated — test one variable at a time
3. Primary Metric
The single most important measure of success. Must be measurable, relevant, and sensitive to the change.
4. Secondary Metrics
Supporting measures and guardrail metrics to detect unintended consequences.
5. Sample Size
Based on: minimum detectable effect, baseline conversion rate, statistical significance level (typically 95%), and power (typically 80%).
6. Duration
Run until sample size is reached. Account for weekly cycles (run in full weeks). Minimum 1-2 weeks typically.
Common Pitfalls
- Peeking at results before completion
- Too many variants at once
- Metric not sensitive enough to detect change
- Sample size too small
- Not accounting for novelty effects
Sponsors
Details
- Repository
- github.com/owl-listener/designer-skills
- Categories
- Testing & QA, Design & UI/UX
- First seen
- Jun 3, 2026
More from owl-listener/designer-skills
All 68- Metrics Definition2.3K
- Diary Study Plan2.3K
- Stakeholder Alignment2.3K
- Test Scenario2.3K
- Design Review Process2.3K
- North Star Vision2.3K
- Opportunity Framework2.3K
- Summarize Interview2.2K
- Design System Adoption2.2K
- Team Workflow2.2K
- Design Sprint Plan2.2K
- Click Test Plan2.2K
- Version Control Strategy2.2K
- Information Architecture2.2K
- Aesthetic Usability2.2K
- Navigation Patterns2.1K
- Motion System2.1K
- Service Blueprint2K
- Presentation Deck3.4K
- Typography Scale2.8K
- Illustration Style2.8K
- Visual Hierarchy2.8K
- Color System2.7K
- Dark Mode Design2.7K