dev-browser

To manually verify frontend features, you need a chrome MCP server, a stable app URL, and explicit success criteria. The Skill launches the browser, loads pages, simulates user interactions like clicks and typing, and captures UI behavior results end-to-end.

Yes, during manual UI testing you can inspect the Accessibility Tree and UI state using a snapshot tool. You can also validate frontend debugging by checking the browser Console for errors and the Network tab for API calls.

Before performing manual browser QA, you must configure a chrome MCP server, ensure your local or remote application URL is stable, and define explicit success criteria to guide feature verification interactions and result capture.

You simulate user behavior for frontend debugging by initializing the browser, navigating to the target URL, and using click, type, or scroll tools to interact with the UI, ensuring features render and interact as expected.

Manual browser QA works across both local and remote environments. You launch the browser, navigate to the local or remote URL, and begin manual verification of the new feature to ensure it renders correctly and interacts as expected.