browser-validationlisted

# Browser Validation ## Purpose Validate browser-facing work with real browser evidence, not assumptions. The goal is to prove the implementation is visually correct, functionally correct, and consistent with business logic. User-facing reports stay in Russian unless requested otherwise. Store browser artifacts under `browser/` and do not commit them. ## When To Use Use this skill without waiting for explicit invocation when the task asks to: - Check, validate, verify, or prove a browser-visible implementation. - Verify UI visually, pixel-perfect, responsive, mobile/desktop, or against a design/reference. - Test navigation, forms, modals, tabs, dialogs, auth-like flows, route changes, loading/error/empty states, or business behavior. - Capture screenshots or browser evidence under `browser/`. - Confirm that a frontend fix works after code changes. If the validation exposes console, network, runtime, layout, hydration, or performance problems, hand off to `browser-debug`. Use this skill after: - UI, layout, styling, responsive, animation, or design-system changes. - User-flow, form, route, navigation, modal, upload, auth, checkout-like, or wizard changes. - Client-side business logic, validation, error-state, loading-state, or empty-state changes. - Changes that affect browser-visible data, browser storage, network requests, hydration, or runtime state. If the user asks for pixel-perfect, production-quality, or "проверь в браузере", this skill applies. ## Required V