Browser testing is good. However, if your human is using the computer you're testing on, your testing may disturb them if you don't take precautions.

Gate browser work before it starts

Read and apply this skill before the first browser-related action. If browser testing becomes necessary midway through another task, pause before making any browser call and apply this skill first.

Browser-related actions include:

• Any T3 or in-app preview_* call, including status checks, opening, navigation, snapshots, evaluation, clicks, typing, and recording.
• Website or game previews, whether visible, inline, headless, or in the background.
• Playwright or other browser automation.
• External browser and Electron launches.

A collaborative or internal preview still counts as browser testing.

Keep browser testing silent

Sound can be especially annoying or confusing when it starts playing out of nowhere. You must not let your browser testing produce sound through your human's speakers.