Designing an A/B test helps you make smart decisions based on real data. You start with a clear hypothesis about what change will improve an outcome. Then you set up two versions called variants and measure the results using metrics. Sample size calculations tell you how many people you need to see a real difference.
This skill covers the full process from start to finish. You learn how to choose the right primary metric and secondary metrics. You also learn about common pitfalls like peeking at results too early. Knowing when not to run an A/B test is just as important.
By following best practices you get results you can trust. Always document your plan before starting. Share what you learn even if the test fails. This approach makes your experiments more valuable.
Global
mkdir -p ~/.claude/skills/a-b-test-designProject
mkdir -p .claude/skills/a-b-test-designSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step