메뉴
Use when building web components, pages, artifacts, or applications — especially when high design quality is needed. Generates creative, polished code that avoids generic AI aesthetics (purple gradients, Inter font, card-in-card layouts).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when you have a spec or requirements for a multi-step task, before touching code
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
| name | frontend-design |
| description | Use when building web components, pages, artifacts, or applications — especially when high design quality is needed. Generates creative, polished code that avoids generic AI aesthetics (purple gradients, Inter font, card-in-card layouts). |
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
Design skills produce generic output without project context. Before doing any design work, confirm:
Gathering order:
.impeccable.md: If it exists in the project root and has context, use it.Commit to a BOLD aesthetic direction before writing any code:
CRITICAL: Choose a clear conceptual direction and execute with precision. Bold maximalism and refined minimalism both work — the key is intentionality, not intensity.
Implement working code that is:
→ See typography reference for scales, pairing, and loading strategies.
Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font.
DO: Use a modular type scale with fluid sizing (clamp())
DO: Vary font weights and sizes to create clear visual hierarchy
DON'T: Use overused fonts — Inter, Roboto, Arial, Open Sans, system defaults
DON'T: Use monospace typography as lazy shorthand for "technical/developer" vibes
DON'T: Put large icons with rounded corners above every heading
→ See color reference for OKLCH, palettes, and dark mode.
DO: Use modern CSS color functions (oklch, color-mix, light-dark()) for perceptually uniform palettes
DO: Tint your neutrals toward your brand hue
DON'T: Use gray text on colored backgrounds — looks washed out; use a shade of the bg color instead
DON'T: Use pure black (#000) or pure white (#fff) — always tint
DON'T: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon on dark
DON'T: Use gradient text for "impact" on metrics or headings
DON'T: Default to dark mode with glowing accents without real design decisions
→ See spatial reference for grids, rhythm, and container queries.
DO: Create visual rhythm through varied spacing — tight groupings, generous separations
DO: Use fluid spacing with clamp() that breathes on larger screens
DO: Use asymmetry and unexpected compositions; break the grid intentionally
DON'T: Wrap everything in cards — not everything needs a container
DON'T: Nest cards inside cards — visual noise
DON'T: Use identical card grids (same-sized card with icon + heading + text, repeated)
DON'T: Center everything — left-aligned text with asymmetric layouts feels more designed
DON'T: Use the same spacing everywhere
DO: Use intentional, purposeful decorative elements that reinforce brand DON'T: Use glassmorphism everywhere — blur/glass/glow as decoration rather than purpose DON'T: Use rounded rectangles with generic drop shadows — forgettable DON'T: Use sparklines as decoration DON'T: Use modals unless there's truly no better alternative
→ See motion reference for timing, easing, and reduced motion.
DO: Use motion to convey state changes — entrances, exits, feedback
DO: Use exponential easing (ease-out-quart/quint/expo) for natural deceleration
DO: For height animations, use grid-template-rows transitions instead of animating height
DON'T: Animate layout properties (width, height, padding, margin) — use transform and opacity only
DON'T: Use bounce or elastic easing — dated and tacky
→ See interaction reference for forms, focus, loading patterns.
DO: Use progressive disclosure — start simple, reveal sophistication through interaction DO: Design empty states that teach the interface, not just say "nothing here" DON'T: Make every button primary — use ghost buttons, text links, secondary styles DON'T: Repeat the same information redundantly
→ See responsive reference for mobile-first, fluid design.
DO: Use container queries (@container) for component-level responsiveness
DO: Adapt the interface for different contexts — don't just shrink it
DON'T: Hide critical functionality on mobile
→ See UX writing reference for labels, errors, and empty states.
DO: Make every word earn its place DON'T: Repeat information users can already see
Critical quality check: If you showed this interface to someone and said "AI made this," would they believe you immediately? If yes, that's the problem.
A distinctive interface should make someone ask "how was this made?" not "which AI made this?"
Review the DON'T guidelines above — they are the fingerprints of AI-generated work from 2024-2025.
Match implementation complexity to the aesthetic vision:
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.
| Category | DON'T |
|---|---|
| Fonts | Inter, Roboto, Arial, Open Sans |
| Colors | Pure black/white, purple gradients, gray on color |
| Layout | Cards in cards, centered everything, identical grids |
| Motion | Bounce/elastic easing, animating height/width |
| Visual | Glassmorphism everywhere, gradient text, generic shadows |
| Writing | "OK", "Submit", redundant copy, vague errors |