Skip to content

EricTechPro/super-board / skills/ui-refine-loop

ui-refine-loop

Verified

FileKindSize
README.mdmarkdown3.6 KB
SKILL.mdskill md13.2 KB
references/checker-brief.mdmarkdown5.3 KB
references/config.mdmarkdown3.7 KB
references/finish-reviewer-brief.mdmarkdown1.5 KB
references/fixer-brief.mdmarkdown4.1 KB
references/grill.mdmarkdown2.6 KB
references/ledger.mdmarkdown2.0 KB
references/routing.mdmarkdown2.7 KB
references/rubric.mdmarkdown3.6 KB
references/taste.mdmarkdown3.7 KB
scripts/pr-shots.shexecutablescript3.8 KB
scripts/refine-setup.shexecutablescript10.2 KB
scripts/shoot.mjsexecutablescript10.8 KB

references/taste.md

View on GitHub
# Taste and direction

<!-- ui-refine-loop's neutral default. The grill (references/grill.md) copies this to the
project's taste file (refine.taste_file, default docs/design/taste.md) and fills in Direction.
Checkers and fixers read it before any playbook and cite rules by id (T3, S5). Replace or extend
the rules with the project's own; the best evidence for a rule is a UI commit the owner kept. -->

## Direction

One block per target, written by the grill. Until a block exists, the direction is "same look, just cleaner", and the open-ended rules at the end decide.

### <target>

- **Goal:** <what someone should be able to do or see>
- **Direction:** <calmer | bolder | denser | more spacious | same look, cleaner>
- **Keep:** <what must not change>
- **Avoid:** <what the fixers must not do>
- **Users:** <who, how often>
- **Reference:** <a product or page Eric likes, if any>

## Taste rules

| id | Rule |
|---|---|
| T1 | **Stay in the visual world.** Tokens, fonts, radii and shared components stay unless Direction names them. Refinement, not redesign. |
| T2 | **The primary task leads.** The first thing the eye lands on is what the visitor came for: the key figure, the main action, the content. |
| T3 | **One color per meaning, from tokens.** Two shades for one meaning is a bug, and so is a raw value next to a token. Color marks meaning, not decoration. |
| T4 | **One spacing scale, one type scale.** Every gap and size comes from the repo's scale. Related things sit closer than unrelated things. |
| T5 | **Aligned edges.** Content reads along a left edge. Labels, figures and actions line up across rows and sections. |
| T6 | **Both themes are real.** Dark mode gets the same hierarchy and contrast as light. Nothing disappears, glows or turns muddy. |
| T7 | **Both widths are real.** At 390 nothing clips, scrolls sideways or shrinks below a 24px tap target. Tables scroll or collapse inside themselves. |
| T8 | **Cut before you add.** Remove duplicate actions, redundant copy and decorative chrome before adding a section, a color or an animation. |
| T9 | **Honest copy.** Labels say what things do. Errors say what failed and how to fix it. Claims match the product. |
| T10 | **Reuse, then extend.** Use the repo's shared components and extend them by prop. A one-off copy is a problem even when it looks good. |

## Slop tells

Check every screenshot for these. Each hit is a problem citing the tell and the rule it breaks.

- **S1** A grid of equal tiles, each with an icon on top, a bold title and two lines of filler. (T2, T8)
- **S2** Gradient text, glow, shimmer or pulse rings used as decoration. (T3)
- **S3** Icon-in-a-tile section headers, or emoji as icons. (T8)
- **S4** Pastel washes, tinted banners and badges on everything. (T3, T8)
- **S5** Everything centered, with no edge to read along. (T5)
- **S6** Decorative backgrounds (blobs, mesh gradients) competing with the task. (T2)
- **S7** Fake-precise stats or unverifiable claims. (T9)
- **S8** Oversized padding and type on a working app page. (T4)
- **S9** Repeated chrome: two headers, a card inside a card, two CTAs saying the same thing. (T8)
- **S10** Dark mode as inverted light mode: pure-black surfaces, unreadable gray text, colors that lose meaning. (T6)

## When the brief is open-ended

For "make it better", "less AI slop" or "cleaner":

1. **Name the page type** (marketing, app or dashboard, settings, content) and write the visitor's job in one sentence.
2. **Check the slop tells** against every shot, in both themes and at both widths.
3. **Rank by what blocks the job.** Anything that pushes the task below the fold, or breaks a theme or a width, is P1. Off-taste chrome is P2. Polish is P3.
4. **Prefer cutting over adding** (T8). A problem that adds something must say which job it serves.
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: 322kUpdated 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: 197kUpdated 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: 197kUpdated 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: 197kUpdated Claude CodeCodexVerifiedInstall