adv-frontend-review

Audit frontend components across six engineering and design dimensions.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Sharper-Flow/Advance --skill adv-frontend-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adv-frontend-review
Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-frontend-review
Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-frontend-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent frontend review quality by providing a canonical, 6-dimension checklist that ensures UI components meet strict engineering and design standards.

Core Features & Use Cases

  • Systematic Review: Evaluates frontend work across component correctness, accessibility, responsiveness, visual polish, site consistency, and finer details.
  • Governance: Enforces the design quality bar established in the Advance engineering contract, preventing scope drift and shallow reviews.
  • Use Case: When a developer submits a new UI component, the reviewer uses this skill to systematically verify that the implementation adheres to accessibility standards and design tokens before merging.

Quick Start

Load the adv-frontend-review skill to begin the 6-dimension assessment of the current frontend task.

Frequently Asked Questions about adv-frontend-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically review frontend components for accessibility and visual consistency?

Systematic frontend review evaluates UI component implementations across six core dimensions: component correctness, accessibility, responsiveness, visual polish, site consistency, and finer details. This structured methodology ensures strict engineering and design standards are met before merging.

What is the best way to enforce a design quality bar during UI code review?

Enforcing design quality during UI code review requires a canonical, multi-dimensional checklist that prevents scope drift and shallow reviews. Evaluating frontend work against accessibility standards and design tokens establishes a durable, repeatable quality gate within the engineering contract.

Does a 6-dimension frontend review cover responsive design and component correctness?

A 6-dimension frontend review covers responsive design and component correctness, alongside accessibility, visual polish, site consistency, and finer details. This comprehensive assessment verifies that UI changes adhere to strict engineering standards across all critical implementation areas.

When do I need a standardized frontend quality gate for UI changes?

A standardized frontend quality gate is needed during the code review and hardening phases when a developer submits a new UI component. It verifies that the implementation adheres to accessibility standards and design tokens before merging.

How to audit frontend implementations against design tokens and accessibility standards?

Auditing frontend implementations involves applying a structured methodology to verify UI changes against accessibility standards and design tokens. This process evaluates component correctness, responsiveness, and visual consistency to prevent scope drift.

What are the limitations of a checklist-based frontend component review?

A checklist-based frontend component review focuses on verifying adherence to predefined engineering and design standards. It is designed for the code review and hardening phases, preventing shallow reviews but limited to the six specified assessment dimensions.