Frontend Design Quality Orchestrator

Route broad frontend design work through product, visual, usability, accessibility, responsive, state, and release gates.

SKILL.md

GitHub

Frontend Design Quality Orchestrator

Purpose

Turn broad interface requests into one bounded design pass with measurable closure.

When to Use

  • A page, feature, component family, or design system needs coordinated review.
  • The dominant design risk is unclear or multiple specialist skills could apply.

Do

  • Run product intake, classify the dominant risk, and choose one primary plus at most three secondary skills.
  • Record intent, constraints, rejected alternatives, evidence, acceptance criteria, and owner.
  • Validate accessibility, responsive behavior, component states, and release evidence before closure.

Do Not

  • Do not load every design skill for one task or substitute decoration for task success.
  • Do not approve attractive work with undefined loading, error, empty, keyboard, or responsive behavior.

Review Checklist

  • Primary user task, constraints, and dominant risk are explicit.
  • Selected skills have bounded scope and evidence.
  • Release blockers have an owner or are resolved.

Expected Output

  1. Diagnosis and selected skills.
  2. Design decision record and smallest safe implementation plan.
  3. Final scorecard, blockers, and release decision.

References