1. Habit
  2. Skills
  3. Improve UI skill
ibelick · 8K installs

Improve UI skill
Runs by itself, biweekly surface audit.

Proven UI fixes, planned for handoff.

Install the Improve UI skill and make it a habit: follow https://gethabit.dev/skills/ibelick/improve-ui.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

8K installs10K starsMIT licenceSource on GitHub ↗

Improve UI

by ibelick · 8K installs

The skill

The improve ui skill audits one product surface against its own design evidence, keeps only proven UI problems, and writes self-contained plans for another agent, for teams fighting design-system drift.

Only when you ask.

The habit

Proven UI fixes, planned for handoff.

↻ Runs by itselfbiweekly surface audit

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

biweekly surface audit. Runs in Claude Code routine.

  • ↻ biweekly surface audit
  • 0 10 1,15 * *

02

It checks its work

proof gate, your pick. If a check fails, it stops.

  • ✓no product source files changed
  • ✓every finding row has all columns including Confidence
  • ✓at most three findings reported
  • ✓plans exist only under design-plans/

03

It remembers

design plans folder. The next run reads it first: existing plans to reconcile instead of duplicating.

design-plans/

One run, step by step.
Then it stops.

Stop ruleStops after one surface and three findings per run.

  1. 01

    Select the surface

    Pick one coherent surface and trace its routes, layouts and components.

  2. 02

    Rebuild the system

    Find current design sources such as DESIGN.md and record the design language.

  3. 03

    Prove findings

    Keep a candidate only with contract, runtime and correction proof.

  4. 04

    Vet findings

    Reopen every source and delete candidates that fail, overlap or invent intent.

  5. 05

    Report

    Show up to three findings and one improve-first pick.

  6. 06

    Ask you

    Ask which findings should become plans.

  7. 07

    Write plans

    Write one self-contained plan per chosen change under design-plans/.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Improve UI skill helps.

Use it when

  • ✓ reviewing an interface for drift
  • ✓ preparing a design handoff
  • ✓ cleaning up UI without a redesign

Skip it when

  • – building a new design from scratch
  • – fixing broken product behavior

Questions

Improve UI skill, answered.

Does it change my code?

No. It is read-only on product source and only writes plans.

Why so few findings?

It keeps only findings that survive a strict proof and vetting pass, at most three.

How do I install the Improve UI skill?

Copy the prompt at the top into your agent. It installs the skill from ibelick/ui-skills and sets up the habit. Or run npx skills add ibelick/ui-skills --skill improve-ui.

Is the Improve UI skill free?

Yes. It is published under MIT. Habit is free too.

Improve UI. Now as a habit.

Install the Improve UI skill and make it a habit: follow https://gethabit.dev/skills/ibelick/improve-ui.md

  • Free
  • No account
  • Undo in one line

All ibelick skills →More design skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by ibelick, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.