UI Audit

Operating Mode

Treat the request as implementation work unless the user asks for analysis only. Read local instructions first, preserve unrelated changes, and keep edits surgical. Do not create project summary documents or reports unless explicitly requested.

In this repository, read skills/rustfs-console-design-guide/SKILL.md before auditing or changing Console UI. Use that guide as the source of design decisions; use this skill for audit execution, browser validation, evidence capture, and verification.

If the user asks to pull latest, do it before editing after checking git status. If local unrelated work is present, preserve it and avoid destructive git commands.

Classify The Surface

Before scanning, identify the primary UI type and adjust emphasis:

• Operational apps: prioritize density, tables, forms, keyboard flow, data states, batch actions, and predictable navigation.
• Landing/product sites: prioritize first viewport, real visual assets, responsive hero composition, contrast, content hierarchy, and scroll rhythm.
• Developer/docs sites: prioritize reading flow, code block overflow, navigation state, search, anchors, and dark theme.
• Interactive tools/games: prioritize canvas/scene nonblank state, controls, motion, hit targets, and viewport fit.
• Component libraries/migrations: prioritize primitive usage, wrapper boundaries, design tokens, API consistency, and regression patterns.