agentleFS
Sign inStart free
SrejonKhanSrejonKhan/agent-skills/skills/enhance_ui/SKILL.md

enhance_ui

Skill3 starsChanged 2 months agoMITView on GitHub

Systematic UI enhancement and verification. Covers styling upgrades, responsiveness, and rigorous integrity testing to prevent code regression/loss.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 12 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants to improve the appearance/interaction of a UI or ensure that recent edits haven't broken the interface.

    line 8
  2. Very specific:

    Use view_file to analyze current styles.

    line 17
  3. Very specific:

    Use replace_file_content to apply styles.

    line 18
  4. Very specific:

    Use generate_image if needing to visualize a new design (optional).

    line 19
  5. Distinctive:

    Interaction: Add distinct hover/active states for all interactive elements.

    line 27
  6. Distinctive:

    Typography: Ensure hierarchy (headings vs body) and legibility.

    line 28
  7. Distinctive:

    Spacing: Check padding/margins to prevent "crowded" layouts.

    line 29
  8. Distinctive:

    Responsiveness: Verify layout behavior on mobile vs desktop.

    line 30
  9. Distinctive:

    Before finalizing any UI code change:

    line 34
  10. Distinctive:

    Completeness: ensure large files weren't truncated.

    line 37
  11. Distinctive:

    Event Listeners: Ensure button clicks/inputs still trigger their attached JS functions.

    line 38
  12. Distinctive:

    UI Test: Do key elements (buttons, forms, modals) appear as expected?

    line 43
  13. Distinctive:

    When executing enhancements, enforce these additional standards:

    line 53
  14. Distinctive:

    Accessibility (a11y): Ensure all interactive elements have visible focus states for keyboard navigation.

    line 55
  15. Distinctive:

    Performance Impact: Ensure visual enhancements (like heavy animations or background blurs) do not negatively impact Core Web Vitals (e.g., …

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Enhance UI & Verification

Use this skill when the user wants to improve the appearance/interaction of a UI or ensure that recent edits haven't broken the interface.

Inputs

  • Target Component/Page: The specific file or UI section to enhance.
  • Goals: Specific improvements (e.g., "Add hover states").

Tooling Strategy

  • Use view_file to analyze current styles.
  • Use replace_file_content to apply styles.
  • Use generate_image if needing to visualize a new design (optional).

Workflow

1. Visual Polish & UX

For the target UI component/page:

  • Interaction: Add distinct hover/active states for all interactive elements.
  • Typography: Ensure hierarchy (headings vs body) and legibility.
  • Spacing: Check padding/margins to prevent "crowded" layouts.
  • Responsiveness: Verify layout behavior on mobile vs desktop.

2. Integrity Checks (The "Anti-Regression" Filter)

Before finalizing any UI code change:

  • Code Block Check: Explicitly verify that no existing logic or code blocks were accidentally removed.
  • Completeness: ensure large files weren't truncated.
  • Event Listeners: Ensure button clicks/inputs still trigger their attached JS functions.

3. Testing Suite

  • Smoke Test: Does the code compile/render without immediate errors?
  • UI Test: Do key elements (buttons, forms, modals) appear as expected?
  • Responsive Check: Does it break when the viewport shrinks?

4. Output

  • Apply the enhancements.
  • Report: "Applied [Styles]. Verified [Integrity Checks]. Confirmed no code loss."

Advanced UI Verification (Pro-Max Guidelines)

When executing enhancements, enforce these additional standards:

  • Accessibility (a11y): Ensure all interactive elements have visible focus states for keyboard navigation. Verify semantic HTML and ARIA labels.
  • Performance Impact: Ensure visual enhancements (like heavy animations or background blurs) do not negatively impact Core Web Vitals (e.g., preventing Cumulative Layout Shift).
  • Micro-interactions: Beyond static hover states, add subtle transitions (e.g., transition-all duration-200) for premium feel.

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.

Check your setup, free