← Back to Engineering & QA

Improve an existing frontend

Compare workflows for visual direction, focused polish, UX critique, or design-system consistency without rebuilding a working product.

Last meaningful review July 20, 2026

The job

You have a working web interface and want to make its presentation or usability more deliberate while preserving the existing product and codebase constraints.

Includedvisual polish of an implemented interface · UX critique tied to an existing page · design-system consistency

Not this pagegreenfield website creation · backend architecture · native mobile work

30-second route

01

The existing frontend needs a broad usability, accessibility, responsive-layout, or stack-aware improvement pass.

It combines a prioritized UI/UX rule set with stack detection and targeted searches.

Editorial confidence: high
Consider Ui Ux Pro Max
02

The interface works but needs a more intentional, non-templated visual direction and better product-specific copy.

Its two-pass visual plan and critique workflow is designed to avoid generic design defaults.

Editorial confidence: high
Consider Frontend Design
03

The main constraint is improving a product UI while respecting existing components, tokens, routing, and repeated-use workflows.

It explicitly starts from product constraints and existing frontend conventions.

Editorial confidence: high
Consider Frontend Design Direction
04

You need only a terse code-review report in file:line format against a pinned guideline set.

That is a narrower audit/reporting need than the selected implementation-oriented improvement skills.

Editorial confidence: medium
Adapt a review workflow around the supplied UI files and guideline set.

Before you install

Adapt one of the three selected skills to the existing project rather than build a new skill.

All three explicitly address existing or production UI improvement and have usable SKILL.md evidence; their different content hashes confirm they are distinct candidates.

Read the intervention guide →

Source-led comparison

What changes the choice

Facts are extracted from each selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.

SkillBest forActionEdits?Setup
Ui Ux Pro MaxBroad, evidence-backed UI/UX improvement with accessibility, responsive-layout, typography, color, interaction, and stack-specific guidance.Use it to assess the existing interface, query the relevant UX/design domains, then implement focused improvements within the detected stack.Prioritize accessibility, interaction, layout/responsiveness, typography/color, and feedback-state polish.Python 3.x; invoke the skill-local search script by its full path. Detect the project stack before requesting stack guidance. ↗Frontend DesignReshaping an existing interface toward a distinctive, deliberate visual direction while retaining clarity, responsive behavior, focus visibility, and coherent UX copy.Establish a compact, product-specific visual plan; critique it for generic defaults; then apply the revised plan to the existing UI.Refine palette, typography, layout hierarchy, one memorable but justified signature element, motion restraint, and interface wording.No runtime dependency or command is specified in the supplied source. ↗Frontend Design DirectionFocused product-UI polish that must preserve the current product workflow, existing design system, component conventions, and responsive constraints.Set purpose, audience, tone, memorable detail, and constraints before editing; use existing tokens/components first; verify the supplied review checklist after changes.Improve visual hierarchy, typography, color, spacing, responsive stability, high-signal motion, and product-first presentation.No runtime dependency or command is specified in the supplied source. ↗

Source notes

Inspect evidence and candidate limits 3 candidates

Why these candidatesEach candidate comes from tracked public sources and has a source-attributed adoption signal. This is a shortlist, not a catalogue or global ranking.

What this cannot establishWe read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.

01

Ui Ux Pro Max

Source ↗

Use it forBroad, evidence-backed UI/UX improvement with accessibility, responsive-layout, typography, color, interaction, and stack-specific guidance.

Avoid ifYou only want an opinionated visual-direction pass and do not need a searchable rules workflow.

ActionUse it to assess the existing interface, query the relevant UX/design domains, then implement focused improvements within the detected stack.

EditsPrioritize accessibility, interaction, layout/responsiveness, typography/color, and feedback-state polish.

SetupPython 3.x; invoke the skill-local search script by its full path. Detect the project stack before requesting stack guidance.

Inspect workflow and compatibility details

ContextDirect fit for improving the presentation and usability of an existing web interface; it explicitly covers UI review, consistency, and perceived-quality improvements.

OutputPrioritized design guidance and targeted domain/stack results to drive implementation.

ControlRule-prioritized and search-assisted.

Invocationpython "${CLAUDE_PLUGIN_ROOT}/.claude/skills/ui-ux-pro-max/scripts/search.py" "<query>" --domain <domain>

Install scopeskill-local Python search tool

Agent fitStrongest overall choice: the highest public-recognition signal among direct fits (SkillsMP Popular rank 2) plus a concrete, reproducible workflow.

Watch outFor an existing page, the documented design-system generation step is required only for new pages/projects; do not overwrite an existing persisted system without checking it first.

Source-visible capabilitiesExisting UI review and polishReviews UI for UX, accessibility, consistency, responsive behavior, and perceived usability/quality.explicit sourceStructured UX checksPrioritizes accessibility, touch/interaction, responsive layout, typography/color, motion, forms, and navigation.explicit sourceStack guidanceProvides implementation guidance across listed frontend stacks after stack detection.explicit source
Compatibilitywebdeclarednot runtime-testedReact / Next.js / Vue / Svelte / Tailwind / shadcndeclarednot runtime-tested
Public signal2 /SkillsMP source-specificbest-overallux-and-accessibilitystack-awareexplicit source
02

Frontend Design

Source ↗

Use it forReshaping an existing interface toward a distinctive, deliberate visual direction while retaining clarity, responsive behavior, focus visibility, and coherent UX copy.

Avoid ifYou need a formal audit with file-and-line findings or a design-token-generation workflow.

ActionEstablish a compact, product-specific visual plan; critique it for generic defaults; then apply the revised plan to the existing UI.

EditsRefine palette, typography, layout hierarchy, one memorable but justified signature element, motion restraint, and interface wording.

SetupNo runtime dependency or command is specified in the supplied source.

Inspect workflow and compatibility details

ContextDirectly covers reshaping an existing UI and offers a two-pass plan-and-self-critique process suited to deliberate visual polish.

OutputA compact design plan followed by an implementation aligned to that plan.

ControlOpinionated visual direction with self-critique.

InvocationNot yet mapped from the source.

Install scopeNot yet mapped from the source.

Agent fitBest alternative for stronger aesthetic authorship. It is also highly recognized among direct fits (SkillsMP Popular rank 6).

Watch outIts guidance is intentionally aesthetic and directional; pair it with project-specific accessibility or code-review checks when a detailed compliance audit is required.

Source-visible capabilitiesExisting UI reshapingGuides intentional visual design for building new UI or reshaping an existing one.explicit sourceTwo-pass design planningCreates a palette/type/layout/signature plan, critiques generic choices against the brief, then builds from the revised plan.explicit sourceUsable interface copyGuides clear, active, consistent UI language, including error and empty states.explicit source
Compatibilitywebdeclarednot runtime-testedexisting frontendappears compatiblenot runtime-tested
Evidence

The skill is for distinctive visual design when reshaping an existing UI.SKILL.md:lines 1-4 · inspected 2026-07-20 · high confidence

It prescribes a plan, a generic-default critique, and implementation from the revised plan.SKILL.md:lines 29-39 · inspected 2026-07-20 · high confidence

It requires responsive behavior, keyboard focus, reduced-motion consideration, and ongoing self-critique.SKILL.md:lines 41-43 · inspected 2026-07-20 · high confidence

It gives interface-copy guidance for controls, failures, and empty states.SKILL.md:lines 45-55 · inspected 2026-07-20 · high confidence

Public signal6 /SkillsMP source-specificvisual-directiondistinctive-designcopy-and-hierarchyexplicit source
03

Frontend Design Direction

Source ↗

Use it forFocused product-UI polish that must preserve the current product workflow, existing design system, component conventions, and responsive constraints.

Avoid ifYou need a deep searchable UX database or a formal code-guideline report format.

ActionSet purpose, audience, tone, memorable detail, and constraints before editing; use existing tokens/components first; verify the supplied review checklist after changes.

EditsImprove visual hierarchy, typography, color, spacing, responsive stability, high-signal motion, and product-first presentation.

SetupNo runtime dependency or command is specified in the supplied source.

Inspect workflow and compatibility details

ContextEspecially direct match where a working UI feels generic, flat, or mismatched and needs polish without a rebuild.

OutputA product-specific design direction, implementation guidance, and final review checklist.

ControlConstraint-aware, project-preserving design direction.

InvocationNot yet mapped from the source.

Install scopeNot yet mapped from the source.

Agent fitUseful substitute when preserving established frontend conventions matters most. It is a direct fit, with a lower public-recognition signal than the first two (SkillsMP Popular rank 20).

Watch outIt is a concise direction and checklist skill; the supplied source does not describe automated auditing or generated token artifacts.

Source-visible capabilitiesPolish a working generic UITargets existing interfaces that are flat, generic, templated, or mismatched to the audience.explicit sourcePreserve project conventionsUses existing components, tokens, icon libraries, and routing patterns before adding a new visual system.explicit sourceResponsive product UI reviewChecks scanning hierarchy, contrast, text fit, stable controls, responsive dimensions, motion, and repo conventions.explicit source
Compatibilitywebdeclarednot runtime-testedexisting design systemsdeclarednot runtime-tested
Public signal20 /SkillsMP source-specificexisting-system-firstproduct-uifocused-polishexplicit source

Still comparing?

Tell us the job, not just the skill names.

Request a task guide
Did this decision map help?