Minimalist Ui
Generate ultra-minimal, editorial web interfaces with warm monochrome typography, flat bento grids, and explicit bans on generic SaaS chrome.
Overview
minimalist-ui is an agent skill for the Build phase that directs agents to ship clean editorial-style interfaces with warm monochrome palettes, typographic contrast, and flat bento grids—without gradients or heavy shadow
Install
npx skills add https://github.com/leonxlnx/taste-skill --skill minimalist-uiWhat is this skill?
- Premium utilitarian minimalism: document-style, high-contrast warm monochrome palette
- Absolute negative constraints block Inter/Roboto/Open Sans, Lucide/Feather/Heroicons, heavy Tailwind shadows, loud hero
- Typographic hierarchy and macro-whitespace over decorative UI chrome
- Flat bento-grid layouts with muted pastel accents only
- Tailwind shadows limited to ultra-diffuse low-opacity treatment (< 0.05)
- Absolute negative constraints section banning multiple generic typefaces, icon families, and shadow presets
Adoption & trust: 94.8k installs on skills.sh; 37.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps producing generic SaaS UI with Inter, blue heroes, and heavy shadows that makes your indie product look interchangeable.
Who is it for?
Solo founders building marketing sites or app chrome who want agent-generated frontend code constrained to a distinctive minimalist design language.
Skip if: Brand systems that require loud marketing gradients, game UI, or component libraries built around default Material or flashy glassmorphism.
When should I use this skill?
Building or refactoring web interfaces that should follow clean editorial minimalism—warm monochrome, flat bento grids, no gradients or heavy shadows.
What do I get? / Deliverables
You get UI implementations that follow explicit minimal editorial constraints—readable hierarchy, flat grids, and muted accents—so the product feels intentional and premium.
- Frontend markup and styles aligned to the minimalist UI protocol
- Component layouts using flat bento grids and approved typographic hierarchy
Recommended Skills
Journey fit
Visual product surfaces are built in the Build phase; this skill encodes frontend design rules the agent applies while implementing UI. Frontend is where layout, type, color, and component styling are decided—matching this protocol’s palette and negative constraints.
How it compares
A taste and layout protocol for agents, not a component kit or Figma handoff replacement.
Common Questions / FAQ
Who is minimalist-ui for?
Indie builders and design-conscious developers who use agents to implement web UI and want strict guardrails against generic SaaS styling.
When should I use minimalist-ui?
Use it during Build/frontend when scaffolding landing pages, dashboards, or settings views where editorial minimalism and typographic contrast should lead the layout.
Is minimalist-ui safe to install?
It is styling guidance only with no runtime privileges; still review the Security Audits panel on this page like any third-party skill.
SKILL.md
READMESKILL.md - Minimalist Ui
# Protocol: Premium Utilitarian Minimalism UI Architect ## 1. Protocol Overview Name: Premium Utilitarian Minimalism & Editorial UI Description: An advanced frontend engineering directive for generating highly refined, ultra-minimalist, "document-style" web interfaces analogous to top-tier workspace platforms. This protocol strictly enforces a high-contrast warm monochrome palette, bespoke typographic hierarchies, meticulous structural macro-whitespace, bento-grid layouts, and an ultra-flat component architecture with deliberate muted pastel accents. It actively rejects standard generic SaaS design trends. ## 2. Absolute Negative Constraints (Banned Elements) The AI must strictly avoid the following generic web development defaults: - DO NOT use the "Inter", "Roboto", or "Open Sans" typefaces. - DO NOT use generic, thin-line icon libraries like "Lucide", "Feather", or standard "Heroicons". - DO NOT use Tailwind's default heavy drop shadows (e.g., `shadow-md`, `shadow-lg`, `shadow-xl`). Shadows must be practically non-existent or heavily customized to be ultra-diffuse and low opacity (< 0.05). - DO NOT use primary colored backgrounds for large elements or sections (e.g., no bright blue, green, or red hero sections). - DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs). - DO NOT use `rounded-full` (pill shapes) for large containers, cards, or primary buttons. - DO NOT use emojis anywhere in code, markup, text content, headings, or alt text. Replace with proper icons or clean SVG primitives. - DO NOT use generic placeholder names like "John Doe", "Acme Corp", or "Lorem Ipsum". Use realistic, contextual content. - DO NOT use AI copywriting clichés: "Elevate", "Seamless", "Unleash", "Next-Gen", "Game-changer", "Delve". Write plain, specific language. ## 3. Typographic Architecture The interface must rely on extreme typographic contrast and premium font selection to establish an editorial feel. - Primary Sans-Serif (Body, UI, Buttons): Use clean, geometric, or system-native fonts with character. Target: `font-family: 'SF Pro Display', 'Geist Sans', 'Helvetica Neue', 'Switzer', sans-serif`. - Editorial Serif (Hero Headings & Quotes): Target: `font-family: 'Lyon Text', 'Newsreader', 'Playfair Display', 'Instrument Serif', serif`. Apply tight tracking (`letter-spacing: -0.02em` to `-0.04em`) and tight line-height (`1.1`). - Monospace (Code, Keystrokes, Meta-data): Target: `font-family: 'Geist Mono', 'SF Mono', 'JetBrains Mono', monospace`. - Text Colors: Body text must never be absolute black (`#000000`). Use off-black/charcoal (`#111111` or `#2F3437`) with a generous `line-height` of `1.6` for legibility. Secondary text should be muted gray (`#787774`). ## 4. Color Palette (Warm Monochrome + Spot Pastels) Color is a scarce resource, utilized only for semantic meaning or subtle accents. - Canvas / Background: Pure White `#FFFFFF` or Warm Bone/Off-White `#F7F6F3` / `#FBFBFA`. - Primary Surface (Cards): `#FFFFFF` or `#F9F9F8`. - Structural Borders / Dividers: Ultra-light gray `#EAEAEA` or `rgba(0,0,0,0.06)`. - Accent Colors: Exclusively use highly desaturated, washed-out pastels for tags, inline code backgrounds, or subtle icon backgrounds. - Pale Red: `#FDEBEC` (Text: `#9F2F2D`) - Pale Blue: `#E1F3FE` (Text: `#1F6C9F`) - Pale Green: `#EDF3EC` (Text: `#346538`) - Pale Yellow: `#FBF3DB` (Text: `#956400`) ## 5. Component Specifications - Bento Box Feature Grids: - Utilize asymmetrical CSS Grid layouts. - Cards must have exactly `border: 1px solid #EAEAEA`. - Border-radius must be crisp: `8px` or `12px` maximum. - Internal padding must be generous (e.g., `24px` to `40px`). - Primary Call-To-Action (Buttons): - Solid background `#111111`, text `#FFFFFF`. - Slight border-radius (`4px` to `6px`). No b