better-interface

Orchestrates cross-discipline interface reviews across accessibility, layout, writing, typography, color, and UI polish.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill better-interface-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-interface
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/better-interface
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill better-interface-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a user interface consistently across accessibility, layout, copy, typography, color, and visual polish is hard to do in one pass, and findings often end up scattered, duplicated, or ranked by taste rather than evidence. This Skill consolidates those domain reviews into a single ranked, evidence-based report. ## Core Features & Use Cases - Cross-domain orchestration: Routes the interface through each better-* domain skill (accessibility, layout, writing, typography, colors, UI) and merges results into one ranked findings table capped at 15 findings. - Evidence-based severity ranking: Applies a shared HIGH/MEDIUM/LOW severity scale with explicit escalation triggers, such as missing accessible names, keyboard traps, contrast failures, and destructive actions without confirmation. - Change-scoped review handoff: Delegates branch, pull request, or uncommitted-change reviews to interface-review, then applies its own severity, ranking, cap, and verdict to introduced and regressed findings. - Use Case: Before shipping a new settings page, ask for an interface review and receive a coverage table per domain, a consolidated findings table with file:line citations and before/after fixes, verification results, and a Block or Approve verdict. ## Quick Start Review the interface of the current screen or flow across accessibility, layout, writing, typography, color, and UI polish, and give me a ranked findings report with a verdict.

Frequently Asked Questions about better-interface

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

FAQPage Schema
How do I review a UI for accessibility and design issues at once?▼

Run a cross-discipline interface review that routes the screen through accessibility, layout, writing, typography, color, and UI polish checks, then consolidates results into one ranked findings table with severity, location, and a before/after fix per row.

How to review a pull request for UI regressions?▼

Name the branch, pull request, or uncommitted changes in your request. The review is delegated to a change-scoped flow that resolves the diff, classifies findings as introduced, regression, or pre-existing, and applies severity and verdict only to introduced and regressed issues.

What severity levels does an interface review use?▼

Findings use HIGH, MEDIUM, and LOW. HIGH covers task blockers and escalation triggers like missing accessible names, keyboard-only failures, contrast violations, and destructive actions without confirmation. Triggers are never averaged down based on surface size.

What happens if a domain review skill is not available?▼

The missing domain is marked Not reviewed and named explicitly in the coverage table, and the review continues with the remaining domains. Its rules are never recreated from memory or substituted by a neighboring domain.

Does the interface review modify my code automatically?▼

No. Reviews are read-only by default and produce a report with findings, verification results, and a Block or Approve verdict. Source edits happen only when you also ask for the findings to be implemented, followed by re-verification.