agentleFS
converge-ai-labsconverge-ai-labs/agent-foundation/.agents/skills/uiux-polish/SKILL.md

uiux-polish

Skill1.3k starsChanged 4 days agoApache-2.0View on GitHub

Build and refine frontend pages and interactions with strong visual taste, proactive polish, and lightweight iteration. Use for UI implementation and visual or interaction improvements.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about converge-ai-labs/agent-foundation

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Be proactive in judgment and lightweight in execution: Look and adjust as you build.

    line 10
  2. Distinctive:

    Follow the design reading path in the repository guide.

    line 12
  3. Distinctive:

    Consider the complete affected interaction, including its natural entry points and important states.

    line 13
  4. Distinctive:

    Keep validation proportional under CONTRIBUTING.md.

    line 15
  5. Distinctive:

    Put accepted reusable visual decisions in their shared or product design owner and recurring implementations in shared components.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UI/UX Polish

Exercise visual taste and own the finished result. Working functionality and assembled components are not enough. Notice awkward proportions, weak hierarchy, inconsistent spacing, poor alignment, distracting colors, and unclear interactions. Resolve those problems yourself within the affected page or flow; do not wait for the user to identify them. Deliver a coherent, refined interface. Polish means purposeful choices, not more decoration.

Be proactive in judgment and lightweight in execution. Look and adjust as you build. Avoid lengthy plans, separate acceptance exercises, and repeated polish cycles with no meaningful improvement. Ask only when a real product tradeoff or visual direction needs the user's decision.

  • Follow the design reading path in the repository guide. Reuse shared components, but judge their composition in the actual page rather than assuming reuse guarantees quality. Product-specific dimensions and interaction patterns do not automatically transfer between Console and Harness.
  • Consider the complete affected interaction, including its natural entry points and important states. Do not implement only the spot highlighted in a screenshot or expand into unrelated redesigns.
  • Open the actual page, assess its overall hierarchy and details, and fix obvious rough edges before handing it back. Check additional states or viewport sizes when they could reveal a relevant problem; do not turn every small change into an exhaustive audit.
  • Keep validation proportional under CONTRIBUTING.md. For visual changes, prioritize the rendered result; for behavior changes, verify the affected behavior. Reuse applicable successful checks. Do not default to repeated full-repository tests or add tests that merely mirror styling.
  • Put accepted reusable visual decisions in their shared or product design owner and recurring implementations in shared components. Remove superseded rules and repair incoming links. Keep local exceptions local; do not accumulate a new permanent rule for every adjustment.

Work directly toward a polished result and a prompt handoff. State what changed and any material validation limitation briefly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.