redesign-skill
Skill1 starsChanged 7 months agoMITView on GitHub
UI audit and upgrade skill. Analyzes existing interfaces for design problems (spacing, contrast, hierarchy, motion, consistency) and provides structured fixes. Use during QA phase or when iterating on existing products. Source: Leonxlnx/taste-skill.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- juandelossantos/another-agent-skillstheir own version, first seen Oct 17, 2026
- PIXARTSeu/Synapsetheir own version, first seen Sep 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- PIXARTSeu/Synapse★ 9same name
- juandelossantos/another-agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- accessibilitySkill
- agent-evalSkill
- agentic-engineeringSkill
- ai-regression-testingSkill
- api-designSkill
- atomic-planningSkill
- backend-patternsSkill
- coding-standards-eccSkill
- context-engineeringSkill
- frontend-patternsSkill
- git-worktreesSkill
- langchain-dependenciesSkill
- langchain-fundamentalsSkill
- langchain-middlewareSkill
- langchain-ragSkill
- langgraph-fundamentalsSkill
- langgraph-persistenceSkill
- minimalist-skillSkill
- output-skillSkill
- security-scanSkill
- ship-architectSkill
- ship-autoSkill
- ship-bugfixSkill
- ship-deploySkill
- ship-discoverSkill
- ship-executeSkill
- ship-finish-branchSkill
- ship-newSkill
- ship-planSkill
- ship-researchSkill
- ship-resumeSkill
- ship-reviewSkill
- ship-settingsSkill
- ship-specSkill
- ship-statusSkill
- ship-testSkill
- ship-worktreeSkill
- soft-skillSkill
- systematic-debuggingSkill
- taste-skillSkill
- test-driven-developmentSkill
- two-stage-reviewSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
When reviewing an existing UI for design quality.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Redesign Skill — UI Audit and Upgrade
When to use
When reviewing an existing UI for design quality. Used by the QA phase (ship-test) or manually when iterating on a product's visual quality.
Audit checklist
1. Spacing audit
- Is spacing consistent? (same gaps between similar elements)
- Is there a spacing scale being followed? (4/8/16/24/32 or similar)
- Are there cramped areas? (elements too close together)
- Are there orphaned elements? (floating with too much space around them)
2. Color audit
- Is there a defined palette? (or are colors ad-hoc?)
- Contrast ratio meets WCAG AA? (4.5:1 for text, 3:1 for large text)
- Is color used consistently? (same color = same meaning everywhere)
- Too many colors? (more than 5-7 indicates palette bloat)
3. Typography audit
- Is there a type scale? (consistent sizes, not random px values)
- Is hierarchy clear? (can you tell headings from body from captions at a glance?)
- Line length appropriate? (45-75 characters for body text)
- Line height appropriate? (1.4-1.6 for body)
4. Layout audit
- Is there a grid? (or are elements positioned arbitrarily?)
- Is alignment consistent? (all left-aligned, or intentionally mixed?)
- Does the layout work on mobile? (responsive breakpoints)
- Are cards/containers consistent in padding and radius?
5. Motion audit
- Are animations meaningful? (convey state change, not just decoration)
- Are durations consistent? (same type of animation = same timing)
- Is prefers-reduced-motion respected?
- Any janky animations? (layout thrashing, jumpy transitions)
6. Consistency audit
- Same element styled the same way everywhere? (buttons, inputs, cards)
- Same interaction pattern everywhere? (click, hover, focus states)
- Component reuse? (or are there one-off implementations of the same pattern?)
Output format
For each issue found, report:
- Location: Which page/component
- Problem: What's wrong (with screenshot or description)
- Fix: Specific CSS/JSX change to make
- Severity: Critical (breaks usability) / Warning (looks unprofessional) / Note (polish opportunity)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.