Skip to content

ui-craft

Use when designing UI aesthetics, generating style guides, modernizing dated interfaces, or exploring visual direction. Also use for color palette generation, typography pairing, and component style samples. The “vibes skill” — creative direction before implementation.

ModelSource
sonnetpack: frontend
Full Reference

Creative direction, aesthetic exploration, and visual system generation. Use this skill before writing a single line of CSS — it finds the right vibe first, then produces implementation-ready tokens and component samples. Works across the full aesthetic spectrum from brutalist to editorial to maximalist. Never defaults to generic corporate SaaS gray.

┏━ 🎨 ui-craft ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ [one-line description of aesthetic task] ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ItemValue
First stepAlways run Socratic Discovery Mode before proposing any direction
Color systemOKLCH — perceptually uniform, use for all palette generation
Token formatTailwind v4 @theme CSS custom properties
Aesthetic range9 directions — brutalist to experimental, corporate is one option among many
Component approachshadcn/ui first, custom only when insufficient
Integration filesbrand.json (skip color/font questions), stack.json (framework syntax)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

I want to…File
Run discovery and understand the user’s aesthetic intentreference/socratic-discovery.md
Choose a visual direction from the full aesthetic spectrumreference/aesthetic-spectrum.md
Modernize an existing UI or detect dated design patternsreference/dated-vs-modern.md
Generate a color palette using OKLCH with @theme tokensreference/color-palette.md
Set up typography scale, font pairings, and spacingreference/typography.md
Understand spacing, border radius, shadow, and density rulesreference/visual-hierarchy.md
Generate implementation-ready components and style tokensreference/sample-components.md

Usage: Read the reference file matching your current task from the index above. Each file is self-contained with code examples and inline gotchas.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

After ui-craft sets the visual direction:

  • tailwind-css for deep Tailwind v4 implementation details
  • shadcn-ui for component theming and installation
  • responsive-design for layout and breakpoint system
  • framer-motion for animation system matching the aesthetic
  • accessibility to verify contrast ratios and ARIA patterns

After delivering a style direction or style guide, always end with a summary:

Direction chosen: [Aesthetic Name] Palette: [N] color tokens Typography: [font pairing] Components: button, card, hero, input Tokens: ready for @theme

● ahh, that felt good didn’t it?

▸ Ship the tokens to tailwind-css, or want component variants first?