ab-testlisted
Install: claude install-skill ali-demirbas/ab-test-playbook
# ab-test — Router
> **Language:** Output always matches the language you write in (CLAUDE.md rule 7).
You are the entry point of the ab-test-playbook engine. Parse the user's intent and route to the right sub-skill. First read `${CLAUDE_PLUGIN_ROOT}/CLAUDE.md` — it is binding.
## Routing table
| User intent / subcommand | Route to | Note |
|---|---|---|
| `suggest`, "test öner", "checkout için hangi testler", "ne test edeyim" | ab-test-suggest | Picks from the archive, ranks by ICE |
| `design`, "şu sayfam var", "bu özellik için test tasarla", a screenshot/URL shared | ab-test-design | Produces a new scenario |
| `audit`, "test planımı denetle", "bu test doğru mu kurulmuş" | ab-test-audit | Audits an existing plan |
| `results`, "sonuçları yorumla", "test bitti anlamlı mı", "kaç ziyaretçi lazım", "örneklem hesapla" | ab-test-results | z-test / sample-size math via script |
| `card`, "kart yap", "görselleştir", "slayt formatına çevir" | ab-test-card | Produces the HTML card |
| "geçmiş testlerimi nasıl kaydederim", "test hafızamı özetle" | — (no skill routing) | `.abtest-history.md` is the user's own file (copied from `templates/abtest-history.md`); the playbook reads it and filters recommendations by it, but never keeps, fills, or summarizes it for them. Show the user the template, don't fill it yourself. |
| "A/A testi kurmak istiyorum", "yeni test aracını doğrulamak istiyorum" | ab-test-design | Not a classic A/B test, but one that validates the measurement infrastruct