Web A/B Testing Suite

What it does

Runs end-to-end A/B tests on modern web projects: edge-side variant assignment (no visual flicker), hypothesis design with a priority score, statistical analysis via confidence z-test, and a data-backed winner declaration. Ships database migrations and a drop-in conversion tracker.

When to use it

• When you want to validate a landing page change with data instead of opinion.
• When you need to prioritize which tests to run first using a clear scoring system.
• When you already have enough traffic and want to declare a statistically confident winner.

Steps

1. Define the hypothesis and the variants to test.
2. The assistant scores the hypothesis and builds the test plan.
3. The database migration and variant-assignment script are generated.
4. Conversion tracking is installed as a reviewable draft.
5. At test close, statistical significance is calculated and a winner is suggested.
6. Nothing deploys to production without your code review and approval.

The skill

---
name: web-ab-testing-suite
description: Full-lifecycle A/B testing for modern web apps: zero-flicker variant assignment, hypotheses, statistical analysis, and winner declaration.
---

# Web A/B Testing Suite

## 1. What it does

- Runs end-to-end A/B tests on modern web projects: edge-side variant assignment (no visual flicker), hypothesis design with a priority score, statistical analysis via confidence z-test, and a data-backed winner declaration. Ships database migrations and a drop-in conversion tracker.

## 2. When to use it

- When you want to validate a landing page change with data instead of opinion.
- When you need to prioritize which tests to run first using a clear scoring system.
- When you already have enough traffic and want to declare a statistically confident winner.

## 3. Step by step

- Define the hypothesis and the variants to test.
- The assistant scores the hypothesis and builds the test plan.
- The database migration and variant-assignment script are generated.
- Conversion tracking is installed as a reviewable draft.
- At test close, statistical significance is calculated and a winner is suggested.
- Nothing deploys to production without your code review and approval.

## 4. Safety rules

- Safety rules: everything ships as a draft first; nothing is sent, published, or paid for without your explicit approval; no data, numbers, or results are ever invented; no credentials or secrets are typed into chat.

## 5. Best practices

- Always review the full draft before approving any send, publish, or payment.
- If real information (data, numbers, results) is missing, ask for it to be flagged as pending instead of invented.
- Keep credentials and keys out of chat; set them in environment variables or your secrets manager.

## 6. GoHighLevel integration

- Where relevant, results can be saved as contacts, tags, tasks, or notes inside your GoHighLevel sub-account.
- No automation inside GHL (workflow, campaign, trigger) activates without your review first.

For Claude Code, save it as ~/.claude/skills/web-ab-testing-suite/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.