Redesign
Critique and improve the visual design of an existing UI component with concrete implementation guidance. Use when the user asks to redesign, restyle, reimagine, polish, or improve a component, screen, or interface, especially in React and Tailwind codebases.From its SKILL.md
npx -y skills add khairm/superset-windows-arm64 --skill redesignAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, as published. Nobody here has run it
Redesign
Inspect the real component and its surrounding layout before proposing changes. Reuse the repository's existing design tokens, primitives, and component conventions.
Respond in this order:
- Identify the component and file being redesigned.
- Name three concrete visual or interaction issues, such as hierarchy, spacing, contrast, alignment, responsiveness, or affordance.
- Propose specific layout, token, component, and Tailwind changes for each issue.
- Show a short before-and-after excerpt containing only the meaningful class or structure changes.
- If implementation was requested, make the changes and verify them using the repository's required UI workflow.
Keep the critique concise and grounded in the current code. Do not invent a new visual language when the repository already provides one.