Token导航 LogoToken导航

Agent Skill · 前端设计

ui-visual-design-system(ui 视觉设计系统)

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

ui-visual-design-system 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 427。

总安装 25,513周安装 773GitHub Stars 3下载 7,032核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ui-visual-design-system(ui 视觉设计系统)
来源仓库:https://github.com/phazurlabs/ux-ui-mastery
仓库路径:skills/ui-visual-design-system
安装命令:
npx skills add https://github.com/phazurlabs/ux-ui-mastery --skill 'UI Visual Design System'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/phazurlabs/ux-ui-mastery --skill 'UI Visual Design System'

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

用于辅助界面设计、视觉规范和交互体验优化。ui-visual-design-system 属于前端设计类 Skill,可作为该场景下的辅助能力补充。适合整理页面结构、生成 UI 方案或检查视觉一致性。使用时需结合品牌、设计系统和用户任务,避免堆砌装饰元素。涉及页面改动时应通过截图或浏览器预览检查文本溢出和对齐。

建议配合现有设计系统使用,确保响应式表现符合预期。

来源仓库内路径:skills/ui-visual-design-system

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/phazurlabs/ux-ui-mastery --skill 'UI Visual De…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

ui-visual-design-system 怎么安装?

在终端执行 npx skills add https://github.com/phazurlabs/ux-ui-mastery --skill 'UI Visual Design Syste…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ui-visual-design-system 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ui-visual-design-system 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

ui-visual-design-system 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

ui-visual-design-system 用的人多吗?

公开数据是累计安装 25,513 次,近一周安装 773 次,下载 7,032 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ui-visual-design-system 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
ui-visual-design-system

ui 视觉设计系统 · 本页

25,5133只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

UI Visual Design System — Visual Excellence Framework

Visual Design Philosophy

"Good design is as little design as possible. Less, but better — because it concentrates on the essential aspects, and the products are not burdened with non-essentials." — Dieter Rams

Visual design is the language through which interfaces communicate hierarchy, meaning, and emotional tone. Every visual decision — typeface, color, spacing, elevation — either clarifies or obscures the user's path. Pursue clarity ruthlessly.

Core Principles

  1. Hierarchy is communication — visual weight directs attention and reveals structure
  2. Consistency breeds trust — systematic visual rules create predictable, professional interfaces
  3. White space is not empty space — it is the most powerful tool for grouping, separating, and emphasizing
  4. Restraint over decoration — every visual element must serve function; remove those that do not
  5. Accessibility is non-negotiable — visual choices that exclude users are design failures

Typography System

Type Scale Design

Build a modular type scale using a consistent ratio. The most common scales:

  • Minor Third (1.200): Subtle, elegant — suited for content-heavy apps
  • Major Third (1.250): Balanced — good default for most applications
  • Perfect Fourth (1.333): Strong contrast — suited for marketing and editorial
  • Augmented Fourth (1.414): Dramatic — suited for expressive, creative products

Example scale (Major Third, base 16px):

xs:    10px (0.625rem)
sm:    13px (0.8125rem)
base:  16px (1rem)
lg:    20px (1.25rem)
xl:    25px (1.5625rem)
2xl:   31px (1.9375rem)
3xl:   39px (2.4375rem)
4xl:   49px (3.0625rem)

Typography Best Practices

Font Selection:

  • Limit to 2 typefaces maximum: one for headings, one for body (or one typeface at different weights)
  • Sans-serif for UI elements and body text on screens (Inter, SF Pro, Roboto, Geist)
  • Variable fonts reduce file size and enable fluid weight/width adjustment
  • Ensure selected fonts support all required character sets and languages

Readability Rules:

  • Body text: 16px minimum on web, 14px acceptable on desktop apps, never below 12px
  • Line height: 1.4-1.6 for body text, 1.1-1.3 for headings
  • Line length: 45-75 characters per line (measure) for optimal readability
  • Paragraph spacing: 0.5-1.0x the body line height
  • Letter spacing: slight increase (+0.01-0.02em) for all-caps text, reduce (-0.01em) for large headings

