// Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.
Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight.
Push interfaces past conventional limits with technically ambitious implementations. Whether that's a shader, a 60fps virtual table, spring physics on a dialog, or scroll-driven reveals â make users ask "how did they do that?"
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
| name | frontend-design |
| description | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. |
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. You MUST have confirmed design context before doing any design work.
Required context â every design skill needs at minimum:
Individual skills may require additional context â check the skill's preparation section for specifics.
CRITICAL: You cannot infer this context by reading the codebase. Code tells you what was built, not who it's for or what it should feel like. Only the creator can provide this context.
Gathering order:
.impeccable.md from the project root. If it exists and contains the required context, proceed.Commit to a BOLD aesthetic direction:
CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both workâthe key is intentionality, not intensity.
Then implement working code that is:
â Consult 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âthey rarely add value and make sites look templated
â Consult color reference for OKLCH, palettes, and dark mode.
Commit to a cohesive palette. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
DO: Use modern CSS color functions (oklch, color-mix, light-dark) for perceptually uniform, maintainable palettes DO: Tint your neutrals toward your brand hueâeven a subtle hint creates subconscious cohesion DON'T: Use gray text on colored backgroundsâit looks washed out; use a shade of the background color instead DON'T: Use pure black (#000) or pure white (#fff)âalways tint; pure black/white never appears in nature DON'T: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds DON'T: Use gradient text for "impact"âespecially on metrics or headings; it's decorative rather than meaningful DON'T: Default to dark mode with glowing accentsâit looks "cool" without requiring actual design decisions
â Consult spatial reference for grids, rhythm, and container queries.
Create visual rhythm through varied spacingânot the same padding everywhere. Embrace asymmetry and unexpected compositions. Break the grid intentionally for emphasis.
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 for emphasis DON'T: Wrap everything in cardsânot everything needs a container DON'T: Nest cards inside cardsâvisual noise, flatten the hierarchy DON'T: Use identical card gridsâsame-sized cards with icon + heading + text, repeated endlessly DON'T: Use the hero metric layout templateâbig number, small label, supporting stats, gradient accent DON'T: Center everythingâleft-aligned text with asymmetric layouts feels more designed DON'T: Use the same spacing everywhereâwithout rhythm, layouts feel monotonous
DO: Use intentional, purposeful decorative elements that reinforce brand DON'T: Use glassmorphism everywhereâblur effects, glass cards, glow borders used decoratively rather than purposefully DON'T: Use rounded elements with thick colored border on one sideâa lazy accent that almost never looks intentional DON'T: Use sparklines as decorationâtiny charts that look sophisticated but convey nothing meaningful DON'T: Use rounded rectangles with generic drop shadowsâsafe, forgettable, could be any AI output DON'T: Use modals unless there's truly no better alternativeâmodals are lazy
â Consult motion reference for timing, easing, and reduced motion.
Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions.
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 directly DON'T: Animate layout properties (width, height, padding, margin)âuse transform and opacity only DON'T: Use bounce or elastic easingâthey feel dated and tacky; real objects decelerate smoothly
â Consult interaction reference for forms, focus, and loading patterns.
Make interactions feel fast. Use optimistic UIâupdate immediately, sync later.
DO: Use progressive disclosureâstart simple, reveal sophistication through interaction (basic options first, advanced behind expandable sections; hover states that reveal secondary actions) DO: Design empty states that teach the interface, not just say "nothing here" DO: Make every interactive surface feel intentional and responsive DON'T: Repeat the same informationâredundant headers, intros that restate the heading DON'T: Make every button primaryâuse ghost buttons, text links, secondary styles; hierarchy matters
â Consult responsive reference for mobile-first, fluid design, and container queries.
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âadapt the interface, don't amputate it
â Consult 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. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details.
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.
Remember: the model is capable of extraordinary creative work. Don't hold backâshow what can truly be created when thinking outside the box and committing fully to a distinctive vision.