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-code

Installs 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
1owl-listener avatarclick-test-planowl-listener/designer-skillsDesign click/first-click tests to evaluate navigation and information findability.2.2Kskills.sh installs
2refoundai avatarusability-testingrefoundai/lenny-skillsHelp users conduct effective usability testing. Use when someone is planning user tests, designing prototype validation, preparing usability studies, or trying 1.8Kskills.sh installs
3forcedotcom avatartesting-agentforceforcedotcom/afv-librarytesting agentforce1.5Kskills.sh installs
4itechmeat avatarreact-testing-libraryitechmeat/llm-codeReact Testing Library: user-centric component testing with queries, user-event simulation, async utilities, and accessibility-first API. Use when writing React 1.4Kskills.sh installs
5jaganpro avatarsf-ai-agentforce-testingjaganpro/sf-skillssf ai agentforce testing1.3Kskills.sh installs
6neolabhq avatartest-driven-developmentneolabhq/context-engineering-kitUse when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests1.3Kskills.sh installs