better-interface

Coordinates six domain skills to review interfaces and produce one prioritized findings report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a screen or flow across accessibility, layout, writing, typography, color, and visual polish often produces six disconnected audits with duplicated or contradictory findings. This Skill orchestrates all six better-* domain skills into a single consolidated review with shared severity, evidence requirements, and a clear verdict. ## Core Features & Use Cases - Cross-Domain Orchestration: Loads better-accessibility, better-layout, better-writing, better-typography, better-colors, and better-ui in a fixed order, letting each own its rules while this Skill owns consolidation. - Quick and Full Modes: Quick mode caps findings at 5 and reports only HIGH and MEDIUM issues on the primary path; full mode covers all states with a cap of 15. - Evidence-Based Findings: Every finding cites path/to/file:line with the current implementation, and systemic root causes are merged into a single row. - Use Case: Before shipping a new settings page, invoke a full interface review to receive one ranked findings table, a considered-but-rejected list, verification results, and a Block, Needs changes, or Approve verdict. ## Quick Start Run a full interface review of the checkout flow and consolidate findings from all six better-* domain skills into one prioritized report.

Frequently Asked Questions about better-interface

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

FAQPage Schema
How do I run a holistic UI review across accessibility, layout, and typography?▼

Invoke the better-interface skill with a screen, flow, or feature scope. It loads all six better-* domain skills in a fixed order, applies each owner's rules, and consolidates the evidence into one prioritized findings table with a final verdict.

What is the difference between quick and full interface review modes?▼

Quick mode inspects the primary user path and highest-traffic states, reporting only HIGH and MEDIUM findings with a cap of 5. Full mode covers the entire requested scope including empty, loading, error, and narrow-width states, with a cap of 15 findings.

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

The missing domain is marked Not reviewed with the unavailable skill named, and the review continues with the remaining domains. The skill never recreates missing rules from memory or claims holistic coverage it did not perform.

Does an interface review modify my source code?▼

No, reviews are read-only by default. Source code is only edited when you explicitly ask to implement the findings, in which case the consolidated report becomes the change scope and verification is re-run afterward.

Why does a review report a domain as Clear or Not reviewed?▼

Clear means the domain was inspected with no actionable finding, while Not reviewed explains why coverage was impossible, such as a missing owning skill. This makes gaps in coverage explicit instead of implying uninspected surfaces were reviewed.