What problem does it solve? Code-level validation alone cannot confirm that a frontend change actually works in the rendered UI. This Skill ensures browser-based evidence is collected whenever visible or interactive behavior determines correctness, and prevents unverified UI paths from being called verified. ## Core Features & Use Cases - Conditional activation: Applies only when rendered or interactive web state materially affects the result, not for ordinary research or API/CLI-performable operations. - Browser-driven validation: Uses the available mcp__cua_repl unified browser capability to exercise the exact affected route and workflow after code validation. - Honest limitation reporting: When browser capability is unavailable or a route cannot be exercised, it states the exact limitation and provides a concrete manual validation path instead of claiming verification. - Use Case: After modifying a checkout form's validation logic, run the code checks, then drive the actual checkout route in the browser, record the observed state, and confirm the workflow behaves as intended. ## Quick Start Validate my frontend change by exercising the affected route in the browser and recording the observed behavior.
