kasonye/ui-aesthetics-skill · Archived

ui-aesthetics

Raise frontend visual judgment for web interfaces with a bias toward refined product-grade composition, precise component craftsmanship, disciplined interaction states, controlled motion, and coherent depth systems.

First seen Apr 12, 2026

Installation

$ npx skills add kasonye/ui-aesthetics-skill --skill ui-aesthetics

Summary

  • Raise frontend visual judgment for web interfaces with a bias toward refined product-grade composition, precise component craftsmanship, disciplined interaction states, controlled motion, and coherent depth systems.
  • Use when generating, reviewing, or refactoring web UI that feels generic, cluttered, flat, over-styled, theatrically animated, visually imprecise, or AI-generated.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 381
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,815 B
  • docs SUMMARY.md 400 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 42 installs

SKILL.md

UI Aesthetics

Use this skill to improve visual judgment for web interfaces without inflating scope.

Core operating rules

  • Preserve the user's requested artifact scope and information density.
  • Improve hierarchy, spacing, and typography before decoration.
  • Prefer restrained neutrals, disciplined accents, and coherent state behavior.
  • Use depth, blur, glow, and motion only when they clarify hierarchy or interaction.
  • Diagnose first when a request mixes critique and rewrite.

Task routing

  1. Generation
  2. Review
  3. Refactor
  4. Component Polish
  5. State / Motion Refinement
  6. Depth / Lighting Refinement

How to use supporting files

Read these shared files first:

  • [core.md](../../../.shared/ui-aesthetics/core.md) for the condensed operating contract
  • [reference-map.md](../../../.shared/ui-aesthetics/reference-map.md) to choose the right detailed reference file
  • [usage.md](../../../.shared/ui-aesthetics/usage.md) for invocation patterns and expected output shape

Then open detailed files under ../../../references/ only when the task needs them.

Output contract

  • State the chosen route and intended visual thesis early.
  • Keep critique actionable and tied to hierarchy, trust, clarity, or interaction quality.
  • When rewriting, state whether the change is light polish, medium restructure, or full rebuild.
  • Keep solutions shippable and maintainable.