菜单
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, or applications, or when any design skill requires project context.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill impeccable-design命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | impeccable-design |
| description | Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, or applications, or when any design skill requires project context. |
| user-invocable | true |
| argument-hint | [component or page to design] |
| license | Apache 2.0. Based on pbakaus/impeccable frontend-design skill. Original based on Anthropic's frontend-design skill. See pbakaus/impeccable NOTICE.md for attribution. |
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 task needs at minimum:
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:
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 NEVER: Inter, Roboto, Arial, Open Sans, system defaults NEVER: Monospace typography as lazy shorthand for "technical/developer" vibes NEVER: Large icons with rounded corners above every heading
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 palettes DO: Tint your neutrals toward your brand hue NEVER: Gray text on colored backgrounds — use a shade of the background color instead NEVER: Pure black (#000) or pure white (#fff) — always tint NEVER (The AI Color Palette): cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds NEVER: Gradient text on metrics or headings NEVER: Default to dark mode with glowing accents
Create visual rhythm through varied spacing — not the same padding everywhere.
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 NEVER: Wrap everything in cards NEVER: Nest cards inside cards NEVER: Use identical card grids — same-sized cards with icon + heading + text, repeated endlessly NEVER: Use the hero metric layout template — big number, small label, supporting stats, gradient accent NEVER: Center everything
NEVER: Glassmorphism everywhere — blur effects, glass cards, glow borders used decoratively NEVER: Rounded elements with thick colored border on one side NEVER: Sparklines as decoration NEVER: Rounded rectangles with generic drop shadows NEVER: Modals unless truly no better alternative
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 NEVER: Animate layout properties (width, height, padding, margin) — use transform and opacity only NEVER: Bounce or elastic easing
DO: Use progressive disclosure — start simple, reveal sophistication through interaction DO: Design empty states that teach the interface DO: Make every interactive surface feel intentional and responsive NEVER: Repeat the same information NEVER: Make every button primary
DO: Use container queries (@container) for component-level responsiveness DO: Adapt the interface for different contexts — don't just shrink it NEVER: Hide critical functionality on mobile
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?"
Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations. Minimalist designs need restraint, precision, careful attention to spacing 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.
Claude 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.