frontend-design

Creates distinctive UI designs with deliberate typography, color tokens, and signature elements.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill frontend-design-kiurakku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-design
Source: https://github.com/kiurakku/cursor-kit-for-ai/tree/main/plugins/frontend/skills/frontend-design
Command: npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill frontend-design-kiurakku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interfaces tend to converge on the same generic patterns — cream backgrounds with serif headlines, dark themes with acid-green accents, or purple-gradient glassmorphism. This Skill forces deliberate aesthetic decisions before any code is written, so landing pages, dashboards, and design systems end up with a recognizable visual identity instead of looking like unreviewed AI output. ## Core Features & Use Cases - Aesthetic Direction Framework: Choose from seven defined design directions (industrial utilitarian, warm editorial, Swiss minimal, playful product, luxury restraint, retro-futurist, organic natural) with an explicit blocklist of overused AI-default combinations. - Token-Based Design System: Define CSS variable or Tailwind theme tokens for surfaces, text, brand, and semantic colors, with contrast requirements and typography pairing rules. - Four-Phase Workflow with Self-Critique: Direction selection, design brief critique, implementation guidance per stack (Tailwind v4, CSS Modules, styled-components, shadcn/ui), and screenshot-based visual critique at three viewport widths. - Use Case: When building a new SaaS landing page, run Phase 1 to commit to a direction and signature element, then use the screenshot critique template to verify the result passes the squint, swap, and neighbor tests before shipping. ## Quick Start Ask the agent to design a landing page for your product using the frontend-design skill, starting with an aesthetic direction and design brief before writing any components.

Frequently Asked Questions about frontend-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated UI not look generic?▼

Commit to one explicit aesthetic direction before writing code, define a signature element users can describe in one sentence, and reject known AI-default combinations like cream backgrounds with serif headlines. Then run a screenshot critique at 375px, 768px, and 1280px widths.

How to structure color tokens in CSS or Tailwind?▼

Define tokens as CSS variables or a Tailwind theme extension covering surfaces, text, brand accent, and semantic states, never hardcoding hex values in components. For Tailwind v4 use @theme in CSS; for shadcn/ui override the globals.css variables rather than component internals.

What typography pairing rules should I follow for web design?▼

Pair a display and body font from different classifications, such as serif with sans or grotesque with mono, never two similar sans families. Use a modular scale with at least five steps, limit body text to two weights, and keep line length between 55 and 75 characters.

Does this design workflow work with shadcn/ui and Tailwind?▼

Yes, the skill includes stack-specific guidance for Tailwind v4, CSS Modules, styled-components, and shadcn/ui. The key rule is to override design tokens rather than component internals, since shadcn defaults are a starting point, not a finished design system.

Why does my UI look fine in code but generic in screenshots?▼

Code review cannot catch visual sameness, which is why the workflow requires a screenshot critique phase. Capture full-page screenshots at three viewport widths and apply the squint test, logo swap test, and competitor neighbor test to verify hierarchy and brand distinctiveness.