ab-test-suggestlisted

# ab-test-suggest — Archive Test Suggestions > **Language:** Output always matches the language you write in (CLAUDE.md rule 7). `${CLAUDE_PLUGIN_ROOT}/CLAUDE.md` rules are binding. ## Flow 1. Take the context from the router (sector, page). **Traffic, test tool and setup info are not asked** (CLAUDE.md rules 5 and 13): they aren't required to produce a scenario, and aren't put in front of the output as "missing." They're only requested when the user asks about duration, sample size or significance. If sector or page is still unclear, pick the closest stage and state the assumption in one sentence — don't ask a question and stall the flow. - **Read the test memory (CLAUDE.md rule 16).** Check whether `.abtest-history.md` exists in the user's working directory. If it does, read it and pull the records for the target page. If not, don't narrate that a search happened, just continue silently; at the end of the output, suggest once: "If you keep test history as `.abtest-history.md`, I can filter suggestions against past results." 2. Map the page/flow to a journey stage and read the matching file: - Homepage, landing, campaign page → `knowledge/scenarios/home-landing.md` - Search, filter, results page → `knowledge/scenarios/search-filtering.md` - Menu and in-site navigation → `knowledge/scenarios/search-filtering.md` - Category/listing page → `knowledge/scenarios/category-listing.md` - Product detail → `knowledge/scenarios/product-detail.md` - Cart, coupon