borghei/Claude-Skills / engineering/interface-refinement
interface-refinement
VerifiedRefine an existing interface with named commands (critique, polish, distill, typeset, colorize ...), a product and design context file, and a static detector of generic UI patterns. Use when UI looks generic, cluttered or unfinished.
references/craft-floor.md
View on GitHub# Craft floor
Read this immediately before any edit, including small ones. It is the minimum every refined
surface meets. The floor holds mechanics; it never picks the direction. The context file and the
owner's brief override every line here except those marked **refuse always**.
## Check on the built result
Run these together on one look at the rendered page (phone and desktop width), fix, then look
again. One batched look beats a screenshot after every tweak.
| Area | The check |
|------|-----------|
| Contrast | body and placeholder text 4.5:1; large text 3:1; icons, controls and focus rings 3:1. Secondary text on a coloured surface is tinted from that surface, never neutral grey. |
| Depth | shadows have a vertical offset and a soft blur; one elevation method per element (border or shadow, not a hairline border under a wide soft shadow on every card). |
| Spacing | tight inside groups, generous between groups; more space above a heading than below it; values from the scale. |
| Type | body measure 60-75 characters; obvious steps between roles; display tracking no tighter than -0.03em; real copy tested at every width, nothing overflows. |
| Motion | one authored moment at most; decelerating curves from an already-visible state; a reduced-motion path. |
| States | default, hover, focus-visible, active, disabled, loading, empty, error, success, long content. |
| Browser surfaces | themed text selection, caret, focus ring, scrollbars on scroll regions, link underline offset, tabular numerals in tables. Defaults here are the cheapest tell that a page was assembled rather than built. |
| Copy | the product's own terms; controls name their action; errors name the problem and the recovery. |
| Coverage | every requirement in the brief is present and findable within seconds. |
## Refuse by default
These are the category's defaults. The brief's own words can earn one back; reaching for one when
nothing asked for it means no decision was made. Recognising one means rewriting the element, not
softening it.
**Page scaffolds**
- Rows of same-size cards (icon, heading, two lines) as the structure of a page.
- Cards inside cards. **Refuse always.**
- The hero-metric block: a giant number, a small label, three supporting stats, an accent colour.
- A small tracked uppercase label above a heading (eyebrow, kicker). **Refuse always**: put the
information in the heading or the sentence below it.
- Section numbers (01, 02, 03) when the order carries no meaning.
- A modal for a task that needs neither interruption nor protected focus.
**Surface habits**
- Gradient-filled text.
- Glass blur as decoration rather than a specific overlay effect.
- A coloured stripe thicker than 1px down one side of a rounded card, list item or alert.
- Hard zero-blur offset shadows outside a deliberately brutalist world.
- Sparklines, progress rings and soft rounded boxes standing in for real content.
- Monospace as a costume for "technical" instead of for code, data and measurements.
- A bare system face as the display voice of a persuade or showcase page.
- Emoji or Unicode glyphs as the icon system. Icons are drawn, one family, one stroke.
- Light or dark theme chosen by category. Choose from the use scene: who, where, under what light.
- Decorative grid paper, repeating stripes, noise grain and sketchy hand-drawn SVG scenes.
- Colour palettes by reflex: violet-to-blue gradients, cyan on near-black, cream page grounds.
- Claims nobody can source: customer counts, logos, testimonials, benchmarks. Label illustrative
numbers as illustrative.
## After the floor
With every check passing, spend the remaining effort on what makes this product recognisable.
When torn between a safe refinement and a committed one that the brief supports, commit.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |