From 7341335356fcd7b69c188a59c0d41c691b3e06f7 Mon Sep 17 00:00:00 2001 From: s62dads4-rgb Date: Fri, 30 Jan 2026 15:06:10 +0400 Subject: [PATCH] fix: make browser testing mandatory for Claude Code, add full-page verification CLAUDE.md had weak "if available" browser testing language while prompt.md (Amp) had mandatory language. This mismatch meant Claude Code iterations would skip browser verification entirely, defeating the purpose of the dev-browser skill for catching UI regressions like broken routes/404s. Changes: - CLAUDE.md: match prompt.md mandatory browser testing with dev-browser skill - Both files: add step to verify ALL pages/routes still work (no 404s) Co-Authored-By: Claude Opus 4.5 --- CLAUDE.md | 14 ++++++++------ prompt.md | 3 ++- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index f95bb927..68e7b155 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -77,15 +77,17 @@ Only update CLAUDE.md if you have **genuinely reusable knowledge** that would he - Keep changes focused and minimal - Follow existing code patterns -## Browser Testing (If Available) +## Browser Testing (Required for Frontend Stories) -For any story that changes UI, verify it works in the browser if you have browser testing tools configured (e.g., via MCP): +For any story that changes UI, you MUST verify it works in the browser: -1. Navigate to the relevant page -2. Verify the UI changes work as expected -3. Take a screenshot if helpful for the progress log +1. Load the `dev-browser` skill +2. Navigate to the relevant page +3. Verify the UI changes work as expected +4. Also verify that ALL other pages/routes still work (no 404s, no broken navigation) +5. Take a screenshot if helpful for the progress log -If no browser tools are available, note in your progress report that manual browser verification is needed. +A frontend story is NOT complete until browser verification passes. ## Stop Condition diff --git a/prompt.md b/prompt.md index cdebe901..66bbd7d8 100644 --- a/prompt.md +++ b/prompt.md @@ -87,7 +87,8 @@ For any story that changes UI, you MUST verify it works in the browser: 1. Load the `dev-browser` skill 2. Navigate to the relevant page 3. Verify the UI changes work as expected -4. Take a screenshot if helpful for the progress log +4. Also verify that ALL other pages/routes still work (no 404s, no broken navigation) +5. Take a screenshot if helpful for the progress log A frontend story is NOT complete until browser verification passes.