redesign
Redesign existing interfaces to premium quality while preserving product goals and functional behavior.
How do I install this agent skill?
npx skills add https://github.com/arjunkshah/design-skill --skill redesignIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The redesign skill implements a workflow for upgrading user interfaces using Tailwind CSS and specific utility packages. It utilizes npm for library installation and processes existing project code as input, which creates a standard surface for indirect prompt injection.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Redesign
Use this command when a product already exists and needs a stronger layout, visual system, and interaction polish.
Implementation Default
Default to Tailwind CSS for redesign output.
- Use Tailwind utility classes for all visual updates unless the user explicitly requests another styling system.
- Preserve existing framework/runtime, but move styling decisions toward Tailwind by default when feasible.
UI Library Access
Allowed reference libraries:
- UIverse
- FlyonUI (
https://flyonui.com/) - daisyUI
Rules:
- use libraries as accelerators, not as full-page templates
- refactor and mutate library components to fit product semantics and brand direction
- avoid repeated stock patterns from any single library
- pair library usage with invented components when repetition risk is high
Pretext Integration
When redesigning existing UIs with text-overflow risk or unstable wrapping, use @chenglou/pretext to plan text layout before finalizing spacing and type scale.
- Install when needed:
npm install @chenglou/pretext - Use
prepare()+layout()to validate key text blocks at target widths (hero, cards, CTA rows, nav labels). - Use the measurements to choose safer width constraints and reduce overflow regressions across breakpoints.
- If the redesign depends on precise line rhythm, use
prepareWithSegments()+walkLineRanges()to compare alternatives and pick the strongest composition. - If the project is static HTML/CDN-only or no JS build step exists, skip pretext integration and handle wrapping with responsive CSS constraints instead.
- Do this silently; do not include user-facing "Note on Pretext" caveats unless asked.
Anti-Repetition Expansion (Required)
Redesign must not look like a cosmetic restyle of standard templates.
Rules:
- Build a broad candidate set across component and interaction types before choosing a direction.
- Replace repetitive card structures with differentiated component families (data cards, narrative blocks, comparison rows, proof strips, utility panels, etc.).
- Invent at least
2 new componentsfor each substantial redesign when current UI blocks are generic. - Invent at least
1 new animation patternwhen motion is requested, tied to user feedback or hierarchy. - Reject outputs where variation is only color, border radius, or font changes.
Redesign Diversity Quotas (Required)
For substantial redesigns, enforce:
- at least
6materially different section structures across the page - at least
3non-card primary content modules - at least
2newly invented components adapted to this product context - no single legacy pattern may dominate more than
25%of sections
If the redesign still resembles the original layout skeleton, escalate structural changes before finalizing.
Anti-AI-Look Redesign Gate (Required)
Reject the redesign if it reads as "template reskin".
Failure cases:
- mostly identical original layout with new colors/fonts only
- repeated stock cards replacing repeated stock cards
- unchanged section rhythm with minor surface edits
- motion limited to basic fade-ins without interaction logic
Minimum redesign bar:
- at least
3clearly new structural modules replacing generic legacy blocks - at least
2bespoke components unique to the product context - at least
1unique interaction pattern not present in the source UI
Component Invention Rules
When inventing components for redesign:
- derive from product semantics (workflow, trust signal, conversion step), not visual novelty alone
- define explicit states and responsive behavior
- ensure implementation remains maintainable in Tailwind class composition
- add motion only where it improves comprehension or feedback speed
Core Objective
Transform a current interface into a clearer, higher-quality, more intentional design without breaking user flows.
Working Method
- Audit the current UI first:
- identify hierarchy failures, spacing inconsistencies, weak composition, and generic patterns
- detect interaction pain points and missing feedback states
- list what must stay stable (flows, core IA, key copy, business constraints)
- Define a redesign direction:
- choose a clear visual thesis and layout archetype
- strengthen typography, section rhythm, and contrast
- improve component consistency and responsive behavior
- Implement safely:
- preserve functionality and navigation logic unless explicitly asked to change it
- avoid regressions in forms, states, and accessibility
- apply motion where it improves clarity and feedback, not decoration
- Validate quality:
- verify desktop and mobile behavior
- check reduced motion behavior if animations are added
- confirm the redesign is materially better, not just stylistically different
Constraints
- Do not ship generic “safe SaaS” defaults.
- Do not remove critical information architecture without reason.
- Do not trade usability for visual novelty.
- Keep performance practical for the target context.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/arjunkshah/design-skill/redesign">View redesign on skillZs</a>