← ClaudeAtlas

ab-split-testlisted

How an agent should use AB Split Test while building, changing, or optimising a WordPress or connected website. Use whenever you create, rewrite, redesign, restructure, or materially change a page, section, offer, price, form, checkout, or conversion flow on a site with AB Split Test installed. Turns the agent from a designer replacing one guess with another into an optimisation system — observe behaviour, find the opportunity, build a hypothesis, prove it on real traffic, keep what works, learn from what doesn't, repeat.
SiteSpot/human-web-feedback-loop · ★ 0 · Testing & QA · score 72
Install: claude install-skill SiteSpot/human-web-feedback-loop
# AB Split Test — the Proof Loop for agents You will have opinions about what should work. So will the owner. Opinions are inputs. Visitor behaviour is evidence. The operating loop is **SEE → FIND → BUILD → PROVE → KEEP** — and KEEP feeds straight back into SEE. Same five steps the product and its documentation use. The rule in one line: **if a material change could plausibly help or hurt conversion, don't silently replace the existing version when you could learn from a test instead.** Testing isn't a final validation step. It's how you find out what to do next. --- ## 0 · Should this be tested at all? Ask: *could this change plausibly alter conversion enough that knowing the answer is worth the traffic?* **Test** — material changes to: homepage hero, landing pages, pricing, product pages, cart/checkout, signup/booking, lead forms · headline or primary promise · primary CTA wording/position/prominence · offer, price, guarantee, urgency · form length or checkout steps · section order or funnel structure · major social proof · **any AI-generated conversion copy** · large design changes · new checkout/booking/form/theme systems (use the test as a safe rollout with instant rollback). **Ship directly** — bug fixes, broken links, typos, factual/legal/accessibility/security fixes, admin-only changes, pages with negligible traffic and no conversion role, changes the owner explicitly asked to publish untested, changes whose conversion impact is genuinely nil. When unsure, we