What problem does it solve? Product teams lack a consistent, objective bar for deciding whether a frontend implementation or design is ready to ship, leading to subjective reviews and inconsistent releases. ## Core Features & Use Cases - Twelve-Category Quality Gate: Evaluates clarity, task completion, consistency, accessibility, visual hierarchy, content quality, forms, responsiveness, performance, error recovery, data display, and security. - Structured Verdicts and Scorecard: Assigns Pass, Pass with minor issues, Fail, or Blocked verdicts and produces a scorecard with prioritized fixes (P0/P1/P2) for the developer agent. - Release Gate Rules: Blocks release when critical failures exist, such as broken accessibility, data loss risk, missing disclaimers, or broken mobile layouts. - Use Case: A technical product owner reviews a new checkout flow before release, runs each screen through the criteria, and returns a scorecard listing P0 accessibility fixes the developer must complete. ## Quick Start Review the attached checkout screen implementation against the interface quality criteria and give me a verdict with a scorecard and prioritized fixes.