Skip to content
Back to search

ui-design-brain

SkillWorks with Claude CodeGitHub

Generate production-grade UI using real component patterns and best practices from 60+ documented interface components. Use when the user asks to build web interfaces, pages, dashboards, forms, navigation, or any UI — ensures modern, minimal, SaaS-quality output grounded in design system conventions rather than generic AI patterns.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/carmahhawwari-ui-design-brain/badge.svg)](/listings/carmahhawwari-ui-design-brain)

HTML

<a href="/listings/carmahhawwari-ui-design-brain"><img src="/api/listings/carmahhawwari-ui-design-brain/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Option A — Personal skill (all projects)

# Clone into your Cursor skills directory
git clone https://github.com/carmahhawwari/ui-design-brain.git \
  ~/.cursor/skills/ui-design-brain

Option B — Project skill (shared with team)

# Clone into your project's .cursor/skills directory
git clone https://github.com/carmahhawwari/ui-design-brain.git \
  .cursor/skills/ui-design-brain

Option C — Manual

Copy the `SKILL.md` and `components.md` files into either: - `~/.cursor/skills/ui-design-brain/` (personal) - `.cursor/skills/ui-design-brain/` (project)

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 163 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: ui-design-brain
  3. description: Generate production-grade UI using real component patterns and best practices from 60+ documented interface components. Use when the user asks to build web interfaces, pages, dashboards, forms, navigation, or any UI — ensures modern, minimal, SaaS-quality output grounded in design system conventions rather than generic AI patterns.
  4. license: Complete terms in LICENSE.txt
  5. ---
  6. # UI Design Brain
  7. This skill provides a curated knowledge base of 60+ UI component patterns sourced from [component.gallery](https://component.gallery) and enriched with best practices, layout guidance, and usage rules. It replaces generic guessing with real design-system knowledge when generating interfaces.
  8. **Before writing any UI code**, consult this skill to select the right components and follow their best practices. Read [components.md](components.md) for the full reference.
  9. ## When to Use This Skill
  10. Apply whenever the user asks to build, design, or generate:
  11. - Web pages, landing pages, marketing sites
  12. - SaaS dashboards, admin panels, settings pages
  13. - Forms, data tables, navigation structures
  14. - Modals, drawers, popovers, or overlay patterns
  15. - Any React, HTML/CSS, or Tailwind UI component
  16. ## Design Philosophy
  17. Every generated interface should feel **modern, minimal, and production-ready** — not like a template.
  18. ### Core Principles
  19. 1. **Restraint over decoration.** Fewer elements, highly refined. White space is a feature.
  20. 2. **Typography carries hierarchy.** Pair a distinctive display font with a clean body font. Maximize weight contrast between headings and labels.
  21. 3. **One strong color moment.** Neutral palette first (warm off-whites, near-blacks, muted mid-tones). Introduce one confident accent. If it could appear on a poster or book cover, it's probably timeless.
  22. 4. **Spacing is structure.** Use an 8 px grid. Tighter gaps group related elements; generous gaps let hero content breathe.
  23. 5. **Accessibility is non-negotiable.** WCAG AA contrast minimums. Focus indicators. Semantic HTML. Keyboard navigation.
  24. 6. **No generic AI aesthetics.** Avoid: purple-on-white gradients, Inter/Roboto defaults, evenly-spaced card grids, and cookie-cutter layouts. Every interface should feel designed for its specific context.
  25. ### Quality Bar
  26. The output should match what you'd expect from a senior product designer at a top SaaS company:
  27. - Clean visual rhythm with intentional asymmetry
  28. - Obvious interactive affordances (hover, focus, active states)
  29. - Graceful edge cases (empty states, loading, error)
  30. - Responsive without breakpoint artifacts
  31. ## Workflow
  32. ### Step 1 — Identify Components
  33. Read the user's request and determine which UI components are needed. Reference [components.md](components.md) to find each component by name or alias.
  34. Common mappings:
  35. - "navigation" → Header, Navigation, Breadcrumbs, Tabs
  36. - "form" → Form, Text input, Select, Checkbox, Radio button, Button
  37. - "data display" → Table, Card, List, Badge, Avatar
  38. - "feedback" → Alert, Toast, Modal, Spinner, Progress bar, Empty state
  39. - "input" → Text input, Textarea, Select, Combobox, Datepicker, File upload, Slider
  40. - "overlay" → Modal, Drawer, Popover, Tooltip, Dropdown menu
  41. ### Step 2 — Apply Best Practices
  42. For each component in the interface, follow its best practices from the reference. Key rules that apply broadly:
  43. **Layout**
  44. - Single-column forms — faster to scan
  45. - Consistent vertical lanes in repeated rows (lists, tables)
  46. - Fixed-width slots for icons and actions, even when empty
  47. - Cards: media → title → meta → action hierarchy
  48. **Interaction**
  49. - Buttons: verb-first labels ("Save changes", not "Submit"), one primary per section
  50. - Modals: always provide X, Cancel, and Escape; trap focus; return focus on close
  51. - Toasts: auto-dismiss 4–6 s, allow manual dismiss, stack newest on top
  52. - Toggles: immediate effect only — use checkboxes in forms that require Save
  53. **Typography & Spacing**
  54. - Strict heading hierarchy (h1 → h2 → h3), one h1 per page
  55. - Minimum 44 px touch targets on mobile
  56. - Labels above inputs (vertical forms) or beside (horizontal)
  57. - Placeholder text as format hint, never as label replacement
  58. **States**
  59. - Empty states: illustration + helpful headline + primary CTA
  60. - Loading: skeleton screens > spinners (show after 300 ms delay)
  61. - Validation: inline on blur, not on every keystroke
  62. - Disabled elements: visually distinct but still readable
  63. ### Step 3 — Choose a Design Direction
  64. Select the style preset that best matches the user's intent, or ask if unclear:
  65. **Modern SaaS** (default)
  66. - Neutral palette, one strong accent
  67. - 8 px grid, generous white space
  68. - Clean, professional, spacious
  69. **Apple-level Minimal**
  70. - Near-monochrome, warm grays
  71. - Large type hierarchy, tight tracking on display text
  72. - Abundant white space, micro-interactions (150–250 ms ease-out)
  73. **Enterprise / Corporate**
  74. - Information-dense, well-defined regions
  75. - Compact spacing scale (4/8/12/16/24 px)
  76. - Robust form handling, fully keyboard-navigable
  77. **Creative / Portfolio**
  78. - Bold, expressive, strong visual personality
  79. - Asymmetric layouts, dramatic scale contrast
  80. - Editorial typography, vivid accent colors
  81. **Data Dashboard**
  82. - Data-dense, optimised for scannability
  83. - Consistent vertical alignment across rows
  84. - Clear metric hierarchy: KPI → trend → detail
  85. ### Step 4 — Generate Code
  86. Write production-ready code following these rules:
  87. ```
  88. Stack: React + Tailwind CSS (unless user specifies otherwise)
  89. Spacing: Tailwind spacing scale (p-2, gap-4, etc.) on an 8px grid
  90. Colors: CSS variables or Tailwind config for palette consistency
  91. Typography: Tailwind text utilities; expressive font pairings via Google Fonts
  92. States: Implement hover, focus, active, disabled for all interactive elements
  93. Responsive: Mobile-first; test at 375, 768, 1440 px
  94. Accessibility: Semantic HTML, ARIA where needed, focus management
  95. ```
  96. ## Component Quick Reference
  97. Below are the 15 most commonly needed components. For the full 60+ component reference with best practices, aliases, and layout examples, see [components.md](components.md).
  98. | Component | When to use | Key rule |
  99. |-----------|------------|----------|
  100. | **Button** | Trigger actions | Verb-first labels; one primary per section |
  101. | **Card** | Represent an entity | Media → title → meta → action; shadow OR border, not both |
  102. | **Modal** | Focused attention | Trap focus; X + Cancel + Escape to close |
  103. | **Navigation** | Page/section links | 5–7 items max; clear active state |
  104. | **Table** | Structured data | Sticky header; right-align numbers; sortable columns |
  105. | **Tabs** | Switch panels | 2–7 tabs; active indicator; accordion on mobile |
  106. | **Form** | Collect input | Single column; labels above; inline validation on blur |
  107. | **Toast** | Brief confirmation | Auto-dismiss 4–6 s; undo action for destructive ops |
  108. | **Alert** | Important status | Semantic colors + icon; max 2 sentences |
  109. | **Drawer** | Secondary panel | Right for detail, left for nav; 320–480 px desktop |
  110. | **Search input** | Find content | Cmd/Ctrl+K shortcut; debounce 200–300 ms |
  111. | **Empty state** | No data | Illustration + headline + CTA; positive framing |
  112. | **Skeleton** | Loading placeholder | Match actual layout shape; shimmer animation |
  113. | **Badge** | Status/metadata label | 1–2 words; pill shape for status; limited color palette |
  114. | **Dropdown menu** | Action/nav options | 7±2 items; destructive actions last in red |
  115. ## Anti-Patterns to Avoid
  116. Never generate these — they signal generic, low-quality UI:
  117. - **Rainbow badges** — every status a different bright color with no semantic meaning
  118. - **Modal inside modal** — use a page or drawer for complex flows
  119. - **Disabled submit with no explanation** — always indicate what's missing
  120. - **Spinner for predictable layouts** — use skeleton screens instead
  121. - **"Click here" links** — link text must describe the destination
  122. - **Hamburger menu on desktop** — use visible navigation when space allows
  123. - **Auto-advancing carousels** — let users control navigation
  124. - **Placeholder-only form fields** — always use visible labels
  125. - **Equal-weight buttons** — establish primary/secondary/tertiary hierarchy
  126. - **Tiny text (< 12 px)** — body text minimum 14 px, prefer 16 px
README.md · README · 119 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # UI Design Brain
  2. A Cursor skill that gives the AI agent real UI component knowledge — best practices, layout patterns, and design-system conventions for 60+ interface components — so it generates production-grade UI instead of generic output.
  3. ## What it does
  4. When you ask Cursor to build a UI, it typically guesses at component patterns. This skill replaces guessing with a curated knowledge base sourced from [component.gallery](https://component.gallery) and enriched with:
  5. - **Best practices** for every component (accessibility, sizing, behavior)
  6. - **Common layouts** — proven arrangements for each pattern
  7. - **Aliases** — so the agent recognizes components by any name
  8. - **Design philosophy** — modern, minimal, SaaS-quality standards
  9. - **Anti-patterns** — specific things to avoid
  10. The result: interfaces that feel designed by a senior product designer, not assembled from a template.
  11. ## Install
  12. ### Option A — Personal skill (all projects)
  13. ```bash
  14. # Clone into your Cursor skills directory
  15. git clone https://github.com/carmahhawwari/ui-design-brain.git \
  16. ~/.cursor/skills/ui-design-brain
  17. ```
  18. ### Option B — Project skill (shared with team)
  19. ```bash
  20. # Clone into your project's .cursor/skills directory
  21. git clone https://github.com/carmahhawwari/ui-design-brain.git \
  22. .cursor/skills/ui-design-brain
  23. ```
  24. ### Option C — Manual
  25. Copy the `SKILL.md` and `components.md` files into either:
  26. - `~/.cursor/skills/ui-design-brain/` (personal)
  27. - `.cursor/skills/ui-design-brain/` (project)
  28. ## Usage
  29. Once installed, the skill activates automatically when you ask Cursor to build UI. You don't need to reference it explicitly.
  30. ### Examples
  31. Just ask naturally:
  32. ```
  33. Build a settings page with a sidebar navigation, toggle preferences, and a profile section.
  34. ```
  35. ```
  36. Create a data table with search, filters, sortable columns, and pagination.
  37. ```
  38. ```
  39. Design a SaaS dashboard with KPI cards, a chart area, and an activity feed sidebar.
  40. ```
  41. The agent will automatically:
  42. 1. Identify which components your request needs
  43. 2. Look up best practices for each one
  44. 3. Apply the right design direction (SaaS, minimal, corporate, creative, or dashboard)
  45. 4. Generate production-ready code following the patterns
  46. ### Design directions
  47. The skill includes 5 built-in style presets. You can request one explicitly:
  48. | Preset | When to use |
  49. |--------|-------------|
  50. | **Modern SaaS** | Default — clean, spacious, professional |
  51. | **Apple-level Minimal** | Ultra-clean with generous whitespace |
  52. | **Enterprise / Corporate** | Information-dense, keyboard-navigable |
  53. | **Creative / Portfolio** | Bold, expressive, editorial typography |
  54. | **Data Dashboard** | Optimized for data scannability |
  55. ```
  56. Build a pricing page with an Apple-minimal aesthetic.
  57. ```
  58. ## What's inside
  59. ```
  60. ui-design-brain/
  61. ├── SKILL.md # Main instructions — design philosophy, workflow, quick reference
  62. ├── components.md # Full reference — 60 components with best practices and layouts
  63. ├── LICENSE.txt # MIT license
  64. └── README.md # This file
  65. ```
  66. ### Component coverage
  67. 60 components including: Accordion, Alert, Avatar, Badge, Breadcrumbs, Button, Button group, Card, Carousel, Checkbox, Color picker, Combobox, Date input, Datepicker, Drawer, Dropdown menu, Empty state, Fieldset, File, File upload, Footer, Form, Header, Heading, Hero, Icon, Image, Label, Link, List, Modal, Navigation, Pagination, Popover, Progress bar, Progress indicator, Quote, Radio button, Rating, Rich text editor, Search input, Segmented control, Select, Separator, Skeleton, Skip link, Slider, Spinner, Stack, Stepper, Table, Tabs, Text input, Textarea, Toast, Toggle, Tooltip, Tree view, Video, Visually hidden.
  68. ## How it differs from frontend-design skills
  69. | | Generic frontend skill | UI Design Brain |
  70. |-|----------------------|-----------------|
  71. | **Component knowledge** | None — relies on model training | 60 components with specific best practices |
  72. | **Layout guidance** | General advice | Concrete layout patterns per component |
  73. | **Anti-patterns** | Not addressed | Explicit list of things to avoid |
  74. | **Accessibility** | Mentioned loosely | Specific per-component rules (focus trapping, ARIA, keyboard nav) |
  75. | **Design system grounding** | Model's general knowledge | Sourced from real design systems via component.gallery |
  76. ## Contributing
  77. PRs welcome. To add or update components:
  78. 1. Edit `components.md` — follow the existing format (name, aliases, description, best practices, common layouts)
  79. 2. If the component is commonly needed, add it to the quick reference table in `SKILL.md`
  80. 3. Keep `SKILL.md` under 500 lines
  81. ## License
  82. MIT — see [LICENSE.txt](LICENSE.txt).
  83. Component data sourced from [component.gallery](https://component.gallery).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.