tpo-interface-quality-criteria

Evaluates product interfaces against twelve quality criteria and produces a release-gate verdict.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-interface-quality-criteria-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tpo-interface-quality-criteria
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/tpo-interface-quality-criteria
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-interface-quality-criteria-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about tpo-interface-quality-criteria

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

FAQPage Schema
How do I evaluate UI quality before release?

Evaluate each screen against twelve categories: clarity, task completion, consistency, accessibility, visual hierarchy, content, forms, responsiveness, performance, error recovery, data display, and security. Assign a verdict of Pass, Pass with minor issues, Fail, or Blocked, then record results in the scorecard.

What accessibility checks should a product interface pass?

The interface must support keyboard navigation, logical focus order, visible focus states, sufficient contrast, labeled form controls, field-connected error messages, and meaningful headings. Color alone must not communicate status, and custom widgets must mimic native behavior.

When should a release be blocked for UI quality issues?

Block release when the main task cannot be completed, critical accessibility failures exist, data loss can occur without warning, permissions are incorrect, sensitive data is exposed, core error states are missing, mobile layout is broken, or required legal disclaimers are absent.

What web performance targets should an interface meet?

The suggested targets are LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less. Interfaces must also show loading states for slow operations and avoid unexpected layout shifts.

What are the limitations of checklist-based UI review?

A checklist review cannot replace real user testing or automated accessibility audits, and it depends on the reviewer having complete requirements, designs, and implementation details. When those inputs are missing, the correct verdict is Blocked rather than Pass or Fail.