Frontend Quality

Use this skill as an evidence-led implementation and review checklist for an existing frontend. It improves the changed surface without silently replacing its framework, data flow, visual system, or public behavior.

Contract

Inputs

• The requirements, acceptance criteria, primary user task, and a verification plan.
• The current frontend stack: framework and version, runtime, rendering mode, routing, styling approach, design tokens, supported browsers, and build/test commands.
• The existing surface map: route entry point, adjacent components, layout wrappers, hooks, client services, state/query patterns, API contracts, styles, assets, and relevant tests.
• Required data and interaction states: loading, empty, partial, error, success, disabled, submitting, permission-denied, selected, and expanded states where relevant.
• Supported viewport range, input methods, locales, themes, accessibility needs, performance constraints, and explicit files, APIs, or behavior that must not change.

Outputs

• Verified implementation guidance or review findings tied to the supplied requirements and inspected code.
• A focused change boundary, reuse targets, component/state contracts, responsive behavior, accessibility obligations, and relevant performance or motion decisions.
• Fresh verification evidence: commands and results, rendered/browser checks when relevant, unresolved questions, and residual risks. Do not call an assertion verified from source inspection alone.