
Design Taste Frontend
- 408 installs
- 27 repo stars
- Updated February 24, 2026
- bnd-1/taste-skill
design-taste-frontend is a Claude agent skill that applies refined visual judgment to layouts, typography, color, spacing, and component choices so developers ship frontend interfaces that feel intentional, modern, and v
About
design-taste-frontend is a Claude Code agent skill from the bnd-1/taste-skill repository that guides coding agents to apply consistent visual judgment when building web and app interfaces. The skill steers decisions about layout rhythm, typographic hierarchy, color palettes, whitespace, and component selection so generated UI does not read as generic or visually disjointed. Developers reach for design-taste-frontend when implementation is functionally correct but the interface still feels flat, cramped, or inconsistent across screens and needs a deliberate polish pass before review or release. The skill encodes taste-oriented heuristics rather than a single design system, making it useful when teams lack a dedicated designer but still want interfaces that communicate quality and coherence. Agents use it while scaffolding pages, refining component libraries, or revising CSS and layout markup where small spacing and typography adjustments compound into noticeably better UX. design-taste-frontend complements framework-specific skills by focusing on aesthetic coherence independent of whether the stack is React, Vue, or plain HTML and CSS.
- Typography and spacing judgment
- Color and hierarchy refinement
- Component-level aesthetic guidance
- Modern UI taste calibration
- Cohesive visual language
Design Taste Frontend by the numbers
- 408 all-time installs (skills.sh)
- Ranked #677 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 1, 2026 (Skillselion catalog sync)
npx skills add https://github.com/bnd-1/taste-skill --skill design-taste-frontendAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 408 |
|---|---|
| repo stars | ★ 27 |
| Last updated | February 24, 2026 |
| Repository | bnd-1/taste-skill ↗ |
How do you improve frontend UI visual polish?
Apply refined frontend design taste to layouts, typography, color, spacing, and component choices so interfaces feel intentional, modern, and visually coherent.
Who is it for?
Frontend developers shipping customer-facing UI who want agent-guided visual refinement without a dedicated design review on every screen.
Skip if: Projects with a locked design system and strict Figma specs where agents should implement tokens verbatim instead of exercising visual judgment.
When should I use this skill?
A developer asks to improve UI taste, fix visual hierarchy, polish typography and spacing, or make a frontend layout feel more modern and intentional.
What you get
Refined layout markup, typography scales, color palettes, spacing rules, and component selections with cohesive visual hierarchy.
- Refined layout markup
- Typography and spacing guidelines
- Cohesive color and component choices
Files
High-Agency Frontend Skill
1. ACTIVE BASELINE CONFIGURATION
- DESIGN_VARIANCE: 8 (1=Perfect Symmetry, 10=Artsy Chaos)
- MOTION_INTENSITY: 6 (1=Static/No movement, 10=Cinematic/Magic Physics)
- VISUAL_DENSITY: 4 (1=Art Gallery/Airy, 10=Pilot Cockpit/Packed Data)
AI Instruction: The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7.
LANGUAGE PRESERVATION [CRITICAL]: You MUST preserve the original language of the user's project. If the existing codebase uses Chinese (中文) for UI text, labels, headings, descriptions, or any user-facing content, you MUST keep all content in Chinese. NEVER replace or translate existing Chinese text into English. This rule applies to all generated code, including new components, pages, and modifications to existing files.
2. DEFAULT ARCHITECTURE & CONVENTIONS
Unless the user explicitly specifies a different stack, adhere to these structural constraints to maintain consistency:
- DEPENDENCY VERIFICATION [MANDATORY]: Before importing ANY 3rd party library (e.g.
framer-motion,lucide-react,zustand), you MUST checkpackage.json. If the package is missing, you MUST output the installation command (e.g.npm install package-name) before providing the code. Never assume a library exists. - Framework & Interactivity: React or Next.js. Default to Server Components (
RSC). - RSC SAFETY: Global state works ONLY in Client Components. In Next.js, wrap providers in a
"use client"component. - INTERACTIVITY ISOLATION: If Sections 4 or 7 (Motion/Liquid Glass) are active, the specific interactive UI component MUST be extracted as an isolated leaf component with
'use client'at the very top. Server Components must exclusively render static layouts. - State Management: Use local
useState/useReducerfor isolated UI. Use global state strictly for deep prop-drilling avoidance. - Styling Policy: Use Tailwind CSS (v3/v4) for 90% of styling.
- TAILWIND VERSION LOCK: Check
package.jsonfirst. Do not use v4 syntax in v3 projects. - T4 CONFIG GUARD: For v4, do NOT use
tailwindcssplugin inpostcss.config.js. Use@tailwindcss/postcssor the Vite plugin. - ANTI-EMOJI POLICY [CRITICAL]: NEVER use emojis in code, markup, text content, or alt text. Replace symbols with high-quality icons (Radix, Phosphor) or clean SVG primitives. Emojis are BANNED.
- Responsiveness & Spacing:
- Standardize breakpoints (
sm,md,lg,xl). - Contain page layouts using
max-w-[1400px] mx-autoormax-w-7xl. - Viewport Stability [CRITICAL]: NEVER use
h-screenfor full-height Hero sections. ALWAYS usemin-h-[100dvh]to prevent catastrophic layout jumping on mobile browsers (iOS Safari). - Grid over Flex-Math: NEVER use complex flexbox percentage math (
w-[calc(33%-1rem)]). ALWAYS use CSS Grid (grid grid-cols-1 md:grid-cols-3 gap-6) for reliable structures. - Icons: You MUST use exactly
@phosphor-icons/reactor@radix-ui/react-iconsas the import paths (check installed version). StandardizestrokeWidthglobally (e.g., exclusively use1.5or2.0).
3. DESIGN ENGINEERING DIRECTIVES (Bias Correction)
LLMs have statistical biases toward specific UI cliché patterns. Proactively construct premium interfaces using these engineered rules:
Rule 1: Deterministic Typography
- Display/Headlines: Default to
text-4xl md:text-6xl tracking-tighter leading-none. - ANTI-SLOP: Discourage
Interfor "Premium" or "Creative" vibes. Force unique character usingGeist,Outfit,Cabinet Grotesk, orSatoshi. - TECHNICAL UI RULE: Serif fonts are strictly BANNED for Dashboard/Software UIs. For these contexts, use exclusively high-end Sans-Serif pairings (
Geist+Geist MonoorSatoshi+JetBrains Mono). - Body/Paragraphs: Default to
text-base text-gray-600 leading-relaxed max-w-[65ch].
Rule 2: Color Calibration
- Constraint: Max 1 Accent Color. Saturation < 80%.
- THE LILA BAN: The "AI Purple/Blue" aesthetic is strictly BANNED. No purple button glows, no neon gradients. Use absolute neutral bases (Zinc/Slate) with high-contrast, singular accents (e.g. Emerald, Electric Blue, or Deep Rose).
- COLOR CONSISTENCY: Stick to one palette for the entire output. Do not fluctuate between warm and cool grays within the same project.
Rule 3: Layout Diversification
- ANTI-CENTER BIAS: Centered Hero/H1 sections are strictly BANNED when
LAYOUT_VARIANCE > 4. Force "Split Screen" (50/50), "Left Aligned content/Right Aligned asset", or "Asymmetric White-space" structures.
Rule 4: Materiality, Shadows, and "Anti-Card Overuse"
- DASHBOARD HARDENING: For
VISUAL_DENSITY > 7, generic card containers are strictly BANNED. Use logic-grouping viaborder-t,divide-y, or purely negative space. Data metrics should breathe without being boxed in unless elevation (z-index) is functionally required. - Execution: Use cards ONLY when elevation communicates hierarchy. When a shadow is used, tint it to the background hue.
Rule 5: Interactive UI States
- Mandatory Generation: LLMs naturally generate "static" successful states. You MUST implement full interaction cycles:
- Loading: Skeletal loaders matching layout sizes (avoid generic circular spinners).
- Empty States: Beautifully composed empty states indicating how to populate data.
- Error States: Clear, inline error reporting (e.g., forms).
- Tactile Feedback: On
:active, use-translate-y-[1px]orscale-[0.98]to simulate a physical push indicating success/action.
Rule 6: Data & Form Patterns
- Forms: Label MUST sit above input. Helper text is optional but should exist in markup. Error text below input. Use a standard
gap-2for input blocks.
4. CREATIVE PROACTIVITY (Anti-Slop Implementation)
To actively combat generic AI designs, systematically implement these high-end coding concepts as your baseline:
- "Liquid Glass" Refraction: When glassmorphism is needed, go beyond
backdrop-blur. Add a 1px inner border (border-white/10) and a subtle inner shadow (shadow-[inset_0_1px_0_rgba(255,255,255,0.1)]) to simulate physical edge refraction. - Magnetic Micro-physics (If MOTION_INTENSITY > 5): Implement buttons that pull slightly toward the mouse cursor. CRITICAL: NEVER use React
useStatefor magnetic hover or continuous animations. Use EXCLUSIVELY Framer Motion'suseMotionValueanduseTransformoutside the React render cycle to prevent performance collapse on mobile. - Perpetual Micro-Interactions: When
MOTION_INTENSITY > 5, embed continuous, infinite micro-animations (Pulse, Typewriter, Float, Shimmer, Carousel) in standard components (avatars, status dots, backgrounds). Apply premium Spring Physics (type: "spring", stiffness: 100, damping: 20) to all interactive elements—no linear easing. - Layout Transitions: Always utilize Framer Motion's
layoutandlayoutIdprops for smooth re-ordering, resizing, and shared element transitions across state changes. - Staggered Orchestration: Do not mount lists or grids instantly. Use
staggerChildren(Framer) or CSS cascade (animation-delay: calc(var(--index) * 100ms)) to create sequential waterfall reveals. CRITICAL: ForstaggerChildren, the Parent (variants) and Children MUST reside in the identical Client Component tree. If data is fetched asynchronously, pass the data as props into a centralized Parent Motion wrapper.
5. PERFORMANCE GUARDRAILS
- DOM Cost: Apply grain/noise filters exclusively to fixed, pointer-event-none pseudo-elements (e.g.,
fixed inset-0 z-50 pointer-events-none) and NEVER to scrolling containers to prevent continuous GPU repaints and mobile performance degradation. - Hardware Acceleration: Never animate
top,left,width, orheight. Animate exclusively viatransformandopacity. - Z-Index Restraint: NEVER spam arbitrary
z-50orz-10unprompted. Use z-indexes strictly for systemic layer contexts (Sticky Navbars, Modals, Overlays).
6. TECHNICAL REFERENCE (Dial Definitions)
DESIGN_VARIANCE (Level 1-10)
- 1-3 (Predictable): Flexbox
justify-center, strict 12-column symmetrical grids, equal paddings. - 4-7 (Offset): Use
margin-top: -2removerlapping, varied image aspect ratios (e.g., 4:3 next to 16:9), left-aligned headers over center-aligned data. - 8-10 (Asymmetric): Masonry layouts, CSS Grid with fractional units (e.g.,
grid-template-columns: 2fr 1fr 1fr), massive empty zones (padding-left: 20vw). - MOBILE OVERRIDE: For levels 4-10, any asymmetric layout above
md:MUST aggressively fall back to a strict, single-column layout (w-full,px-4,py-8) on viewports< 768pxto prevent horizontal scrolling and layout breakage.
MOTION_INTENSITY (Level 1-10)
- 1-3 (Static): No automatic animations. CSS
:hoverand:activestates only. - 4-7 (Fluid CSS): Use
transition: all 0.3s cubic-bezier(0.16, 1, 0.3, 1). Useanimation-delaycascades for load-ins. Focus strictly ontransformandopacity. Usewill-change: transformsparingly. - 8-10 (Advanced Choreography): Complex scroll-triggered reveals or parallax. Use Framer Motion hooks. NEVER use
window.addEventListener('scroll').
VISUAL_DENSITY (Level 1-10)
- 1-3 (Art Gallery Mode): Lots of white space. Huge section gaps. Everything feels very expensive and clean.
- 4-7 (Daily App Mode): Normal spacing for standard web apps.
- 8-10 (Cockpit Mode): Tiny paddings. No card boxes; just 1px lines to separate data. Everything is packed. Mandatory: Use Monospace (
font-mono) for all numbers.
7. THE 100 AI TELLS (Forbidden Patterns)
To guarantee a premium, non-generic output, you MUST strictly avoid these common AI design signatures unless explicitly requested:
Visual & CSS
- NO Neon/Outer Glows: Do not use default
box-shadowglows or auto-glows. Use inner borders or subtle tinted shadows. - NO Pure Black: Never use
#000000. Use Off-Black, Zinc-950, or Charcoal. - NO Oversaturated Accents: Desaturate accents to blend elegantly with neutrals.
- NO Excessive Gradient Text: Do not use text-fill gradients for large headers.
- NO Custom Mouse Cursors: They are outdated and ruin performance/accessibility.
Typography
- NO Inter Font: Banned. Use
Geist,Outfit,Cabinet Grotesk, orSatoshi. - NO Oversized H1s: The first heading should not scream. Control hierarchy with weight and color, not just massive scale.
- Serif Constraints: Use Serif fonts ONLY for creative/editorial designs. NEVER use Serif on clean Dashboards.
Layout & Spacing
- Align & Space Perfectly: Ensure padding and margins are mathematically perfect. Avoid floating elements with awkward gaps.
- NO 3-Column Card Layouts: The generic "3 equal cards horizontally" feature row is BANNED. Use a 2-column Zig-Zag, asymmetric grid, or horizontal scrolling approach instead.
Content & Data (The "Jane Doe" Effect)
- NO Generic Names: "John Doe", "Sarah Chan", or "Jack Su" are banned. Use highly creative, realistic-sounding names.
- NO Generic Avatars: DO NOT use standard SVG "egg" or Lucide user icons for avatars. Use creative, believable photo placeholders or specific styling.
- NO Fake Numbers: Avoid predictable outputs like
99.99%,50%, or basic phone numbers (1234567). Use organic, messy data (47.2%,+1 (312) 847-1928). - NO Startup Slop Names: "Acme", "Nexus", "SmartFlow". Invent premium, contextual brand names.
- NO Filler Words: Avoid AI copywriting clichés like "Elevate", "Seamless", "Unleash", or "Next-Gen". Use concrete verbs.
External Resources & Components
- NO Broken Unsplash Links: Do not use Unsplash. Use absolute, reliable placeholders like
https://picsum.photos/seed/{random_string}/800/600or SVG UI Avatars. - shadcn/ui Customization: You may use
shadcn/ui, but NEVER in its generic default state. You MUST customize the radii, colors, and shadows to match the high-end project aesthetic. - Production-Ready Cleanliness: Code must be extremely clean, visually striking, memorable, and meticulously refined in every detail.
8. THE CREATIVE ARSENAL (High-End Inspiration)
Do not default to generic UI. Pull from this library of advanced concepts to ensure the output is visually striking and memorable. When appropriate, leverage GSAP (ScrollTrigger/Parallax) for complex scrolltelling or ThreeJS/WebGL for 3D/Canvas animations, rather than basic CSS motion. CRITICAL: Never mix GSAP/ThreeJS with Framer Motion in the same component tree. Default to Framer Motion for UI/Bento interactions. Use GSAP/ThreeJS EXCLUSIVELY for isolated full-page scrolltelling or canvas backgrounds, wrapped in strict useEffect cleanup blocks.
The Standard Hero Paradigm
- Stop doing centered text over a dark image. Try asymmetric Hero sections: Text cleanly aligned to the left or right. The background should feature a high-quality, relevant image with a subtle stylistic fade (darkening or lightening gracefully into the background color depending on if it is Light or Dark mode).
Navigation & Menüs
- Mac OS Dock Magnification: Nav-bar at the edge; icons scale fluidly on hover.
- Magnetic Button: Buttons that physically pull toward the cursor.
- Gooey Menu: Sub-items detach from the main button like a viscous liquid.
- Dynamic Island: A pill-shaped UI component that morphs to show status/alerts.
- Contextual Radial Menu: A circular menu expanding exactly at the click coordinates.
- Floating Speed Dial: A FAB that springs out into a curved line of secondary actions.
- Mega Menu Reveal: Full-screen dropdowns that stagger-fade complex content.
Layout & Grids
- Bento Grid: Asymmetric, tile-based grouping (e.g., Apple Control Center).
- Masonry Layout: Staggered grid without fixed row heights (e.g., Pinterest).
- Chroma Grid: Grid borders or tiles showing subtle, continuously animating color gradients.
- Split Screen Scroll: Two screen halves sliding in opposite directions on scroll.
- Curtain Reveal: A Hero section parting in the middle like a curtain on scroll.
Cards & Containers
- Parallax Tilt Card: A 3D-tilting card tracking the mouse coordinates.
- Spotlight Border Card: Card borders that illuminate dynamically under the cursor.
- Glassmorphism Panel: True frosted glass with inner refraction borders.
- Holographic Foil Card: Iridescent, rainbow light reflections shifting on hover.
- Tinder Swipe Stack: A physical stack of cards the user can swipe away.
- Morphing Modal: A button that seamlessly expands into its own full-screen dialog container.
Scroll-Animations
- Sticky Scroll Stack: Cards that stick to the top and physically stack over each other.
- Horizontal Scroll Hijack: Vertical scroll translates into a smooth horizontal gallery pan.
- Locomotive Scroll Sequence: Video/3D sequences where framerate is tied directly to the scrollbar.
- Zoom Parallax: A central background image zooming in/out seamlessly as you scroll.
- Scroll Progress Path: SVG vector lines or routes that draw themselves as the user scrolls.
- Liquid Swipe Transition: Page transitions that wipe the screen like a viscous liquid.
Galleries & Media
- Dome Gallery: A 3D gallery feeling like a panoramic dome.
- Coverflow Carousel: 3D carousel with the center focused and edges angled back.
- Drag-to-Pan Grid: A boundless grid you can freely drag in any compass direction.
- Accordion Image Slider: Narrow vertical/horizontal image strips that expand fully on hover.
- Hover Image Trail: The mouse leaves a trail of popping/fading images behind it.
- Glitch Effect Image: Brief RGB-channel shifting digital distortion on hover.
Typography & Text
- Kinetic Marquee: Endless text bands that reverse direction or speed up on scroll.
- Text Mask Reveal: Massive typography acting as a transparent window to a video background.
- Text Scramble Effect: Matrix-style character decoding on load or hover.
- Circular Text Path: Text curved along a spinning circular path.
- Gradient Stroke Animation: Outlined text with a gradient continuously running along the stroke.
- Kinetic Typography Grid: A grid of letters dodging or rotating away from the cursor.
Micro-Interactions & Effects
- Particle Explosion Button: CTAs that shatter into particles upon success.
- Liquid Pull-to-Refresh: Mobile reload indicators acting like detaching water droplets.
- Skeleton Shimmer: Shifting light reflections moving across placeholder boxes.
- Directional Hover Aware Button: Hover fill entering from the exact side the mouse entered.
- Ripple Click Effect: Visual waves rippling precisely from the click coordinates.
- Animated SVG Line Drawing: Vectors that draw their own contours in real-time.
- Mesh Gradient Background: Organic, lava-lamp-like animated color blobs.
- Lens Blur Depth: Dynamic focus blurring background UI layers to highlight a foreground action.
9. THE "MOTION-ENGINE" BENTO PARADIGM
When generating modern SaaS dashboards or feature sections, you MUST utilize the following "Bento 2.0" architecture and motion philosophy. This goes beyond static cards and enforces a "Vercel-core meets Dribbble-clean" aesthetic heavily reliant on perpetual physics.
A. Core Design Philosophy
- Aesthetic: High-end, minimal, and functional.
- Palette: Background in
#f9fafb. Cards are pure white (#ffffff) with a 1px border ofborder-slate-200/50. - Surfaces: Use
rounded-[2.5rem]for all major containers. Apply a "diffusion shadow" (a very light, wide-spreading shadow, e.g.,shadow-[0_20px_40px_-15px_rgba(0,0,0,0.05)]) to create depth without clutter. - Typography: Strict
Geist,Satoshi, orCabinet Groteskfont stack. Use subtle tracking (tracking-tight) for headers. - Labels: Titles and descriptions must be placed outside and below the cards to maintain a clean, gallery-style presentation.
- Pixel-Perfection: Use generous
p-8orp-10padding inside cards.
B. The Animation Engine Specs (Perpetual Motion)
All cards must contain "Perpetual Micro-Interactions." Use the following Framer Motion principles:
- Spring Physics: No linear easing. Use
type: "spring", stiffness: 100, damping: 20for a premium, weighty feel. - Layout Transitions: Heavily utilize the
layoutandlayoutIdprops to ensure smooth re-ordering, resizing, and shared element state transitions. - Infinite Loops: Every card must have an "Active State" that loops infinitely (Pulse, Typewriter, Float, or Carousel) to ensure the dashboard feels "alive".
- Performance: Wrap dynamic lists in
<AnimatePresence>and optimize for 60fps. PERFORMANCE CRITICAL: Any perpetual motion or infinite loop MUST be memoized (React.memo) and completely isolated in its own microscopic Client Component. Never trigger re-renders in the parent layout.
C. The 5-Card Archetypes (Micro-Animation Specs)
Implement these specific micro-animations when constructing Bento grids (e.g., Row 1: 3 cols | Row 2: 2 cols split 70/30): 1. The Intelligent List: A vertical stack of items with an infinite auto-sorting loop. Items swap positions using layoutId, simulating an AI prioritizing tasks in real-time. 2. The Command Input: A search/AI bar with a multi-step Typewriter Effect. It cycles through complex prompts, including a blinking cursor and a "processing" state with a shimmering loading gradient. 3. The Live Status: A scheduling interface with "breathing" status indicators. Include a pop-up notification badge that emerges with an "Overshoot" spring effect, stays for 3 seconds, and vanishes. 4. The Wide Data Stream: A horizontal "Infinite Carousel" of data cards or metrics. Ensure the loop is seamless (using x: ["0%", "-100%"]) with a speed that feels effortless. 5. The Contextual UI (Focus Mode): A document view that animates a staggered highlight of a text block, followed by a "Float-in" of a floating action toolbar with micro-icons.
10. FINAL PRE-FLIGHT CHECK
Evaluate your code against this matrix before outputting. This is the last filter you apply to your logic.
- [ ] Is global state used appropriately to avoid deep prop-drilling rather than arbitrarily?
- [ ] Is mobile layout collapse (
w-full,px-4,max-w-7xl mx-auto) guaranteed for high-variance designs? - [ ] Do full-height sections safely use
min-h-[100dvh]instead of the buggedh-screen? - [ ] Do
useEffectanimations contain strict cleanup functions? - [ ] Are empty, loading, and error states provided?
- [ ] Are cards omitted in favor of spacing where possible?
- [ ] Did you strictly isolate CPU-heavy perpetual animations in their own Client Components?
Taste-Skill (高审美前端)
这个项目让你的 AI(Cursor、Claude Code、Codex、Windsurf 等)拥有真正的设计品味。它能阻止 AI 生成那些千篇一律、毫无特色的"泡沫代码",强制它构建现代、高端的界面。
整个系统只靠一个文件运行:SKILL.md。
反馈与贡献
欢迎提出建议或反馈 Bug:
- 在 GitHub 上提 Pull Request 或 Issue
- 在 x.com/lexnlin 给我发私信
- 邮件联系:hello@learn2vibecode.dev
安装方式
方式一:npx 一键安装(推荐)
npx skills add https://github.com/BND-1/taste-skill.git自动将 SKILL.md 安装到你的 AI 代理(Claude Code、Cursor 等)的 skills 目录中。
也可以全局安装,这样所有项目都能生效:
npx skills add https://github.com/BND-1/taste-skill.git -g方式二:手动下载
1. 从本仓库下载 SKILL.md 文件 2. 放到你的项目文件夹中 3. 告诉你的 AI:"请严格遵循 SKILL.md 中的规则"(在 Cursor 中可以直接 @SKILL.md)
就这么简单,AI 会立刻升级它的前端代码质量。
三个控制旋钮
在 SKILL.md 的最顶部,你会看到三个设置参数:
DESIGN_VARIANCE: 8MOTION_INTENSITY: 6VISUAL_DENSITY: 4
你可以把这些数值调整为 1 到 10,具体含义如下:
1. DESIGN_VARIANCE 设计差异度(1 到 10)
控制布局的大胆程度。
- 1 到 3(常规): 安全、居中的布局,标准网格,一切整齐排列。
- 4 到 7(创意): 元素开始有重叠,文字可能偏向一侧,图片大小各异。
- 8 到 10(狂野): 非对称布局、大面积留白、瀑布流网格,非常艺术和现代。
2. MOTION_INTENSITY 动效强度(1 到 10)
控制页面上有多少东西在动。
- 1 到 3(静态): 几乎没有动画,只有悬停时的简单颜色变化。
- 4 到 7(流畅): 页面加载时有漂亮的淡入效果,丝滑的滚动体验。
- 8 到 10(电影级): 按钮会被鼠标磁性吸引,元素以弹簧物理弹入,高级滚动特效。
3. VISUAL_DENSITY 视觉密度(1 到 10)
控制一屏内塞了多少内容,也就是"呼吸感"。
- 1 到 3("美术馆"模式):
大量留白,一张大图、一个大标题,需要滚动才能看到下一项内容。感觉高端奢华,像 Apple、Gucci 的风格。
- 4 到 7("日常应用"模式):
正常间距,像 Instagram 或新闻网站,不太拥挤,但内容充足。
- 8 到 10("驾驶舱"模式):
所有东西都很小且紧凑,没有大卡片,只有细线和列表。一屏能看到上百个数据,不用滚动。适合专业场景(交易应用、仪表盘、科幻界面)。
示例
(示例项目和模板将在后续更新中添加,敬请期待!)
Related skills
FAQ
What does design-taste-frontend improve?
design-taste-frontend improves frontend layout, typography, color, spacing, and component choices so interfaces feel intentional and visually coherent rather than generic or inconsistently styled across screens.
When should developers invoke design-taste-frontend?
Developers should invoke design-taste-frontend when UI code works but looks unpolished—agents apply taste heuristics to spacing, type scales, palettes, and components before review or release.