better-interface

Orchestrates cross-discipline interface reviews by consolidating findings from domain-specific review skills.

6.7k|239|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/jakubkrehel/skills --skill better-interface-jakubkrehel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-interface
Source: https://github.com/jakubkrehel/skills/tree/main/skills/better-interface
Command: npx skills add https://github.com/jakubkrehel/skills --skill better-interface-jakubkrehel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing an interface across accessibility, layout, writing, typography, color, and UI polish requires juggling multiple checklists, and findings often end up duplicated, unranked, or missing evidence. This Skill runs a single consolidated review that routes the interface to each domain skill, collects their evidence, and produces one ranked verdict. ## Core Features & Use Cases - Cross-domain orchestration: Delegates to six domain skills (accessibility, layout, writing, typography, colors, UI) in a fixed order and consolidates their findings into one severity-ranked table capped at 15 findings. - Evidence-based severity ranking: Applies a shared HIGH/MEDIUM/LOW scale with explicit escalation triggers, such as missing accessible names, keyboard traps, contrast failures, and destructive actions without confirmation. - Structured review output: Produces a scope and coverage table, a findings table with file:line citations and before/after fixes, verification results, and a final Block or Approve verdict. - Use Case: Before shipping a new settings page, ask for a full interface review. The Skill inspects every domain, cites exact code locations, proposes fixes in the project's own idiom, and returns a ranked report ending in a clear ship/no-ship verdict. ## Quick Start Review this screen 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?▼

Request an interface review scoped to a screen, flow, or feature. The review delegates to domain skills for accessibility, layout, writing, typography, color, and UI polish, then consolidates all findings into one severity-ranked table with a Block or Approve verdict.

What does the interface review report include?▼

The report contains a scope and coverage table per domain, a findings table with severity, file:line location, before/after fix, and rationale, plus a verification section listing checks run and a final verdict. Findings are capped at 15 and ranked by user impact.

Can this review uncommitted changes or pull requests?▼

No. Change-scoped reviews of branches, pull requests, or uncommitted work belong to the separate user-invoked interface-review skill, which resolves the diff scope and hands findings back for severity ranking and verdict.

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 review modify my code automatically?▼

No. Reviews are read-only by default. Source edits happen only when you also ask for the findings to be implemented, after which the relevant verification checks are re-run.