skills/frontend-design/SKILL.md
Create distinctive, production-grade frontend interfaces with high design quality. Covers websites, landing pages, dashboards, SaaS UIs, React components, and any web UI. Includes Verbalized Sampling methodology to avoid generic AI aesthetics, domain exploration for interface design, and creative implementation patterns.
npx skillsauth add ihj04982/my-cursor-settings frontend-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create distinctive, production-grade interfaces. This skill combines creative implementation, anti-generic methodology, and domain-driven interface design.
Before any design, gather deep context:
Use AskUserQuestion if the prompt is vague. Do not proceed with assumptions.
Verbalize the most predictable design for this request. Common "AI-slop" markers:
You are forbidden from choosing this baseline.
Produce all four before proposing any direction:
Apply the AIDA Framework:
| Stage | Goal | Design Application | |-------|------|--------------------| | Attention | Stop the scroll | Bold typography, unexpected imagery, striking contrast | | Interest | Build curiosity | Progressive reveal, visual storytelling, unique value | | Desire | Emotional connection | Social proof, benefits visualization, micro-interactions | | Action | Drive conversion | High-contrast CTAs, reduced friction |
Generate three aesthetic directions with Typicality Scores (0 = unique, 1 = generic):
Select the lowest T-Score that still meets functional requirements and quality guardrails.
| Guardrail | Description | |-----------|-------------| | Visual Hierarchy | Clear priority ordering — eye knows where to go first, second, third | | Contrast & Legibility | Text readable against background (WCAG AA minimum) | | Internal Consistency | Follows its OWN logic — a coherent system, not random choices | | Functional Clarity | Interactive elements recognizable as such; clear affordances |
Choose fonts that are distinctive and context-appropriate. Avoid Inter, Roboto, Arial, system fonts, Space Grotesk as defaults. Pair a characterful display font with a refined body font. Variable fonts and unusual weights encouraged.
Commit to a cohesive palette. CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. Gray builds structure; color communicates status, action, emphasis.
Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density. If a standard grid is P=0.9, consider P=0.1 layouts.
Create atmosphere. Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, grain overlays. Match the aesthetic vision.
Surfaces barely different but distinguishable. Study Vercel, Supabase, Linear. Elevation changes so subtle you almost can't see them — but you feel the hierarchy. Borders light but not invisible.
Every pattern has infinite expressions. A metric display could be a hero number, sparkline, gauge, progress bar, comparison delta, or something new. Before building, ask: What's the ONE thing users do most here?
Every product exists in a world with colors. Walk into the physical version of this space — what would you see? Your palette should feel like it came FROM somewhere.
If you swapped the typeface for your usual one, would anyone notice? The places where swapping wouldn't matter are where you defaulted.
Blur your eyes. Can you still perceive hierarchy? Nothing should jump out harshly.
Point to five specific elements where your signature appears. Not "the overall feel" — actual components.
cursor-pointerprefers-reduced-motion respecteddevelopment
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
research
Generate high-entropy research (자료조사) and ideas (아이디어) using Verbalized Sampling to avoid mode collapse and maximize creativity and novelty.
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
documentation
Sync documentation from source-of-truth (package.json, .env.example). Generates CONTRIB.md, RUNBOOK.md. Use when updating project docs or after adding scripts/env vars.