Downloads contain the instructions shown here. Use the install command for the complete skill.

Improve UI

Audit one coherent product surface against the system that actually governs it. Preserve the product's identity, reuse existing owners, and prefer no finding to an unsupported one. Write plans only for changes the user selects; another agent executes them.

Boundaries

Never modify product source. Create or edit files only under design-plans/.
Do not install dependencies, run formatters, commit, push, or otherwise mutate the working tree.
Do not update design documentation. Record accepted documentation changes in the plan for its executor.
Use rendered evidence only when the user provides it or explicitly requests visual inspection.
Make every plan self-contained; its executor has no context from the audit or conversation.

1. Select the surface

Honor the user's scope. If the request is broad, select one deployable application and one coherent surface family representing a primary product task. State the selection; do not synthesize the whole repository into one product.

Start from the surface's routes and layouts. Trace the rendered path through compositions, shared components, variants, resolved tokens, and styles. Do not begin with a repository-wide search for inconsistencies.

A connection exists only when it is proven through rendering, imports, props, resolved configuration, CSS inheritance, or a generated artifact loaded by the surface. Shared names, similar tokens, repository proximity, and conceptual relationships do not establish a connection. Exclude other applications, previews, configurators, generated registries, legacy systems, and enterprise variants unless they participate in the traced path.

2. Reconstruct the local system

Check for DESIGN.md, repository guidance, and surface-local design documentation. Use a source only after proving it is current and governs the selected surface; drafts, proposals, migrations, and task lists describe future intent unless explicitly accepted and current. Absence of design documentation is not a finding.

Inspect only the tokens, variables, themes, primitives, variants, and compositions relevant to the traced path. Resolve aliases and variants to their definitions. Classify an implementation as local or legacy only when the repository says so.

Record:

## Design language
- Audited surface:
- Design sources:
- Documented decisions:
- Governing owners and consumers:
- Explicit exceptions:

Write None documented under Explicit exceptions unless a cited source explicitly identifies the exception.

3. Prove findings

Before applying the proof gate, inspect every traced surface's user-facing labels, active-state presentation, responsive branches, and sibling variants for internal contradictions. Treat the results only as candidates.

