better-interface

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/squidllee/skills --skill better-interface-squidllee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-interface
Source: https://github.com/squidllee/skills/tree/main/better-interface
Command: npx skills add https://github.com/squidllee/skills --skill better-interface-squidllee

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 arrive as disconnected domain reports with no shared severity scale or verdict. This Skill consolidates those domain reviews into a single ranked findings table with evidence-backed citations and a clear Block or Approve verdict. ## Core Features & Use Cases - Cross-domain orchestration: Routes the interface through the better-accessibility, better-layout, better-writing, better-typography, better-colors, and better-ui skills, then consolidates their evidence into one ranked report capped at 15 findings. - Shared severity and escalation triggers: Applies one HIGH/MEDIUM/LOW scale, with automatic HIGH escalation for issues like missing accessible names, keyboard-inaccessible controls, contrast failures, or destructive actions without confirmation. - Evidence-based reporting: Requires every finding to cite path/to/file:line, show the current implementation, and propose the cheapest viable fix, with verification results separated from unverified checks. - Use Case: Ask for a review of a checkout flow before release. The Skill inspects each domain, consolidates systemic issues into single rows, and returns a verdict table showing exactly what blocks shipping. ## Quick Start Review the settings screen of this project across accessibility, layout, writing, typography, color, and UI polish, and give me a ranked findings table 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 web interface for accessibility and design issues?▼

Request a review of a specific screen or flow, and the Skill routes it through accessibility, layout, writing, typography, color, and UI polish domains. Findings are consolidated into one ranked table with file and line citations, severity ratings, and a Block or Approve verdict.

What makes a UI finding high severity in a design review?▼

HIGH severity applies to issues that block tasks, mislead users, or hide content, plus escalation triggers like controls without accessible names, keyboard-inaccessible paths, contrast failures, or destructive actions without confirmation. Triggers are never averaged down based on how minor the surface seems.

Can this review uncommitted changes or pull requests?▼

No, change-scoped reviews of branches, commits, or uncommitted work belong to the separate `interface-review` skill, which resolves the scope and classifies findings. This Skill handles screen and flow reviews and receives handoffs back from `interface-review`.

What happens if one of the domain review skills is missing?▼

The unavailable domain is marked `Not reviewed` and named explicitly, while the remaining domains proceed normally. The Skill never recreates missing domain rules from memory or claims coverage it did not perform.

Does the interface review modify my source code?▼

Reviews are read-only by default and produce a findings report without editing source files. If you also ask for implementation, the consolidated report becomes the change scope and relevant verification is re-run afterward.