Frontend Guidelines

Audit user-facing interface code against the Web Interface Guidelines: accessibility, focus states, forms, animation, typography, performance, touch, theming, i18n, hydration, copy, and the anti-pattern list.

The rules

GUIDELINES.md is a pinned copy of the guidelines and the source of truth for every audit. Reading the pin rather than the network keeps the audit deterministic, offline-capable, and usable inside a sub-agent with no web access. frontend-design uses this audit process for its integrated check; other workflows read the pin directly.

Process

1. Read GUIDELINES.md in full, including its output format.
2. Resolve the files under audit from the caller's argument, file list, or pattern. Ask the user which files to review when none was supplied.
3. Apply every rule to every file. Read enough surrounding code to tell a real violation from a rule satisfied elsewhere: a label rendered by a wrapper, a focus ring set by a shared class, a token that already honours prefers-reduced-motion.
4. Report findings in the format GUIDELINES.md specifies: grouped by file, one terse file:line line per finding, ✓ pass for a clean file. State the issue and its location; explain only when the fix is non-obvious.

Completion criterion: every rule applied to every file under audit, each finding carrying a file:line, and every audited file either listed with findings or marked ✓ pass.

Invocation boundary