agentleFS
Evan-Kim2028Evan-Kim2028/agent-skills/skills/frontend/product-ui-craft/SKILL.md

product-ui-craft

Skill1 starsChanged 3 months agoMITView on GitHub

Raise product UI craft — spacing, hierarchy, density, radii, states, and restrained motion so chrome feels designed. Use only when polishing already structured UI ("works but feels off"), not as the default for any UI task. Prefer product-design when multi-step product UX/craft is unclear (it routes here). Prefer frontend-design for full FE feature implementation pipelines. Not for brand invention, marketing landings, design-system token definition (design-system), mobile sticky/sheet systems (mobile-product-ux), or ship/e2e proof (quality-check / browser-verify).

1 other project uses a version of this.

Adopted by

Most recently taken up by

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:

    After design-system constraints are clear

    line 37
  2. Distinctive:

    Prefer a single scale (4/8 or project tokens)

    line 49
  3. Distinctive:

    Prefer progressive disclosure over walls of equal-weight controls

    line 63
  4. Distinctive:

    Prefer one orchestrated moment over many micro-wiggles

    line 84
  5. Distinctive:

    Use as self-instructions when iterating:

    line 91

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

Product UI craft

Job: Turn working UI into refined product UI without changing brand identity.

Sources (attribution)

  • Product-mode craft ideas aligned with community skills such as Impeccable (Paul Bakaus) — especially separating product density from brand/marketing maximalism, and directional polish passes (quieter / bolder mental model).
  • Micro-detail checklists in the spirit of Make Interfaces Feel Better (jakub.kr / UI polish principles): spacing, type, alignment, hierarchy, radii, subtle motion.
  • Classic product design craft (scanability, grouping, consistent rhythm) — applied as agent checklists, not a redesign brief.

This skill is original synthesis for agents; it is not a vendor dump of those repos.

When to load

  • “Looks fine but cheap / uneven / sparse / noisy”
  • Chat shells, toolbars, filter bars, tables, empty states
  • After design-system constraints are clear

Craft pass (run in order)

1. Hierarchy

  • One primary action per region
  • Type steps: page title → section → body → meta (mono for numbers if system says so)
  • Don’t bold everything; don’t mute the primary metric

2. Spacing rhythm

  • Prefer a single scale (4/8 or project tokens)
  • Related items: tighter; unrelated groups: looser
  • Kill accidental 1-off gaps that break the grid

3. Alignment

  • Columns share edges; icons and labels share baselines
  • Trailing numbers/tabular figures when comparing prices
  • Sticky headers align with scroll body, not “almost”

4. Density

  • Product data surfaces: prefer information density over marketing whitespace
  • Collapse chrome before shrinking type below readable
  • Prefer progressive disclosure over walls of equal-weight controls

5. Surfaces & radii

  • Consistent elevation language (flat panels vs glossy controls if defined)
  • One radius family; don’t mix pill + sharp + random 10px
  • Borders: prefer token borders over heavy shadows for data UI

6. States

For each interactive/async region:

StateMust have
LoadingSkeleton/spinner + aria-busy on container
EmptyWhat & next action
ErrorRecoverable message + retry if applicable
SuccessStable layout (no jump)

7. Motion

  • Prefer one orchestrated moment over many micro-wiggles
  • 150–300ms transitions for UI chrome
  • Honor prefers-reduced-motion
  • Don’t animate layout of dense tables unless essential

8. Directional polish (optional pass names)

Use as self-instructions when iterating:

PassDo
QuieterReduce borders, shadows, competing accents
BolderStrengthen primary CTA/metric only
TighterReduce vertical waste in lists/toolbars
ClearerLabels, contrast, grouping

Anti-patterns

  • “Polish” that changes brand fonts/colors
  • Decorating every card with gradients and glow
  • Equal visual weight on 8 actions
  • Hover-only affordances on mobile-critical controls

Hand off

NeedNext skill
Tokens/components wrongdesign-system
Phone sticky/gesturesmobile-product-ux
A11y/focusweb-quality
Prove pixelsbrowser-verify

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.