agentleFS
educlopezeduclopez/ui-craft/skills/ui-craft-minimal/SKILL.md

ui-craft-minimal

Skill441 starsChanged 3 months agoMITView on GitHub

Minimal / clean / Linear / Notion / Vercel / whitespace-heavy UIs. Locked knobs: CRAFT=8, MOTION=3, DENSITY=2. Monochrome + one accent, Inter/Geist, hairline borders over shadows. Trigger on: minimal, clean, Linear-like, Notion-like, Vercel-like, whitespace-heavy.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not re-ask these in Discovery.

    line 17
  2. Distinctive:

    Every pixel deliberate. When in doubt, cut it.

    line 28
  3. Very specific:

    All rules in ../ui-craft/SKILL.md apply.

    line 32
  4. Distinctive:

    No display serifs. No geometric display sans.

    line 42
  5. Distinctive:

    No card grids with more than 2 columns on desktop.

    line 56
  6. Distinctive:

    Default chrome = 1px hairline border, no shadow.

    line 60
  7. Very specific:

    Keep the reading list tight.

    line 78

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

UI Craft — Minimal

Pre-committed minimal style: editorial clean, Linear / Notion / Vercel. Whitespace is the composition. One accent, hairline borders, almost no motion.

Knobs (locked)

  • CRAFT_LEVEL = 8 — minimal aesthetics only work when executed precisely; Polish Pass is mandatory.
  • MOTION_INTENSITY = 3 — hover + modal enter/exit only. No scroll reveals, no page transitions, no stagger.
  • VISUAL_DENSITY = 2 — whitespace-heavy, 1-2 items per row, generous gutters.

Do not re-ask these in Discovery. Skip straight to accent + font confirmation if ambiguous.

Style anchors

  • Black or near-black type on white or near-white canvas. Monochrome + ONE accent.
  • Inter / Geist for body — never a display font.
  • Section padding 120-200px vertical, 40-80px gutters.
  • Hairline borders 1px solid oklch(92% 0.005 250) in place of shadows.
  • Typography is the hierarchy. No decorative gradients, patterns, or glass.
  • Single-column hero default. Asymmetry via one supporting element, not layout tricks.
  • Motion is punctuation, not spectacle.
  • Every pixel deliberate. When in doubt, cut it.

Base rules (inherited)

All rules in ../ui-craft/SKILL.md apply. This file overrides knob defaults and adds style-specific guidance below. The anti-slop and craft tests still apply in full.

Style-specific overrides

Typography

  • Body: Inter or Geist, 400 weight. UI emphasis: 500. Never 600/700 in body copy.
  • system-ui, -apple-system as fallback stack.
  • Headings: tracking-tight / -0.02em above 24px, 500 or 600 max.
  • text-wrap: balance on headings, text-wrap: pretty on paragraphs.
  • No display serifs. No geometric display sans. No mixing two sans families.

Color

  • Surface: oklch(99% 0 0) (light) / oklch(14% 0.005 250) (dark).
  • Text: oklch(18% 0.01 250) primary, oklch(46% 0.01 250) secondary.
  • Accent reserved for: primary CTA, active nav item, one key metric. That is it.
  • Borders: oklch(92% 0.005 250) light / oklch(24% 0.008 250) dark. No colored borders.

Spacing & layout

  • Section vertical: py-24 md:py-32 lg:py-40 (96 / 128 / 160px) minimum; 200px for hero on large screens.
  • Container: max-w-5xl typical; max-w-3xl for reading content.
  • One accent placement per viewport preferred; two max.
  • No card grids with more than 2 columns on desktop.

Borders & elevation

  • Default chrome = 1px hairline border, no shadow.
  • Elevation only for floating UI (menus, toasts, modals) — single soft ambient shadow, not layered.
  • Radius: 6px inputs, 8px cards, 12px modals. Keep the scale narrow.

Motion

  • Allowed: hover (opacity / border color, 120-150ms), modal + dialog enter/exit (180-220ms ease-out), focus ring.
  • Forbidden at this intensity: scroll-triggered reveals, stagger, page transitions, parallax, magnetic cursor, entrance choreography.
  • Any animation must honor prefers-reduced-motion.

Composition

  • Hero: left-aligned or centered headline, ONE supporting element (social proof line, screenshot, single chip). No floating badges, orbs, blobs.
  • Features: stacked rows with a single real visual each. No 3-up uniform icon grids even when tempting.
  • Nav: text-only links, current state = accent underline or weight 500. No pill backgrounds.

Reference files to read first

Keep the reading list tight. Load only these from ../ui-craft/references/:

  • layout.md — spacing, hierarchy, composition
  • typography.md — scale, readability, weight
  • color.md — monochrome scales, OKLCH, dark mode
  • accessibility.md — focus, contrast, keyboard

Skip dashboard.md, stack.md, sound.md unless explicitly relevant.

Anti-patterns for THIS style

  • Multiple accent colors. One accent, period.
  • Display serifs, geometric display sans, or mixing two sans families.
  • Decorative gradients, mesh backgrounds, noise overlays, glass panels.
  • Scroll-triggered reveals, stagger, page transitions — even "subtle" ones.
  • Uniform 3-column icon-heading-text feature grids.
  • Colored shadows or glows as affordances.
  • Dense layouts. If density feels right, this is the wrong variant — switch to ui-craft-dense-dashboard.
  • Pill backgrounds on nav links or buttons by default; prefer text + underline.
  • Section padding under 96px on desktop.

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.