Auditing Interface Quality

Overview

Audit frontend source for the systems that make an interface feel coherent, predictable, and physically stable. Infer the project's own interface language first, then produce evidence-backed remediation guidance without editing the application.

Core principle: Stable UI is not motionless UI. It preserves geometry, identity, state continuity, input behavior, and feedback locality while change occurs.

Boundaries

• Keep the audit read-only. Do not edit application source, install dependencies, or apply remediation.
• Use source, project documentation, configuration, and existing tests only. Do not require or use a browser in this workflow.
• Do not consult external library documentation, web sources, design guidelines, or standards to fill source gaps. If a higher-priority instruction explicitly requires external context, disclose it under evidence boundaries and never use it as evidence of project behavior.
• Report source facts as facts. Label rendering-dependent behavior as a source-inferred risk and name the runtime check needed to confirm it.
• Do not claim visual appearance, accessibility conformance, performance, layout-shift magnitude, or cross-browser behavior from source alone.
• Preserve documented product-specific exceptions. Audit consistency with the project's language, not conformity to a preferred aesthetic.

Required Workflow