agentsclimarketplace
Sign in

Frontend ui polish

Skill jukrap/ai-agent-playbook/skills/quality/frontend-ui-polish

Use when refining visible frontend UI surfaces, responsive layout, interaction states, visual hierarchy, or production polish within existing product intent.From its SKILL.md

Install
npx -y skills add jukrap/ai-agent-playbook --skill frontend-ui-polish

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 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.0 KB, 162 tokens by cl100k_base, as published. Nobody here has run it

Frontend UI Polish

Primary route: frontend/ui-polish.

Refine visible UI so it works well in the actual product context.

Workflow

  1. Inspect the existing screen, nearby components, design system, tokens, CSS conventions, and target audience.
  2. Identify the workflow the user needs to complete, then improve hierarchy, spacing, layout stability, state coverage, and responsive behavior around that workflow.
  3. Preserve the repository's style policy. Use style-policy-selection if the styling convention is unclear or contested.
  4. Avoid decorative redesign unless the user asks for a new visual direction.
  5. Verify changed surfaces with rendered UI or browser evidence when possible.

Reference

Read references/frontend-ui-polish-checklist.md for detailed UI polish criteria and verification guidance.

What ships with it: 1 file

2.0 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most design frontend skills give in 162 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • identify the target workflow
  • improve hierarchy spacing and layout
  • improve state coverage and responsive behavior
  • preserve the repository style policy
  • use style-policy-selection if convention is unclear

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,696. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.