Group
  • Testing

    Test my core flows in every major browser

    Runs the money-path user flows through Chrome, Safari, and Firefox and fixes the browser-specific breakage it finds.

    • Improve quality
    • Plan & validate
    • Intermediate
    • General

Free Prompt

Test my app's core flows across browsers and fix what breaks. The flows that matter: signup, login, the primary create/edit action, and checkout/payment. 1. Setup: configure my e2e test tool (Playwright makes this easy) to run the core flow suite in Chromium, WebKit (Safari's engine), and Firefox. If I have no e2e setup, create it for these flows only. 2. Run and triage: execute the suite in all three engines and list every failure per browser. Common culprits to check even if tests pass: date input rendering, autofill behavior, sticky/fixed layout differences, flexbox and grid edge cases in Safari, file input styling and behavior, and any CSS or JS API I used that needs a prefix or is unsupported somewhere (check caniuse for anything recent). 3. Manual pass: for each browser, do one manual run of the checkout flow, because payment iframes and redirects behave differently enough that automation misses things. Include Safari specifically; it is the browser most likely to break and the one vibe-coders test least. 4. Fix with standards: fix breakage with web standards (proper prefixes, feature detection with fallbacks) rather than browser sniffing and user-agent branching. 5. CI: add the cross-browser suite to CI so future changes get caught. If runtime is a concern, run WebKit and Firefox on the core flows only, with the full suite in Chromium. Do not polyfill heavily for ancient browsers; my support target is the last two major versions of Chrome, Safari, Firefox, and Edge. Do not skip Safari because it is inconvenient. Give me: the browser matrix config, failures found per browser with the fix applied, and the CI change.

What This Does / How This Helps

Runs your critical flows through all three browser engines and fixes the Safari-shaped holes before your users find them. Everything works in Chrome, because that is what the AI tested in and what you developed in. Then a Safari user cannot complete checkout because of a date input or a flexbox quirk, and you find out from a refund request. Safari is roughly a quarter of browser traffic and the most standards-picky of the bunch. The prompt sets up a three-engine test run on just the flows that matter, does a manual payment pass per browser since automation misses iframe quirks, and puts the matrix in CI so it stays fixed.

Want to skip doing this by hand?

Fortivibe audits your app for all of the areas these prompts cover (and more).

See What We Check

Related Prompts