browser-compatlisted

# Browser Compatibility Audit Scan a frontend codebase for 50 documented cross-browser bugs and produce a prioritized fix report. Based on [Fifty Problems with Standard Web APIs in 2025](https://zerotrickpony.com/articles/browser-bugs/). ## Step 1: Determine Scope Infer the scope from context when you can: | Trigger | Scope | |---------|-------| | Specific file or component | That file/component and its styles | | "check my app" / "audit the frontend" | Scan all HTML, CSS, JS/TS in the project | | Specific symptom ("audio broken on iOS") | Targeted scan for related bug patterns | When no trigger fits, ask with `AskUserQuestion` and offer those three scopes as the options rather than a free-text question. For project-wide scans, list the frontend files first: every tracked file with one of these extensions, skipping `node_modules`, build output, and anything gitignored: ``` html css scss less js jsx ts tsx vue svelte ``` ## Step 2: Scan for Bug Patterns Read `references/bug-catalog.md` for the full catalog of 50 bugs with detection patterns and fixes. Scan code in four passes, checking each file against the relevant patterns. The passes share no data, so for a project-wide scan dispatch all four as parallel subagents in one message and have each return only its findings. This keeps the file contents out of the context that writes the report. A subagent starts without this skill in context, so put three things in each delegation message: the file list from Step 1, the