check-browser

You can verify UI state using an API-first approach by checking element existence and data status via lightweight API calls. Browser automation through Playwright is used only as a fallback for visual checks when API data is insufficient.

You can check queue health and service incidents through lightweight API calls. This API-first verification method confirms service status directly, avoiding the overhead of full browser automation for data-only checks.

Playwright is used for UI testing when you need to verify visual attributes that API checks cannot confirm. The API-first approach serves as the default, with Playwright acting as a smart fallback specifically for visual checks.

You can run a quick browser status check by using the /check-browser command followed by your question. This triggers concise outputs that verify element existence, data status, or visual attributes based on your query.

API-first browser checking handles data status and element existence, but relies on Playwright browser automation as a fallback for confirming visual attributes. This ensures visual checks are covered when API data is not sufficient.