--- name: web-conventions description: Generic, composable web platform conventions — semantic HTML, accessibility, modern CSS, custom-property design tokens, and Baseline browser-support policy that apply across all web frontends (static sites, web component SPAs). Meant to be composed with context-specific skills (e.g. `web-static`, `web-components`). Use when writing, generating, or reviewing HTML or CSS anywhere the composed skill does not already specify a rule. Triggers on "web conventions", "semantic HTML", "web forms", "form validation", "input types", "accessibility review", "modern CSS", "design tokens", "DESIGN.md", "Baseline status", "serve the site", "dev server", "zws", or any request to write or review HTML/CSS. Also use when a project contains a DESIGN.md that should guide HTML/CSS generation, when a Baseline status must be looked up (bundled webstatus.dev snapshot in `references/baseline-snapshot.md`), or when a static site root needs to be served locally (bundled zws dev server in `scripts/zws`). --- Apply all rules below strictly to any HTML and CSS you write, generate, or review. ## Scope - Platform-level rules for HTML and CSS only — semantics, accessibility, styling, theming, browser-support policy. - JavaScript policy, architecture, state management, routing, dependencies, project structure, and verification loops are **not** in this skill — see the context-specific skills `web-static` (no-JavaScript static sites) and `web-components` (web component SPAs). - Responsive strategy (media queries vs container queries) is stack-specific — the composed skill decides. - When a composed skill specifies a rule, the composed skill wins; this skill is the fallback baseline. ## Guiding Principles - web standards and web platform first - minimal external dependencies — every dependency must justify its existence - progressive enhancement over JavaScript-first design ## HTML Rules - semantic elements over generic `

`/`` — use `

`, `