前端设计
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 设计与多媒体
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Auto-detect the best domain from a concise query
python3 .claude/skills/frontend-design/scripts/search.py "glassmorphism dark mode"
# Ask for a specific kind of guidance
python3 .claude/skills/frontend-design/scripts/search.py "healthcare saas" --domain colors
# Add framework context when implementation details matter
python3 .claude/skills/frontend-design/scripts/search.py "responsive layout" --stack html-tailwind
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.
The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
## Design Thinking
Before coding, understand the context and commit to a BOLD aesthetic direction:
- **Purpose**: What problem does this interface solve? Who uses it?
- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
- **Constraints**: Technical requirements (framework, performance, accessibility).
- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
**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 (HTML/CSS/JS, React, Vue, etc.) that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail
## Frontend Aesthetics Guidelines
Focus on:
- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
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 (Space Grotesk, for example) across generations.
**IMPORTANT**: 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. Elegance comes from executing the vision well.
## Design Intelligence
Use the bundled design search tooling when you need concrete guidance that should shape implementation rather than generic inspiration.
Reach for `.claude/skills/frontend-design/scripts/search.py` when you need any of the following:
- a style direction that fits a product category or audience
- a color system, typography pairing, or chart recommendation
- UX or accessibility guidance for a specific interface problem
- stack-specific frontend advice for React, Next.js, Vue, Tailwind, and other supported stacks
- a full design-system recommendation grounded in the bundled dataset
Skip the search when the user already gave a precise visual direction and the implementation path is obvious.
### Search Workflow
1. Start with the smallest query that captures the product or interface type.
2. Use auto-detection first; add `--domain` only when you know what kind of answer you need.
3. Add `--stack` when framework-specific implementation details matter.
4. Synthesize the retrieved guidance into one cohesive direction instead of pasting disconnected search results into the final answer.
### Quick Start
```bash
# Auto-detect the best domain from a concise query
python3 .claude/skills/frontend-design/scripts/search.py "glassmorphism dark mode"
# Ask for a specific kind of guidance
python3 .claude/skills/frontend-design/scripts/search.py "healthcare saas" --domain colors
# Add framework context when implementation details matter
python3 .claude/skills/frontend-design/scripts/search.py "responsive layout" --stack html-tailwind
```
### High-Value Defaults
Treat these as strong defaults, not blind rules:
- Prefer SVG icon systems over emoji so the UI feels product-grade and stylistically consistent.
- Keep clickable elements obviously interactive, including pointer cues where the platform expects them.
- Protect readability first; contrast and hierarchy matter more than visual gimmicks.
- In light mode, translucent surfaces need enough opacity to stay legible.
- Floating elements look more intentional when they breathe instead of touching viewport edges.
- Prefer hover treatments that preserve layout stability unless movement is a deliberate part of the concept.
### References
- `references/design-system-generation.md` — use when the user wants a full design-system or style-guide recommendation for a project type (e.g. "SaaS dashboard", "e-commerce luxury", "fintech app") assembled from multiple search domains
- `references/quality-checklist.md` — use as the final self-critique pass before delivering UI work
## Gotchas
- **Defaulting to safe choices**: Inter font + blue primary + white background is AI slop. Be distinctive.
- **Using search as decoration**: Retrieved guidance should change the design system or implementation decisions, not just add buzzwords.
- **Inconsistent design system**: Don't mix unrelated tokens or visual languages. Commit to one system throughout.
- **Ignoring contrast ratios**: WCAG AA minimum. Beautiful but unreadable is a failure.
- **Purple gradients**: The #1 AI cliché. Avoid unless specifically requested.
- **Interaction polish gaps**: Missing hover/focus states or weak affordances make even strong visuals feel unfinished.
## Data Source
Remote: [ui-ux-pro-max-skill](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill/tree/main/src/ui-ux-pro-max/data)
Available domains include styles, colors, typography, charts, products, landing, ux, icons, ui-reasoning, and web-interface. Supported stacks include html-tailwind, react, nextjs, astro, vue, nuxtjs, nuxt-ui, svelte, swiftui, react-native, flutter, shadcn, and jetpack-compose.
Search uses a cached BM25 ranking script over the remote dataset, so prefer concise, concrete queries over long prompt-like paragraphs.
Remember: 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.
---
> Source: [avibebuilder/claude-prime](https://github.com/avibebuilder/claude-prime) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
设计思维
前端美学指南
设计智能
搜索工作流程
高价值默认值
文件/命令 -> .claude/skills/frontend-design/scripts/search.py · --domain · --stack · references/design-system-generation.md · references/quality-checklist.md
内容校验值 -> 79ce194f4921
当前原文的自动摘译,尚未人工审校。
设计思维
在编码之前,了解上下文并致力于大胆的美学方向: 目的:这个界面解决什么问题?谁使用它?基调:选择一个极端:极简主义、混乱主义、复古未来主义、有机/自然、奢华/精致、俏皮/玩具、社论/杂志、野兽派/原始、装饰艺术/几何、柔和/柔和、工业/实用等。有很多口味可供选择。使用它们来获取灵感,但设计出一款符合美学方向的产品。
前端美学指南
重点: 版式:选择美观、独特且有趣的字体。避免使用 Arial 和 Inter 等通用字体;相反,选择独特的选择来提升前端的美感;意想不到的、有特色的字体选择。将独特的显示字体与精致的正文字体配对。颜色和主题:致力于具有凝聚力的美感。使用 CSS 变量来保持一致性。带有鲜明强调的主色调胜过胆小、分布均匀的调色板。
设计智能
当您需要具体指导来塑造实施而不是通用灵感时,请使用捆绑的设计搜索工具。当您需要以下任何一项时,请选择
.claude/skills/frontend-design/scripts/search.py:适合产品类别或受众的风格方向、色彩系统、排版配对或图表推荐用户体验或针对特定界面问题的可访问性指南搜索工作流程
从捕获产品或接口类型的最小查询开始。首先使用自动检测;仅当您知道需要什么样的答案时才添加
--domain。当特定于框架的实现细节很重要时添加--stack。将检索到的指导综合为一个有凝聚力的方向,而不是将断开连接的搜索结果粘贴到最终答案中。高价值默认值
将这些视为强默认值,而不是盲目规则:与表情符号相比,更喜欢 SVG 图标系统,这样 UI 感觉产品级且风格一致。保持可点击元素明显的交互性,包括平台期望的指针提示。首先保护可读性;对比和层次比视觉噱头更重要。在浅色模式下,半透明表面需要足够的不透明度才能保持清晰。