design-improve

Implements prioritized design fixes from audit findings with verification and reporting.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill design-improve-mjlike123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-improve
Source: https://github.com/Mjlike123/ui-prototype-workbench/tree/main/.agents/skills/monkren-design/skills/05-improve/design-improve
Command: npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill design-improve-mjlike123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design audits produce lists of issues, but turning those findings into actual code changes requires prioritization, authorization checks, and verification. This Skill converts review findings into concrete, verified fixes without scope creep. ## Core Features & Use Cases - Finding-to-Fix Mapping: Reads existing review reports (or runs a read-only five-dimension review first) and extracts each issue's location, impact, evidence, severity, and acceptance criteria. - Prioritized Implementation: Orders fixes P0 to P2, addressing structure, usability, and accessibility before visual consistency and polish, with each change traceable to an original finding. - Authorization & Escalation: Outputs a fix plan only when the user wants suggestions, modifies files only on explicit approval, and consults a design-decision advisor when fixes conflict or require large refactors. - Verification & Delivery: Runs the project's build, tests, and lint, re-checks contrast, focus, responsiveness, and states, then saves a report to .monkren/improvements/{project}-{date}/report.md. ## Quick Start Fix the P0 and P1 issues from my latest design review report and verify the changes with the project build and tests.

Frequently Asked Questions about design-improve

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

FAQPage Schema
How do I turn design review findings into actual code fixes?

Provide an existing review report and explicitly ask for fixes. The Skill extracts each issue's location, severity, and acceptance criteria, orders them P0 to P2, implements authorized changes, and verifies with the project's build and tests.

How are design fixes prioritized before implementation?

Fixes are sorted P0, P1, then P2. Structural, usability, and accessibility issues come first, followed by visual consistency, and finally detail polish. Every fix must map back to a specific original finding.

Can it generate a fix plan without modifying my files?

Yes. If you only ask for suggestions, it outputs a repair path without changing any files. File modifications happen only when you explicitly request fixing, improving, or implementing.

What happens when design fixes conflict or require large refactors?

When recommendations conflict, affect brand identity, or demand high-cost changes, the Skill consults a read-only design-decision advisor for a second opinion. It then implements only the parts you authorized with clear conclusions.

How are design fixes verified after implementation?

It runs the project's existing build, test, and lint commands, then re-checks for contrast, focus, responsive, and state regressions. If visual tooling is unavailable, it performs static checks and states the limitation.