Skip to content

Kartik-Doye/Ravengard-AI-Recruiter / .agents/skills/polish

polish

Verified

Refines a product interface while preserving its visual language, improving hierarchy, typography, spacing, density, states, responsiveness, keyboard use, focus, motion, and accessibility. Use when the user asks to make an existing web or app interface look intentional and professional.

FileKindSize
SKILL.mdskill md14.4 KB
references/audit.mdmarkdown3.9 KB
references/research.mdmarkdown3.8 KB

references/audit.md

View on GitHub
# UI audit checklist: walk on the real rendered UI

Audit with screenshots/running app, not by reading code. For each
dimension: what good means, and the tell that it's bad.

## Structure

- **Layout**: alignment is deliberate (a grid, not an accident); related
  things sit together; nothing floats without a reason. Tell: every page
  is a centered max-width column regardless of content.
- **Spacing rhythm**: one scale (4/8/12/16/24/32/48…), used
  consistently. Tell: seven different gaps between cards.
- **Hierarchy**: the eye lands on the primary thing first: one primary
  action per view, headline → subhead → content in descending weight.
  Tell: five elements all shouting at font-weight 700.
- **Density**: appropriate to the audience: tools dense, marketing airy.
  Tell: a data dashboard with landing-page whitespace.

## Surfaces

- **Typography**: use the smallest coherent family and type scale supported by
  the product; evaluate line length with real content and viewports.
- **Color**: role-based palette; verify the applicable WCAG 2.2 contrast
  criterion and its exceptions; color is not the only signal.
- **Dark theme**: contrast and elevation re-checked in dark mode, never
  inverted: text still meets AA, surfaces lift (lighter, not transparent),
  brand accents survive. Tell: pure-inverted palette where shadows vanish
  and the primary turns neon.
- **Component consistency**: same component = same look everywhere;
  buttons don't have four radii. Tell: every card has slightly different
  corner rounding.
- **Iconography**: one icon set, consistent weight, icons clarify rather
  than decorate.

## Behavior

- **States on everything interactive**: hover, focus-visible, active,
  disabled, loading; then the content states: empty, error, success.
  Tell: buttons with no hover and no disabled, tables with no empty state.
- **Loading**: use measured latency and user expectations to choose progress
  treatment; never a frozen UI; optimistic
  only where rollback is safe. Tell: a blank white flash where a table
  will be.
- **Empty states**: say what's empty, why, and what to do next (with an
  action). Tell: "No data." and nothing else.
- **Stress Testing (Data Scaling)**: UI must survive real data constraints, not just the happy path. Tell: a layout that breaks when a title is 100 characters long, or a list that assumes there will only ever be 3 items.
- **Errors**: human-readable, actionable, placed near the field/area
  they belong to. Tell: "Something went wrong" as the only error message
  in the app.
- **Motion**: purposeful (entrance, feedback, transition), tuned to the
  interaction, and respects `prefers-reduced-motion`. Tell: everything
  bounces because it can.

## Reach

- **Responsive**: real breakpoints by content, not three magic widths;
  no avoidable horizontal scroll on mobile; target sizes follow applicable
  accessibility requirements and product context; tables get a
  mobile strategy (not just overflow-scroll).
- **Mobile behavior**: primary action reachable; modals usable; keyboard
  doesn't cover the focused input.
- **Accessibility in design (A11y)**: focus indicators designed (not removed),
  information not carried by color alone, hit areas generous, motion
  optional.
- **Semantic Structure**: layout uses correct HTML semantics (`<nav>`, `<main>`, `h1`-`h6` in order) rather than `<div>` soup. Tell: a visually massive title that is actually a `<p>` tag.

## Web performance as design

- **LCP**: hero image sized/formatted for its slot (not a 4MB PNG);
  fonts subsetted with display swap.
- **CLS**: dimensions reserved for images/embeds; no late-loading
  banners pushing content.
- **INP**: interactions stay responsive; no giant synchronous work on
  click.

Fix order: structure first (layout/hierarchy/spacing), then surfaces
(type/color/components), then behavior (states), then polish (motion).
Structure errors make surfaces meaningless.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall