badesign-skill
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseBADESIGN
BADESIGN
How to weigh this guidance
如何权衡本指南的优先级
When two considerations pull in different directions, resolve them in this order and move on:
- The user's explicit instructions.
- The project's existing design system and conventions.
- The hard limits below. They are measurable and have no exceptions.
- What the brief's users need to accomplish.
- The visual idea you chose for this brief.
- The defaults in this skill.
Everything outside the hard limits is a default with a reason. When the brief or your visual idea gives a better reason, follow it.
当不同考量因素出现冲突时,按以下优先级排序解决:
- 用户的明确指令。
- 项目现有的设计系统与规范约定。
- 下述硬性限制:这些是可量化的,无任何例外。
- 需求brief中用户需要完成的任务。
- 你为本次需求选定的视觉创意方向。
- 本Skill的默认规则。
硬性限制之外的所有规则均为带适用前提的默认规则。若需求brief或你的视觉创意有更充分的理由,可优先遵循相应方向。
Hard limits
硬性限制
- Text people need to read is 12px or larger, with contrast of at least 4.5:1 (3:1 for text 24px and larger).
- Interactive elements have a hit area of at least 44 by 44px on touch screens and 24 by 24px with a pointer.
- Nothing is clipped, overlapping or overflowing its container at the target screen sizes, and the page has no horizontal scroll from 320px up.
- Text and icons inside buttons, badges, chips, tabs and inputs are vertically centered, and controls in the same row share the same height.
- Every requirement in the brief is present and usable, and the code is complete, with no placeholders.
- Inputs have labels, controls are reachable by keyboard with a visible focus state, and zoom is never disabled.
- 用户需要阅读的文本字号不小于12px,对比度至少为4.5:1(24px及以上字号的文本对比度至少为3:1)。
- 交互元素的可点击区域要求:触摸屏上不小于44×44px,指针设备上不小于24×24px。
- 在目标屏幕尺寸下,所有内容不得被裁剪、重叠或溢出容器,且页面宽度从320px起不得出现横向滚动条。
- 按钮、徽章、胶囊标签、标签页和输入框内的文本与图标需垂直居中,同一行的控件高度保持一致。
- 需求brief中的所有要求均需实现且可用,代码需完整,不得有占位符。
- 输入框需关联标签,所有控件可通过键盘访问且有可见的焦点状态,不得禁用页面缩放。
Understand before designing
设计前需明确的要点
- The job. Who uses this, for what task, how often, on what device, in what conditions. A tool used every day, a page that has to persuade, a flow that has to be finished and a piece meant to be experienced call for different amounts of expression.
- The content. What the screen must contain, what matters most, and realistic data including imperfect cases: long names, missing values, errors, items that need attention.
- The whole product. A screen belongs to a real product. It keeps that product's navigation, secondary actions and the small functional details a shipped app has, even when the brief describes only one screen.
- The visual idea. One concept taken from the subject's own world (its objects, materials, places, era, printed matter, vocabulary) rather than from how interfaces in this category usually look. It decides color, type, shape, density, imagery and composition together, so the screen feels designed as one thing.
- 任务属性:目标用户是谁、用于完成什么任务、使用频率、使用设备、使用场景。日常使用的工具、需要说服用户的页面、需要用户完成的流程、以及侧重体验的内容,所需的表达程度各不相同。
- 内容要求:屏幕必须包含哪些内容、优先级最高的内容是什么、以及真实数据(包括非理想情况:长名称、缺失值、错误、需要关注的条目等)。
- 产品全貌:单个屏幕属于完整产品的一部分。即使需求brief只描述了一个屏幕,也需要保留该产品的导航、次要操作以及已上线应用具备的细节功能。
- 视觉创意:从主题本身的语境(相关物品、材质、场景、时代、印刷品、词汇)中提取概念,而非照搬同类界面的常见样式。该概念需统一决定色彩、字体、形状、密度、图像和构图,让整个屏幕呈现统一的设计感。
Principles
设计原则
Composition
- Each view has one focal point, reached through clear contrast in scale, weight and position between levels of importance.
- The layout is shaped by the content: a sequence reads as a sequence, a comparison as a comparison, a queue as a queue. Repeating the same block structure section after section is the sign of a template.
- Use a grid and align to it. Break it deliberately where emphasis needs it.
- Rhythm varies: dense areas next to open ones, large type next to small.
Craft
- Be opinionated. When two paths are equally valid, commit to one and carry it through every detail.
- Fewer elements, fully resolved, beat many half-finished ones. Within the brief's requirements, spend effort on finishing rather than adding.
- The details nobody asks for are the ones that show quality: a number that does not jump, a border that does not move on hover, a focus state that looks designed.
Expression
- Express the visual idea with conviction in type, color and at least one element that could only belong to this subject.
- Tools and flows carry the idea through typography, color, density and detail while their layout stays predictable. Persuasive and expressive pages can also carry it through composition, imagery, scale and motion.
- Comfortable values are the starting point on every axis. Extremes such as square corners everywhere, very small or very thin type, condensed faces for body text, heavy or stacked shadows, and very tight spacing need a reason that comes from the idea.
- Decoration is welcome when it comes from the idea. The patterns listed under "Habits of generated interfaces" do not count as an idea.
Structure and grouping
- Group with proximity first: space inside a group is smaller than space between groups.
- Shadows belong to elements that float above the page, such as menus, dialogs, popovers and dragged items.
- Containers such as cards, panels and bordered boxes mark real objects and real groups. Page regions are separated by space, bands of color or rules.
- One separation method per boundary.
Typography
- Choose typefaces for a reason that comes from the visual idea.
- Use a small scale with visible steps. Running text is about 16px on web and 17pt on iOS; dense product interfaces use 13 to 14px. Secondary text stays close to the body size; small sizes are for short metadata only.
- Keep lines of running text to 45 to 75 characters, with line height around 1.5 for text and 1.1 to 1.25 for headings.
- Use tabular figures for numbers that are compared, right-aligned in tables, with units.
Color
- Assign color by role: surfaces, text levels, the accent for action and selection, and status colors that always come with text or an icon.
- The color strategy follows the idea. It can be quiet neutrals with one accent, or one color owning large areas.
- Build ramps in a perceptual space such as OKLCH. On dark grounds, surfaces lighten as they rise.
Data and detail
- Short values such as names, IDs, dates, phone numbers and amounts stay on one line. Long text truncates with the full value reachable.
- Values that identify themselves need no label.
- Radii of nested elements shrink inward. Icons come from one set, sized to the text beside them. Edges and baselines line up.
Behavior
- Every view that loads data has designed loading, empty and error states. Controls show hover, focus, pressed and disabled states.
- Use each platform's own navigation conventions and keep primary mobile actions within thumb reach.
- In mobile flows the top bar and the primary action stay in place while content scrolls, with space reserved so nothing is covered.
- Layouts reflow by priority across screen sizes.
Motion and interaction
- Motion explains cause and effect: what appeared, where it came from, what changed, that an action registered. Its amount follows frequency: actions repeated many times a day respond instantly, occasional ones get a short transition, and rare moments such as a first load or a completed task may carry one crafted animation.
- Every interactive element responds to input: a hover change on pointer devices, a press state (a slight scale to about 0.97 or a darker fill), and a focus state.
- Durations: 100 to 160ms for press and hover, 150 to 250ms for menus and popovers, 200 to 300ms for dialogs, sheets and panels. Exits are faster than entrances.
- Easing: ease-out for anything entering or responding to the user, such as cubic-bezier(0.23, 1, 0.32, 1); ease-in-out for elements moving across the screen; linear only for continuous progress.
- Elements enter from where they originate: a menu grows from its trigger, a sheet slides from its edge, a new row appears in its place. Scale starts at 0.9 or above, combined with opacity.
- Animate transform and opacity; list the properties you transition. Motion stays interruptible, so a reversed hover or a second click changes course from the current state.
- Hover effects apply only on devices that hover. Under reduced-motion settings, movement becomes an instant change or a short fade.
Copy
- Buttons name their outcome. Headings name what an area is.
- The interface does not describe itself or explain how to use it.
- Write in the language of the brief. Where content is missing, invent plausible fictional content without disclaimers, and do not present real brands or people as customers or endorsers.
构图
- 每个视图有且仅有一个焦点,通过不同重要层级间在尺寸、权重和位置上的清晰对比来凸显。
- 布局由内容决定:序列类内容要体现顺序感,对比类内容要体现对比感,队列类内容要体现队列感。不同章节重复使用相同的区块结构是模板化的表现。
- 使用网格系统并对齐网格,需要强调内容时可有意打破网格规则。
- 节奏要有变化:密集区域与留白区域相邻,大字号与小字号搭配。
工艺细节
- 要有明确的设计主张。当两种方案同样合理时,选定其一并贯彻到所有细节中。
- 少而精的元素远胜过多而半成品的元素。在满足需求brief要求的前提下,把精力放在完善细节而非增加元素上。
- 那些无人特意要求的细节正是品质的体现:不会跳动的数字、悬停时不会移位的边框、经过精心设计的焦点状态。
表达风格
- 通过字体、色彩以及至少一个仅属于该主题的元素,坚定地传递视觉创意。
- 工具类和流程类界面通过排版、色彩、密度和细节来体现创意,同时保持布局的可预测性。说服性和表达性的页面还可以通过构图、图像、尺寸和动效来传递创意。
- 所有维度的默认值都应采用舒适的取值。诸如全圆角、极小或极细的字体、正文使用压缩字体、厚重或层叠的阴影、过紧的间距等极端设计,都需要有来自视觉创意的合理理由。
- 源自视觉创意的装饰是可取的。「AI生成界面的常见陋习」中列出的模式不算作创意。
结构与分组
- 优先通过邻近性原则分组:组内间距小于组间间距。
- 阴影属于悬浮在页面之上的元素,例如菜单、对话框、气泡弹出框(popover)和拖拽中的元素。
- 卡片、面板、带边框的容器等用于标记真实的对象和分组。页面区域通过留白、色带或分割线来区分。
- 每个边界仅使用一种分隔方式。
排版
- 选择字体需有来自视觉创意的合理理由。
- 使用跨度适中、层级清晰的字号体系。网页正文约16px,iOS正文约17pt;密集的产品界面使用13-14px。辅助文本字号接近正文字号;小字号仅用于短元数据。
- 正文字符行宽保持在45-75字符之间,正文行高约为1.5,标题行高为1.1-1.25。
- 需对比的数字使用等宽数字(tabular figures),在表格中右对齐,并附带单位。
色彩
- 按角色分配颜色:背景色、文本层级色、操作与选中的强调色、以及始终与文本或图标搭配使用的状态色。
- 色彩策略需符合视觉创意。可以是中性色加一个强调色,也可以是单一颜色占据大面积区域。
- 在感知色彩空间(如OKLCH)中构建色阶。深色模式下,层级越高的表面颜色越浅。
数据与细节
- 名称、ID、日期、电话号码、金额等短值保持单行显示。长文本截断显示,且可查看完整内容。
- 可自我说明的数值无需额外标签。
- 嵌套元素的圆角半径向内递减。图标来自同一套图标库,尺寸与旁边的文本匹配。边缘与基线对齐。
行为交互
- 所有加载数据的视图都需要设计加载态、空状态和错误状态。控件需具备悬停、焦点、按下和禁用状态。
- 遵循各平台自身的导航规范,移动端的主要操作需放在拇指可及范围内。
- 移动端流程中,顶部栏和主要操作需在内容滚动时保持固定,并预留足够空间避免内容被遮挡。
- 布局需根据屏幕尺寸按优先级自适应重排。
动效与交互
- 动效用于解释因果关系:什么元素出现了、它从哪里来、什么发生了变化、操作已被响应。动效的时长与使用频率成反比:每天重复多次的操作需即时响应,偶尔的操作可以有短过渡,首次加载或任务完成等罕见场景可以有精心设计的动画。
- 每个交互元素都需对输入做出响应:指针设备上的悬停变化、按下状态(略微缩小到约0.97倍或加深填充色)、以及焦点状态。
- 时长参考:按下和悬停为100-160ms,菜单和弹出框为150-250ms,对话框、底部抽屉和面板为200-300ms。退出动画比进入动画更快。
- 缓动函数:进入类或响应用户的动效用ease-out,例如cubic-bezier(0.23, 1, 0.32, 1);在屏幕上移动的元素用ease-in-out;仅连续进度条使用linear。
- 元素从其来源位置进入:菜单从触发点展开,底部抽屉从边缘滑入,新行出现在其对应位置。缩放从0.9或更大的比例开始,配合透明度变化。
- 仅对transform和opacity属性做动画;明确列出要过渡的属性。动效需可中断,因此反向悬停或第二次点击会从当前状态开始改变方向。
- 悬停效果仅适用于支持悬停的设备。在减少动效(reduced-motion)设置下,动效应改为即时变化或短淡入淡出。
文案
- 按钮文案需明确说明点击后的结果。标题需明确说明区域的内容。
- 界面不应自我描述或解释使用方法。
- 使用与需求brief一致的语言。内容缺失时,需编造合理的虚构内容,无需加免责声明,且不得将真实品牌或人物作为客户或代言人。
Habits of generated interfaces
AI生成界面的常见陋习
These appear so often in AI-generated UI that they read as the absence of a decision. Use one only when the brief asks for it or your visual idea needs it and you can name why.
- Purple, indigo or violet-to-blue accents and gradients.
- Palettes built from one hue family: all slate, all beige, all purple.
- Dark ground with a neon accent.
- Gradient text, glows, glass panels, blurred orbs and blobs, grid or dot backgrounds.
- A thin border combined with a wide soft shadow.
- Every section wrapped in a rounded card, and cards nested inside cards.
- Rows of identical cards with an icon in a tinted square, a title and two lines.
- Rows of big-number stat tiles, especially with captions that repeat the number.
- A centered hero with a badge above the headline, or one highlighted word in the headline.
- Small uppercase tracked labels above headings, and numbered section labels.
- Pills and badges on ordinary metadata.
- A descriptive subtitle under every heading.
- A greeting as the most prominent text of a tool.
- Fade-and-rise on every section, pulsing dots, marquees, scale on hover.
- Buzzwords, slogans and em dashes in copy.
These are never used, because they have no legitimate use in a finished interface:
- A colored stripe on one side of a card, row or callout to mark it.
- A drawn device frame, fake status bar, fake browser window or terminal dots around content that is itself the screen.
- Emoji standing in for icons.
- Lorem ipsum, "John Doe" or "Acme".
这些模式在AI生成的UI中极为常见,以至于显得毫无设计思考。仅当需求brief明确要求,或你的视觉创意需要且能说明理由时,才可使用。
- 紫色、靛蓝色或紫到蓝的强调色与渐变。
- 单一色相构建的调色板:全是石板灰、全是米色、全是紫色。
- 深色背景配霓虹强调色。
- 渐变文字、发光效果、玻璃面板、模糊球体、网格或点状背景。
- 细边框搭配宽柔阴影。
- 每个区块都包裹在圆角卡片中,且卡片嵌套卡片。
- 一排排完全相同的卡片:带底色的方块图标、标题加两行描述。
- 一排排大数字统计卡片,尤其是说明文字重复数字内容的。
- 居中的首屏区域,标题上方有个徽章,或者标题里有一个高亮词。
- 标题上方的小型大写字母间距标签,以及带编号的章节标签。
- 普通元数据上也加胶囊标签和徽章。
- 每个标题下都有描述性副标题。
- 问候语成为工具中最醒目的文本。
- 每个区块都有淡入上浮效果、脉冲点、跑马灯、悬停缩放。
- 文案中充斥着流行词、口号和破折号。
以下内容绝对禁止使用,因为在成品界面中没有合理的应用场景:
- 卡片、行或提示框的一侧用彩色条纹做标记。
- 在本身就是屏幕内容的周围加上手绘设备边框、假状态栏、假浏览器窗口或终端圆点。
- 用Emoji代替图标。
- Lorem ipsum、John Doe或Acme这类占位内容。
Before delivering
交付前检查
If you can render, look at the result at the target sizes. Check the hard limits, the focal point, and the habits list, fix what you find, and deliver.
如果你可以渲染效果,在目标尺寸下查看结果。检查硬性限制、焦点、以及陋习列表,修复发现的问题后再交付。