You want a strong visual direction and implementation guidance.
Its declared workflow centers on a deliberate visual direction before implementation.
01 / Existing frontend
← All task guidesPick a skill based on what needs improvement: visual direction, a design-system pass, or a critique that leaves code untouched.
The job
Includedvisual polish · UX critique · design-system consistency
Not this pagebackend architecture · native mobile work · full product discovery
Fast route
Its declared workflow centers on a deliberate visual direction before implementation.
Its instructions are scoped to refinement rather than rebuilding the product.
Its declared output is critique and prioritised observations.
Source-led comparison
Facts are extracted from the selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.
How to choose
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
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.
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.
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.
Still comparing?