UI improvement audit: evidence-backed design reviews
Audit a product surface against its own design system with a contract-runtime-correction proof gate and self-contained fix plans — read-only on your source
- What
- Audit a product surface against its own design system with a contract-runtime-correction proof gate and self-contained fix plans — read-only on your source
- Cost
- Free
- Needs
- a product codebase to audit; the skill is read-only — it never modifies product source, it only writes plans under design-plans/
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @ibelick's read-only UI improvement audit: select one coherent product surface, reconstruct the design system that actually governs it (tokens, primitives, documented decisions), then prove every finding through a contract-runtime-correction gate — a binding design decision, proof the implementation reaches the surface, and one deterministic correction — with falsification passes that delete anything unsupported; reports stop at three findings and only turn user-selected findings into self-contained implementation plans under design-plans/. By @ibelick, listed here with credit to its creator. Honest caveats: strictly read-only on product source (never modifies it), writes plans only; no finding preferred over an unsupported one; discards accessibility/ARIA findings unless explicitly requested; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a product codebase to audit; the skill is read-only — it never modifies product source, it only writes plans under design-plans/ Install "UI improvement audit: evidence-backed design reviews" for me. It teaches the agent to audit one product surface against its own design system, prove findings through a contract-runtime-correction gate, and write self-contained implementation plans for user-selected fixes — strictly read-only on your source. Repository: https://github.com/ibelick/ui-skills/blob/main/skills/improve-ui/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "improve-ui". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing to configure — point it at a product surface when invoking it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.