# Improve UI Audit one coherent product surface against the system that actually governs it. Preserve the product's identity, reuse existing owners, and prefer no finding to an unsupported one. Write plans only for changes the user selects; another agent executes them. ## Boundaries - Never modify product source. Create or edit files only under `design-plans/`. - Do not install dependencies, run formatters, commit, push, or otherwise mutate the working tree. - Do not update design documentation. Record accepted documentation changes in the plan for its executor. - Use rendered evidence only when the user provides it or explicitly requests visual inspection. - Make every plan self-contained; its executor has no context from the audit or conversation. ## 1. Select the surface Honor the user's scope. If the request is broad, select one deployable application and one coherent surface family representing a primary product task. State the selection; do not synthesize the whole repository into one product. Start from the surface's routes and layouts. Trace the rendered path through compositions, shared components, variants, resolved tokens, and styles. Do not begin with a repository-wide search for inconsistencies. A connection exists only when it is proven through rendering, imports, props, resolved configuration, CSS inheritance, or a generated artifact loaded by the surface. Shared names, similar tokens, repository proximity, and conceptual relationships do not establish a connection. Exclude other applications, previews, configurators, generated registries, legacy systems, and enterprise variants unless they participate in the traced path. ## 2. Reconstruct the local system Check for `DESIGN.md`, repository guidance, and surface-local design documentation. Use a source only after proving it is current and governs the selected surface; drafts, proposals, migrations, and task lists describe future intent unless explicitly accepted and current. Absence of design documentation is not a finding. Inspect only the tokens, variables, themes, primitives, variants, and compositions relevant to the traced path. Resolve aliases and variants to their definitions. Classify an implementation as local or legacy only when the repository says so. Record: ```markdown ## Design language - Audited surface: - Design sources: - Documented decisions: - Governing owners and consumers: - Explicit exceptions: ``` Write `None documented` under `Explicit exceptions` unless a cited source explicitly identifies the exception. ## 3. Prove findings Before applying the proof gate, inspect every traced surface's user-facing labels, active-state presentation, responsive branches, and sibling variants for internal contradictions. Treat the results only as candidates. A finding is in scope only when its correction primarily changes visual presentation, interface copy, layout, component styling, or conformance to a documented design rule. If the correction primarily changes whether product behavior works, reject it. Search results, repetition, and implementation differences produce candidates, not findings. Keep a candidate only when all three proofs exist: 1. **Contract** — Cite a binding design decision for this property and scope, or a direct contradiction in user-facing presentation or content within the same task. “Prefer,” “generally,” names, omissions, repetition, and absence of an exception do not establish a contract. 2. **Runtime** — Prove that the cited owner, value, or behavior reaches the affected surface through the traced runtime path. Do not compare separate ownership layers or lifecycle states. 3. **Correction** — State one change required by the evidence. If it depends on an existing token, variant, primitive, or exemplar, name it exactly. If the evidence cannot determine the correct choice, the intended condition is ambiguous, the proposal contains alternatives, or the correction requires inventing product intent, reject the candidate. Source can prove token, typography, color, spacing, layout, copy, component-variant, responsive-presentation, and explicit design-contract violations. It cannot turn functional behavior, state management, or interaction correctness into design findings. Hierarchy, prominence, density, clarity, discoverability, usability, and perceived coherence require rendered or user evidence. Discard accessibility and HTML/ARIA semantic findings unless the user explicitly requests them. Discard broken routes, redirects, data wiring, action failures, metadata, package API, performance, architecture, and code-quality findings unless the user requested them or a product-specific design contract governs them. Assign confidence only after all proofs pass. Reuse an existing owner when the evidence supports it; do not create a shared primitive from repetition alone. ## 4. Vet findings Before reporting, re-open every cited source and try to falsify each candidate. Delete it when: - The problem does not exactly match the cited implementation. - The rule does not govern that property and surface. - Counterevidence shows the difference is valid or deliberate. - The evidence supports multiple corrections. - The correction invents product intent. - Another finding describes the same root problem. Only findings that survive this pass may enter the table. ## 5. Report Order surviving findings by confidence, user impact, reach, and correction cost. Stop at three. Use this structure: ```markdown ## Design language - Audited surface: - Design sources: - Documented decisions: - Governing owners and consumers: - Explicit exceptions: ## Findings | # | Problem | Evidence | Proposed change | Scope | Confidence | | --- | --- | --- | --- | --- | --- | ## Improve first <Highest-leverage finding and why, or no supported recommendation.> ``` Evidence must establish the contract, runtime relationship, and deterministic interface consequence. Proposed change must contain one correction. Delete unsupported or overlapping rows before returning. Delete any finding that does not include every required column, including Confidence. Under `Improve first`, select one surviving finding with the strongest evidence and highest leverage. Never combine findings. If no candidate survives, write `No supported findings were found.` under `## Findings` and `No supported recommendation.` under `## Improve first`. If findings survive, stop and ask which to turn into plans. If the user already selected a finding or explicitly requested a plan for a described improvement, continue with that scope. If asked to fix or improve directly, offer a plan; never implement it. ## 6. Specify selected changes Read [references/plan-template.md](references/plan-template.md). Write one plan per selected change, never one per symptom. Before writing, re-open every cited source, record the current commit when available, identify exact reusable primitives and exemplars, and trace affected surfaces. Reconcile an existing plan instead of duplicating it. Do not invent values when the repository provides a token or component contract. Introduce a primitive only after proving why the existing system cannot express the decision and which consumers should share it. If asked to reconcile, recheck existing plans against current source and documented decisions; update stale evidence, affected surfaces, and status. --- ## Source and license Source: [ibelick/ui-skills](https://github.com/ibelick/ui-skills/tree/00db7d656719c399c091f3ea138c6f42a7fa4d98/skills/improve-ui). Author: ibelick. MIT License Copyright (c) 2026 Julien Thibeaut Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Instructions

Improve UI

Boundaries

1. Select the surface

2. Reconstruct the local system

3. Prove findings

4. Vet findings

5. Report

6. Specify selected changes

Source and license