Hierarchy Through Typography:

  • Use weight (bold/medium/regular) more than size for subtle hierarchy
  • Reserve size jumps for major structural distinctions (page title vs. section heading)
  • Color/opacity variation as tertiary hierarchy tool (primary text vs. secondary/caption)
  • Limit distinct text styles to 6-8 across the entire application

Color System

Color Architecture

Semantic Color Categories:

  • Primary: Brand identity color — used for key actions, active states, links
  • Secondary: Complementary accent — used for secondary actions, highlights
  • Neutral: Gray scale — used for text, borders, backgrounds, surfaces
  • Success: Green spectrum — confirmations, completed states
  • Warning: Amber/orange spectrum — caution, pending states
  • Error: Red spectrum — errors, destructive actions, required indicators
  • Info: Blue spectrum — informational messages, tips

Color Scale Generation:

  • Generate 10-step scale per color (50-900) for systematic flexibility
  • 50 = lightest (background tint), 500 = base value, 900 = darkest (text on light)
  • Ensure perceptual uniformity across steps (use OKLCH or CIELAB color space)
  • Tools: Leonardo by Adobe, Radix Colors, Tailwind color generator

Accessibility Color Requirements

Contrast Ratios (WCAG 2.2):

  • Normal text (<24px): 4.5:1 minimum against background
  • Large text (>=24px or >=18.67px bold): 3:1 minimum
  • UI components and graphical objects: 3:1 minimum against adjacent colors
  • Enhanced (AAA): 7:1 for normal text, 4.5:1 for large text

Color Independence:

  • Never use color as the sole indicator of meaning — pair with icons, text, or patterns
  • Error states: red color + error icon + descriptive text
  • Charts and graphs: use patterns, labels, and distinguishable hues (not just red/green)
  • Test with color blindness simulators (protanopia, deuteranopia, tritanopia)

Dark Mode Design

  • Do not simply invert colors — redesign the elevation and emphasis model
  • Dark mode backgrounds: not pure black (#000) — use desaturated dark grays (#121212-#1E1E1E)
  • Reduce color saturation by 10-20% for dark backgrounds to prevent vibration
  • Elevated surfaces get lighter in dark mode (opposite of light mode shadow approach)
  • Text contrast: use 87% white (not 100%) for primary text on dark backgrounds to reduce eye strain

Spacing System

Spacing Scale

Use a base-4 or base-8 scale for consistent spacing:

Base-4 scale (recommended for dense UIs):

4px, 8px, 12px, 16px, 20px, 24px, 32px, 40px, 48px, 64px, 80px, 96px

Base-8 scale (recommended for spacious UIs):

8px, 16px, 24px, 32px, 48px, 64px, 80px, 96px, 128px

Spacing Application Rules

  • Component internal padding: 8-16px (compact) or 12-24px (comfortable)
  • Between related elements: 8-12px (grouping by proximity — Gestalt law)
  • Between unrelated groups: 24-32px (separation)
  • Section spacing: 48-80px
  • Page margins: 16px (mobile), 24-32px (tablet), 48-80px (desktop)

Layout Grid

  • 12-column grid for maximum flexibility (divisible by 2, 3, 4, 6)
  • Column gutter: 16-24px (responsive, wider on larger screens)
  • Max content width: 1200-1440px for readability, centered with side padding
  • Use CSS Grid and Flexbox — avoid float-based layouts
  • Subgrid (CSS subgrid) for component-level alignment to parent grid

Visual Hierarchy

The Visual Hierarchy Toolkit (ordered by impact)

  1. Size — larger elements command attention first
  2. Color/Contrast — high-contrast and saturated colors draw the eye
  3. Position — top-left (LTR languages) and center-screen hold priority
  4. Weight — bolder elements stand out from regular weight
  5. White space — isolated elements surrounded by space demand attention
  6. Motion — animated elements capture attention (use sparingly)

Hierarchy Application

  • Every screen should have exactly one primary focal point — the main action or content
  • Create clear layers: primary (what to notice), secondary (supporting context), tertiary (background/metadata)
  • Squint test: when blurred, the visual structure should remain distinguishable
  • Test hierarchy with grayscale rendering to verify it does not rely solely on color

Elevation and Depth

Elevation System

Level 0: Flat surface (0px shadow) — background, canvas
Level 1: Low (0 1px 3px rgba(0,0,0,0.12)) — cards, tiles
Level 2: Medium (0 4px 6px rgba(0,0,0,0.12)) — dropdowns, popovers
Level 3: High (0 8px 16px rgba(0,0,0,0.12)) — modals, dialogs
Level 4: Highest (0 16px 32px rgba(0,0,0,0.16)) — toasts, floating elements
  • Higher elevation = closer to user = more important/temporary
  • Use elevation consistently: persistent UI at level 0-1, transient UI at level 2-4
  • Dark mode: use surface tint (lighter background) instead of shadow for elevation

Iconography

Icon Design Rules

  • Consistent style: outline OR filled, not mixed (pick one system-wide)
  • Minimum touch target: 44x44pt even if icon is visually 24x24
  • Always pair icons with text labels in navigation — icons alone are ambiguous
  • Standard sizes: 16px (inline), 20px (buttons), 24px (navigation), 32px (feature)
  • Consistent stroke width across all icons (typically 1.5-2px at 24px size)

Cross-Referencing

  • For design token implementation, reference design-systems-architecture
  • For accessibility requirements, reference accessibility-inclusive-design
  • For motion and animation, reference interaction-motion-design
  • For mobile-specific visual design, reference mobile-ux-design

v3.0 Cross-References

The v3.0 upgrade introduces production CSS implementation references, Figma workflow integration, and multi-brand design system architecture that extend visual design systems into implementation and scale.

Modern CSS Implementation — component-patterns-code/references/css-modern-patterns.md

The component-patterns-code/references/css-modern-patterns.md reference provides production CSS patterns that implement the visual design system principles above. Key coverage includes: container queries for component-level responsive design (replacing media query dependence); :has() selector for parent-aware styling enabling contextual visual variations; anchor positioning for tooltip, popover, and dropdown placement without JavaScript; view transitions API for smooth page and state transitions; OKLCH color space for perceptually uniform color manipulation (superior to HSL for generating accessible color scales as described in the Color System section); and @layer for cascade management in multi-team design system environments. Essential for translating visual design specifications into maintainable, modern CSS.

Figma Design Tool Workflows — figma-design-tool-workflows

The figma-design-tool-workflows skill covers Figma-specific workflows for visual design system implementation. Includes: Figma variable modes for encoding the spacing scales, type scales, and color systems defined in this skill as structured design tokens; design token extraction pipelines that export Figma variables to Style Dictionary or Tokens Studio formats; and the MCP-powered design-to-code flywheel that maintains synchronization between Figma design system files and production CSS/component libraries. Directly applicable to maintaining visual consistency across design and code.

Multi-Brand Theming Architecture — design-systems-architecture/references/maturity-model-multi-brand.md

The design-systems-architecture/references/maturity-model-multi-brand.md reference addresses scaling visual design systems across multiple brands, products, or white-label deployments. Covers multi-tier token architecture (global tokens, brand tokens, component tokens), theme switching strategies, and maturity model stages from single-product design systems through enterprise multi-brand platforms. Essential when the visual design system defined in this skill needs to support brand variants while maintaining structural consistency.

Key Sources

  • Rams, D. "Ten Principles for Good Design"
  • Muller-Brockmann, J. "Grid Systems in Graphic Design"
  • Material Design 3 color and typography specifications
  • Apple Human Interface Guidelines visual design
  • W3C WCAG 2.2 contrast requirements

平台分布

Codex

34.79%
按下载量换算2,446

Claude

27.46%
按下载量换算1,931

Cursor

18.26%
按下载量换算1,284

Gemini CLI

9.51%
按下载量换算669

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills