design-frontend

Solid

Create distinctive, production-grade frontend interfaces that avoid generic AI aesthetics. Use when the user says "build this UI", "design this page", "make it look good", "dashboard layout", "beautify this", or "make the UI feel premium". Produces accessible, responsive components with intentional typography, color, and spacing. Pairs with design-system, enhance-web-ui. Do NOT use for pure logic or API work.

Web & Frontend 9 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
33
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Frontend Design Skill > Discover design systems, respect existing patterns, create beautiful interfaces. --- ## Phase 1: Design System Discovery (MANDATORY) **Before writing ANY frontend code:** ### 1.1 Find Design System Files ``` Glob: **/*design-system*.{md,ts,css} Glob: **/tokens*.{ts,json} Glob: **/components/ui/** Glob: **/_*README* ``` ### 1.2 Extract & Document Tokens | Category | Find | Examples | |----------|------|----------| | Typography | Sizes, weights | `text-xs`, `font-medium` | | Spacing | Padding, gaps | `p-4`, `gap-2` | | Colors | Palette, semantic | `bg-emerald-50` | | Borders | Radius, styles | `rounded-sm` | | Animations | Durations | `duration-200` | ### 1.3 Find Forbidden Patterns ```bash grep -r "NEVER\|FORBIDDEN\|❌" docs/ README* ``` ### 1.4 Verification Statement (REQUIRED) ``` "Design System Discovery: ├─ Found: [design system path] ├─ Typography min: [e.g., text-xs] ├─ Radius standard: [e.g., rounded-sm] ├─ Forbidden: [list patterns] └─ Reusing: [existing components]" ``` --- ## Phase 2: Implementation Standards ### Typography Minimums | Context | Minimum | Usage | |---------|---------|-------| | Body | `text-sm` (14px) | Primary content | | Captions | `text-xs` (12px) | Labels, hints | | Compact | `text-[10px]` | Dense dashboards only | **Never use** `text-[8px]` or `text-[9px]` for readable content. ### Accessibility Requirements | Check | Requirement | |-------|-------------| | Touch targets | ≥44×44px | | Contrast | 4.5:1 text, ...

Details

Author
kensaurus
Repository
kensaurus/cursor-kenji
Created
7 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

frontend-design

Designs, builds, or refactors user-facing web or application interfaces with deliberate visual direction, typography, color and spacing tokens, content hierarchy, responsive behavior, accessible interaction states, and real rendered-surface verification. Use for pages, components, dashboards, landing pages, design systems, and frontend polish. Not for backend logic, API-only work, or visual claims that cannot be rendered or inspected.

94 Updated 2 weeks ago
thiientv
Web & Frontend Listed

frontend-design

Build distinctive, production-grade frontend interfaces with high design quality, guided by named aesthetic philosophies. Use when building components, pages, or applications. Generates working code with exceptional attention to aesthetic details and creative choices that avoid generic AI output.

0 Updated 1 months ago
muzalee
Web & Frontend Listed

frontend-design

Create distinctive, production-grade visual interfaces — design principles that apply to ANY frontend (React, Next.js, Vue, Svelte, plain HTML/CSS, React Native). Use when the aesthetic direction matters — building a component, page, landing site, or app where it must look intentional, not generic "AI slop". Covers visual hierarchy, spacing/rhythm, typography, color + contrast, layout, and design tokens — independent of framework. Triggers — "make this look good", "design", "UI", "landing page", "the spacing feels off", "color palette", "it looks generic/AI". Pairs with frontend-fundamentals (implementation patterns), a11y (accessibility — aesthetic without it is a lawsuit), state-management.

6 Updated yesterday
kouroshez