improve-ui

Audit a product surface against its design system and write implementation plans for verified UI findings.

Updated May 5, 2026
One-click install
npx skills add https://github.com/josippapez/ai-setup --skill improve-ui-josippapez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-ui
Source: https://github.com/josippapez/ai-setup/tree/main/claude/plugins/better-design/skills/improve-ui
Command: npx skills add https://github.com/josippapez/ai-setup --skill improve-ui-josippapez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? UI reviews often produce vague, unsupported suggestions or accidental rewrites of a product's identity. This Skill audits one coherent product surface strictly against the design evidence that actually governs it, so every reported problem is backed by a contract, a runtime path, and a single deterministic correction. ## Core Features & Use Cases - Evidence-gated auditing: Traces routes, layouts, components, variants, and resolved tokens, then keeps only findings that pass contract, runtime, and correction proofs plus a falsification pass. - Read-only by design: Never modifies product source, installs dependencies, or commits; output is limited to a findings report and plan files under design-plans/. - Self-contained handoff plans: Writes one implementation plan per selected change using a structured template covering evidence chain, reuse, scope, validation, and stop conditions, so another agent can execute with zero prior context. - Use Case: Ask it to review your app's settings page for design-system drift; it returns a ranked table of at most three verified findings, then drafts an executor-ready plan for the one you pick. ## Quick Start Ask the agent to audit the settings page of the web app for design inconsistencies and prepare an improvement plan for the top finding.

Frequently Asked Questions about improve-ui

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

FAQPage Schema
How do I audit a UI for design system inconsistencies?

Select one coherent surface, trace its rendered path through components, variants, and resolved tokens, then check each candidate against a documented design contract. This Skill automates that workflow and reports only findings that survive contract, runtime, and correction proofs.

How to prepare a design handoff plan for another developer or agent?

Write one self-contained plan per selected change using the plan template: evidence chain, design decision, reusable tokens or components, exact changes, scope, validation steps, and stop conditions. The executor needs no context from the original audit.

Does this UI audit modify my source code?

No. The audit is strictly read-only on product source. It never installs dependencies, runs formatters, commits, or edits implementation files; it only creates or updates plan files under the design-plans/ directory.

What kinds of UI issues are out of scope for a design audit?

Functional bugs, broken routes, data wiring, performance, accessibility, and code-quality issues are discarded unless explicitly requested or governed by a design contract. Only visual presentation, copy, layout, styling, and documented design-rule violations qualify.

Why does the audit report no findings even when the UI looks inconsistent?

Repetition, naming similarity, or implementation differences are only candidates, not findings. Without a cited binding design decision, a proven runtime path, and a single evidence-determined correction, the candidate is rejected to avoid unsupported recommendations.