effective-weblisted

# Effective Web Treat the web experience as one system. Route each request to the smallest relevant guidance set, then check the result across design, implementation, accessibility, performance, and verification boundaries. Treat a website, URL, browser, or HTML document as input evidence, not as a trigger by itself. Load this skill only when the deliverable designs, changes, reviews, or verifies a browser-facing experience. ## Workflow 1. Inspect the product goal, primary users and actions, accepted ADRs, existing stack, local conventions, browser support, and available evidence. 2. Select one primary route from the table. Read that route before acting. 3. Load only the detailed references required by the route and current problem. Add another route only when the work genuinely crosses concerns. 4. Implement or review against the existing product language and architecture. Prefer measured evidence and repository conventions over generic defaults. 5. Verify the affected states, responsive behavior, keyboard and screen-reader use, loading cost, and relevant project checks before declaring the work done. For greenfield direction or an AI-assisted feature, start with Design Planning. For a broad redesign or cross-cutting review, start with Design Review and Modernization. Add focused routes only as the work crosses those concerns. ## Route by Intent | User intent | Read | | --- | --- | | Plan a new experience or establish its register, hierarchy, direction, an