01 / Existing frontend

← All task guides

Improve an existing frontend

Pick a skill based on what needs improvement: visual direction, a design-system pass, or a critique that leaves code untouched.

Last meaningful review July 13, 2026

The job

You have a working web interface. You want to make it clearer, more deliberate, and more useful without starting the product over.

Includedvisual polish · UX critique · design-system consistency

Not this pagebackend architecture · native mobile work · full product discovery

Fast route

01

You want a strong visual direction and implementation guidance.

Its declared workflow centers on a deliberate visual direction before implementation.

Consider frontend-design
02

You want a focused polish pass on a page that already works.

Its instructions are scoped to refinement rather than rebuilding the product.

Consider polish
03

You want feedback before any code is changed.

Its declared output is critique and prioritised observations.

Consider critique

Source-led comparison

What changes the choice

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

How to choose

Match the condition first.

Start with the fast route above. Then compare the candidate’s declared action, edit behaviour, context requirement and setup friction against the way you actually plan to work.

Why these candidates

Each candidate is selected from tracked public sources and has a visible, source-attributed adoption signal. We keep the shortlist small; this is not a catalogue or a global ranking.

Limits of this page

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

Candidate notes

01

frontend-design

Source ↗

Use it forEstablishing a bold visual direction while building or revising a web interface.

Avoid ifYou need critique only and do not want implementation direction.

ContextMedium

Outputunknown

Controlunknown

Agent fitunknown

Watch outDeclared behavior is source-linked, not independently tested.

EvidenceSKILL.md describes frontend design workflows and visual-direction constraints.

Public signal160,703 /GitHub repository starsexplicit source
02

polish

Source ↗

Use it forRefining an existing page’s visual details and presentation.

Avoid ifYour main issue is information architecture or codebase structure.

ContextMedium

Outputunknown

Controlunknown

Agent fitunknown

Watch outDeclared behavior is source-linked, not independently tested.

EvidenceSkill naming and workflow describe a polish-oriented pass.

Public signal46,133 /GitHub repository starsexplicit source
03

critique

Source ↗

Use it forFinding visual and UX issues before deciding what to change.

Avoid ifYou expect the agent to immediately implement a redesign.

ContextMedium

Outputunknown

Controlunknown

Agent fitunknown

Watch outDeclared behavior is source-linked, not independently tested.

EvidenceSkill naming and workflow position it as a review/critique step.

Public signal46,133 /GitHub repository starsexplicit source

Still comparing?

Tell us the job, not just the skill names.

Request a task guide