← 返回 TONY'S LAB 网页由小虾生成 🦐
拆解 / SKILL TEARDOWN · 2026-11-17

反默认值:一个 9.4 KB 的
设计说明书

Anthropic 的 frontend-design skill 不教你怎么写网页,它教你怎么不做出「AI 味儿」。下面拆开它的骨架、它的迭代方法,以及那套紧凑到能背下来的设计 token 系统。

源文件:SKILL.md · 1,516 词 许可:Apache 2.0 零脚本 · 零资源

正文里的上标是出处编号,对应第 09 节;※ 表示本站的判断或本站构造的示例,没有外部出处。

01

先说清楚它是什么

它不是一个工具,是一份写给模型看的作业规范。整个目录只有两个文件,正文全是自然语言,没有任何可执行代码。119

项值
仓库anthropics/skills · 官方 Agent Skills 示例库11
目录内容SKILL.md(9.4 KB)+ LICENSE.txt11
加载方式frontmatter 的 description 命中「新建或重塑 UI」时,正文才被读进上下文1
约束力来源全靠模型自觉——没有 lint,没有无障碍检测,没有性能预算※

所以读它的正确姿势不是「照着执行」,而是拿它的判断标准回头检查自己。※

02

骨架:三层渐进披露

官方文档把这条当成唯一的核心设计原则:skill 不是一段长提示词,是一个按需加载的目录。17

层级内容何时进上下文成本
L1name + description启动时全部预载约 100 tokens / skill1
L2SKILL.md 正文命中触发时才读< 5k tokens(< 500 行)2
L3+references/ scripts/ assets/模型自己决定读或跑不读就是 01

关键在第三条:脚本是「跑」的,不是「读」的。一个 validate.py 的源码永远不进上下文,只有它的输出进来。这就是官方敢说「打包内容实际上没有上限」的原因。17

03

它是怎么写出来的:Claude A / Claude B

这是整套文档里最像工程的部分,也是这类 skill 的质量来源。四步循环4:

  1. 先不带 skill 干一遍活,记下模型在哪卡住、你反复交代了什么。
  2. 让 Claude A 把这些沉淀成 skill 草稿(官方原话:模型原生就会这个格式,不需要专门的元提示词)。4
  3. 让 Claude B(干净上下文 + 加载 skill)跑两三个真实任务。
  4. 观察 B 的行为,把发现带回给 Claude A 改,再跑。4

观察什么(而不是看它说得对不对)4

  • 走了你没预料到的文件路径 → 你的结构不够直觉
  • 漏读某个引用 → 链接不够显眼
  • 反复读同一个文件 → 那段该搬进正文
  • 从来不读某个文件 → 它是废的

配套的是评测先行:跑无 skill 的基线 → 写三个场景 → 只写「刚好够通过」的说明 → 对比基线迭代。官方也承认:目前没有内置的评测运行器,得自己搭。4

04

一个很好用的框架:自由度分级

写指令前先判断任务有多「脆」。官方比喻是:一边悬崖的窄桥,还是没危险的旷野。3

高自由度

纯文字步骤

多条路都行、靠情境判断。给方向,别给清单。例:code review。

中自由度

伪代码 / 带参脚本

有偏好模式但允许变化。给模板,留参数。例:报表生成。

低自由度

一个确切命令

一步错全错。给护栏,写死参数,并明说「不许改」。例:数据迁移。3

05

几条反直觉的规矩

  • 默认模型已经够聪明。每段都问:这段值它的 token 吗?反例是花 150 词解释什么是 PDF。3
  • 别给太多选项。「pypdf 或 pdfplumber 或 PyMuPDF 或…」是坏例子;给一个默认 + 一个逃生口。5
  • 别放时效信息。「2025 年 8 月前用旧 API」会过期;改成折叠的「旧模式」区块。5
  • 术语必须前后一致。endpoint / URL / route / path 混着用,模型就得猜。5
  • 脚本要自己处理错误。官方叫 solve, don't defer——别把异常甩给模型;常量必须写理由,不许 TIMEOUT = 47。5
  • 讲「为什么」,少堆 MUST。写清缘由让模型自己泛化,别把规则焊死到具体例子上。8
  • description 要「pushy」。官方承认模型有「该用不用」的倾向,所以描述里要把用户的说法都列进去。8

这几条不用背——官方把它们收成了一份发布前的 checklist,逐项打勾即可。6

06

紧凑的 token 系统

这里的 token 是设计 token,跟语言模型的 token 没关系——就是给颜色、字体、字号起的命名变量。skill 的原话是 a compact token system with color, type, layout, and principles。9

关键词是 compact:它不是让你搭一套设计系统,而是一份写代码前能一口气背下来的契约。因为后面那句要求是「每个颜色和字体决策都必须从它推导出来」——一旦允许临时加个灰,契约就废了。9

  • 颜色只留 4–6 个(再多说明没想清谁是主角)
  • 字体只留 1–2 套(多一套就多一个打架的理由)
  • 布局用一句话 + 一个 ASCII 线框说清,不画完整稿
  • 每个值必须有角色名,不是 --gray-100 这种别人的调色盘9

反例正是 Tailwind 默认色板:200 个颜色不等于 token 系统,那是别人替你做的决定。※

对照台:同一张卡片,两套 token

下面这张卡片的 HTML 一个字都不变,只有 CSS 变量在换。这就是「紧凑」的意义——它是一份能整体替换的契约,而不是散落在样式表里的临时决定。※

DEMO · 同一组件 / 两套 token
潜龙 6000
6,000 m · 12 h · 4 推进器

深海作业型遥控潜器,双机械臂,可在 6000 米深度连续作业。

/* A · 深海 ROV */
ink      #06171C   深海黑绿,正文与背景的极端
paper    #E8EDE9   海水泡久的纸,唯一大面积浅色
depth-1  #0C2A33   分区底色(同色相,只压明度)
signal   #FF6A00   航标橙,全站只出现在可点元素上
radius  0         工业件没有软的边
/* B · 拼装玩具 */
chalk    #FFF9F2   接近白但偏暖,留给孩子照片当底
jelly    #FF5C8A   主色,只用在「可拼」的零件上
slime    #7BE0A8   次色,与 jelly 一对
ink      #2B1B3D   紫黑,不用纯黑(纯黑太硬)
radius  18        圆角各不相同,从不统一

字体差异这里用字重与字距模拟;真实项目会换成 Archivo Narrow / Baloo 2。

完整的 token 块长什么样

以 A 为例,十几行就能定死一个页面的视觉。注意每条后面那半句:用法规则也写进 token 里,否则 signal 迟早被拿去当装饰。9

Color
  ink      #06171C   深海黑绿,正文与背景的极端
  paper    #E8EDE9   海水泡久的纸,唯一大面积浅色
  depth-1  #0C2A33   分区底色(同色相,只压明度)
  depth-2  #123C47   第二层分区
  signal   #FF6A00   航标橙,全站只出现在 3 个可点元素上

Type
  display  Archivo Narrow 600/700   标题,字距 -0.02em
  body     Inter 400/500            正文 16/1.65,行长 ≤68ch
  data     JetBrains Mono 400       只有深度、压力、时长这些读数用

Layout
  左对齐单栏 720px 居中,参数读数以侧注挂在右边缘;
  页面自上而下背景逐段变暗,像一次下潜。

Principles
  唯一的橙只标记「可以动的东西」;明度递减代替分割线;
  所有圆角 = 0(工业件没有软的边)。

落成 CSS 就是一一对应,这样「临时加个灰」变成了显式违规※:

:root{
  --ink:     #06171C;
  --paper:   #E8EDE9;
  --depth-1: #0C2A33;
  --signal:  #FF6A00;  /* 仅限可交互元素,全站 ≤3 处 */

  --font-display: "Archivo Narrow", sans-serif;
  --font-body:    "Inter", sans-serif;

  --measure: 68ch;
  --radius:  0;
}

唯一的验收标准

skill 要求拿这套 token 回头问一句:换个同行业的客户,它还能直接用吗?9

如果写成「#F4F1EA 米白 + 高对比衬线 + #D97757 陶土」,答案是「能」——任何工业客户都能套。那它就是默认值,不是设计。紧凑 token 系统的价值在于:它的数值本身就是论据。※

07

破绽清单:五类 AI 味儿

这是整份文件里最好用的部分。它不列正面原则,而是列出「一眼看出是生成的」的聚类特征。发页面前过一遍,勾中几条心里有数。9

命中 0 / 5 · 暂时干净

注意态度:这五类都合法,只是「默认值而非选择」。简报自己指定了方向就照做;没指定的轴,别浪费在这些默认值上。9

08

五个标本

下面是五张真实渲染的迷你页面,每张只做自己那一类默认值。它们不是「错误示例」——每一个都能交付,只是换个客户还能照样用。当参照物用:做完自己的页面,和它们比一比。※

AldergateWorkAboutJournalEnquire
Interiors made slowly,
for rooms that last
A small studio in Copenhagen working on houses, not projects.
Start a conversation
12,000Hours on site
38Houses built
9Years in practice
01 · 奶油底 + 高对比衬线 + 陶土色 #F4F1EA 底 · #1F1B16 字 · #D97757 点缀 · 衬线大标题 + 一个词换色斜体 为什么是破绽:这套配色不描述任何行业——律所、民宿、咖啡、建筑事务所都能套。而小标签 + 大数字的 stats 行是这个模板的标配填充物。9
●VoltageDocsPricingChangelog
Ship faster.
Break nothing.
Deploy previews for every branch, with instant rollback and zero config.
01 / EDGE

Runs in 34 regions, no cold starts, no config files.

02 / ROLLBACK

One command returns you to any previous build.

03 / INSIGHT

Trace every request from edge to origin.

02 · 近黑底 + 单一荧光色 #0B0B0B 底 · #C6FF3D 唯一 accent · 编号小卡 + 荧光绿圆点 为什么是破绽:开发者工具的默认制服。荧光色只用来「显得很未来」,和产品本身没有任何关系——换成任何一家 dev tool 都成立。9
The MeridianVOL. IV · NO. 12 · SATURDAY EDITION
WEATHER · 14°CMARKETS · CLOSEDEST. 1897

A quiet harbour town learns to live with water

The tide comes in twice a day and takes a little more each time. Residents have stopped rebuilding the sea wall and started rebuilding their habits instead.

What began as a municipal problem is now a shared calendar: who moves what, and when.

Notes from the archive, forty years on

Boxes recovered from the old press building turned out to hold the complete set of printing plates, still legible after four decades.

The paper has begun a slow restoration, one plate at a time, in the order they were first used.

Opinion: the case for slower reporting

Deadlines are not the enemy. The enemy is publishing before anyone has checked the second source.

We have made that mistake, and we have printed the correction on the same page.

03 · 报纸风 #FFF 底 · 3px 双线刊头 · 全页发丝线 · 三栏密排 · 零圆角 为什么是破绽:看起来最「有品味」,其实是最省事的一种——不需要任何图像或色彩决策,用线把内容切开就行了。它适合真正的出版物,不适合一个 SaaS 落地页。9
NimbusNEW · v2.4
Everything your team needs,
in one calm place
Plan, write, and ship — without the tab sprawl.
◈
Unified workspace

Docs, tasks and decisions live next to the work they describe.

◇
Smart summaries

Every thread ends with the decision and who owns it.

◆
Quiet notifications

Only what changed since you last looked.

04 · SaaS 卡片套件 #F8FAFC 底 · 16px 统一圆角 · 0 4px 12px rgba(0,0,0,.1) · 紫蓝渐变洗色 · 三张等大卡 为什么是破绽:三张卡片的形状、阴影、内边距、图标尺寸完全一致,因为它们本来就不是为内容设计的,是为了「凑一屏」。9
Product — Infrastructure
The control plane
for everything you run
Compute · Storage · Edge · Observability
Compute — Elastic
Scale without thinking

Capacity follows traffic, not your calendar.

Edge — Global
34 regions, one config

Same deploy, same behaviour, everywhere.

Read the docs →
05 · 模板配件 #0B0B0B 假黑 · 全大写宽字距引题 · A · B · C 中点串 · WORD — fragment · 小数据等宽 · 按钮挂 → 为什么是破绽:最隐蔽的一类——每一件单看都合理,但五件同时出现在每个标题上,就是「按模板填空」的痕迹。注意那个中点串,它通常没有任何信息量。9

五个标本放在一起看,共同点不是「丑」——它们都还体面。共同点是可替换性:把文案换成另一个客户,页面一个字都不用改。这就是 06 节那个验收标准要拦的东西。※

09

出处

下面每一条都能落到具体章节,编号与正文上标一致。注意 docs.claude.com 已 301 跳转到 platform.claude.com。

#支撑的内容出处
1三层披露、各层 token 成本、脚本只把输出送进上下文Agent Skills 概览 · How Skills work
2name/description 限制、500 行、引用一层深、长文件加目录Authoring best practices · Skill structure
3自由度分级、窄桥与旷野的比喻同上 · Set appropriate degrees of freedom
4评测先行、Claude A/B 循环、观察模型怎么用文件同上 · Evaluation and iteration
5别给太多选项、别放时效信息、术语一致、solve don't punt、常量要写理由同上 · Anti-patterns to avoid、Solve, don't punt
6发布前 checklist(本文最后一段提炼的即此)同上 · Checklist for effective Skills
7「新员工入职手册」、渐进披露是核心原则、打包内容无上限工程博客(2025-12-18)
8description 要 pushy、讲「为什么」少堆 MUST、主观输出可免测试用例skills/skill-creator/SKILL.md
9紧凑 token 系统、hero/字体/动效原则、五类 AI 味儿、验收标准skills/frontend-design/SKILL.md
10「avoid generic design defaults」这次改动本身commit 41bbe19d
11目录只有 SKILL.md 与 LICENSE.txt、skill 的开放标准skills/frontend-design/、agentskills.io
10

哪些是事实,哪些是推断

事实部分:三层结构、字段限制、自由度分级、A/B 循环、评测先行、五类破绽清单,全部原文可查(编号见 09 节)。

推断部分:这份 skill 具体是怎么被改出来的,官方从没公布制作过程。依据只有两条可查的硬证据——提交历史只有三次实质改动(最近一次 41bbe19d,+36/−20,标题就叫「avoid generic design defaults」),以及正文里那些只有观察过大量真实输出才写得出的具体度。这是合理推断,不是官方说法。10

另外修正一处常见误传:「主观输出的 skill 不需要测试用例」这句的准确出处是 skill-creator 的建议,不是官方 docs 的规则。8

11

附录:SKILL.md 全文

下面是 skills/frontend-design/SKILL.md 的完整原文——71 行、1,516 词、9,390 字节(即 9.4 KB),一字未删,frontmatter 也保留。同页附一份中文翻译,可切换对照。前面所有解读都能在这里逐句核对。9

中文为本站翻译,非官方;有歧义以英文为准
frontend-design / SKILL.md · EN1,516 words · 9.4 KB · 71 lines
---
name: frontend-design
description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
license: Complete terms in LICENSE.txt
---

Frontend Design

Approach this as the design lead at a design studio known for giving every client a distinct visual identity that is not mistaken for anyone else's. This client has already rejected proposals that felt cliché or templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take aesthetic risk if justified.

Ground your designs in the subject matter

If the brief does not identify what the product or subject matter is, identify it yourself before designing, and confirm with the client. You can come up with one concrete subject, the design's audience, and the design's primary job, as a proposal. If there's any information in your memory about the client's preferences or context about what they're building, use that as a hint. The subject's industry, subject matter, materials, and vernacular are where distinctive visual choices come from — a design for a toy for girls aged 8–11 will be very aesthetically different from a dashboard for financial analysts. Build with the brief's real content and subject matter throughout.

Design principles

For web designs, the hero is the first thing viewers will see. Open with the most characteristic thing in the subject's world, in the form that is most appropriate: a headline, an image, an animation, a live demo, an interactive moment, or other treatments. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the default treatment, so only use it if that's truly the best option.

Typography carries the personality of the page. You don't need a different typeface for display or headline text and body content: use one family or two, and if two, make them clearly distinct.

Choose your typefaces deliberately, not the default families you would reach for on any other project, and set a clear type scale following the default guidance of The Elements of Typographic Style with intentional weights, widths, and spacing. When type is used as a headline or visual element, use the type treatment itself as an active part of the design, not a neutral delivery vehicle for the content.

Default to line lengths of less than 80 characters. Serif typefaces can have slightly longer line lengths; give serif body text slightly more line-height than a sans-serif.

Avoid these default typographic treatments; they are the commonest tells of a generated page:

  • Accenting just a single word or phrase in a headline, like putting one word in italic/bold or a different color.
  • Using all caps for labels.
  • Adding unnecessary typographic labels above content.

Visual structure is information. Structural devices like outlines, borders, numbering, eyebrows, dividers, labels, etc., encode useful information about the content rather than decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence — like a stepped process or a timeline. Before adding numbered markers, check the content really is a sequence.

Use non-user-triggered motion sparingly and deliberately, only to draw attention. A single orchestrated moment — one page-load sequence or one reveal — lands better than scattered effects; fade-and-slide-up entrances on each section and hover transitions on every card are the generic default and read as AI-generated. Motion that answers a person's action (opening, expanding, confirming) is welcome when it shows what changed.

Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy and placeholder content. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.

Process: plan, review against the brief, build, critique

For calibration, AI-generated design right now clusters around some traits:

  1. a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta or warm-clay accent (often near #D97757 — Anthropic's own Claude-interaction accent, so on a user's brief it reads as a tell);
  2. a near-black background with a single bright acid-green or vermilion accent;
  3. a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns;
  4. the SaaS-card kit: content chopped into identical rounded cards, one border-radius on everything regardless of hierarchy, the same soft grey shadow (rgba(0,0,0,.1)) under each, and gradient washes as decoration;
  5. template chrome that appears whatever the subject: a tracked-out ALL-CAPS eyebrow label above every heading; meta strings joined with middle dots ('A · B · C'); labels built as 'WORD — fragment' with a spaced em dash; tinted near-black (#0B0B0B, #111) standing in for black; a monospace face for small data labels; a '→' appended to link and button text.

All traits are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. As with a hired human designer, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.

Work in two passes. First, brainstorm a short design plan based on the client's design brief: create a compact token system with color, type, layout, and principles.

  • Color: describe the core base palette as 4–6 named hex values.
  • Type: the typefaces and their roles.
  • Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Include alignment guidance; should the content be left aligned, center aligned, justified?
  • Principles: the high-level guidance for what makes this page unique.

Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan.

When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and an element-based selector like .cta). This can happen often with padding/margin between sections.

Restraint and self-critique

Spend your boldness in one place. Let one element be the memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected, visually accessible, harmonious color palettes. Critique your own work as you build, taking screenshots to review if your environment supports it — a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creatives have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.

More on writing in design

Words appear in a design for one reason: to make it easier to understand and use. They are design content, not decoration. Bring the same intentionality and minimalism to copywriting that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.

Write from the end user's perspective. Name things by what users will understand in simple language, not by how the system is built. A user manages notifications, not webhook config. Describe what something is or does in plain terms rather than selling it. Being specific and legible to new users is always better than being clever.

Use active voice as default. A CTA says exactly what happens when it is used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.

Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.

Keep the tone conversational: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each written element do exactly one job.

frontend-design / SKILL.md · 中文本站翻译 · 非官方
---
name: frontend-design
description: 在为新建 UI、或重塑现有界面做有辨识度、有意图的视觉设计时使用。帮助确定审美方向、字体排印,以及如何避免做出读起来像模板默认值的选择。
license: 完整条款见 LICENSE.txt
---

前端设计

以一间设计工作室的设计主管的身份来对待这件事——这间工作室以「给每个客户一套不会被误认成别人的独特视觉识别」著称。这个客户已经否掉了那些显得陈词滥调、像套模板的方案,他付钱买的是一个鲜明的观点:为这份简报在配色、字体排印和布局上做出刻意、有主张的选择;如果有理由,就承担审美上的风险。

让设计扎根于主题

如果简报没有说明产品是什么、主题是什么,在动手设计之前先自己定下来,并向客户确认。你可以提出一个具体的主题、这份设计面向谁、这份设计的主要任务,作为一份提案。如果你记忆里有关于客户偏好、或他们在做什么的上下文,把它当作线索。行业的属性、主题本身、材料与行话,才是独特视觉选择的来源——给 8–11 岁女孩做的玩具,和给金融分析师做的 dashboard,在审美上会非常不同。整个过程都要用简报里真实的内容和主题来构建。

设计原则

对网页设计来说,hero 是观者第一眼看到的东西。用主题世界里最有代表性的东西开场,形式挑最合适的:一句标题、一张图、一段动画、一个可运行的 demo、一个可交互的瞬间,或其他处理方式。这个选择要有意识:大数字配小标签、若干支撑数据、加一点渐变点缀,是默认做法,所以只有它确实最优时才用它。

字体排印承载页面的性格。你不需要给展示文字/标题和正文各配一套完全不同的字体:用一套或两套,如果用两套,就让它们的区别足够明显。

选字体要有意识,不要用你在任何别的项目上都会顺手拿起的默认字体族;按《The Elements of Typographic Style》的默认指引建立清晰的字体阶梯,并对字重、字宽和字距做有意的处理。当文字被当作标题或视觉元素使用时,让字体处理本身成为设计的主动部分,而不是内容的中性载体。

行宽默认控制在 80 字符以内。衬线字体可以稍长一些;衬线正文的行高要给得比无衬线略大。

避开下面这些默认的字体处理方式,它们是生成式页面最常见的破绽:

  • 只给标题里的一个词或短语做强调,比如把一个词改成斜体、粗体,或换个颜色。
  • 标签用全大写。
  • 在内容上方加多余的字体标签(eyebrow)。

视觉结构也是信息。轮廓、边框、编号、引题、分割线、标签这类结构性装置,应该是在编码关于内容的有用信息,而不是做装饰。很多通用设计会用编号标记(01 / 02 / 03),但只有当内容真的是一段序列时——比如分步流程或时间线——那才合适。在加编号标记之前,先确认内容真的是序列。

非用户触发的动效要克制、要有目的,只用来把注意力引过去。一个被精心编排的瞬间——一次载入序列,或一次揭示——比零散的效果更有力;每个区块都淡入上移、每张卡片都有 hover 过渡,是通用默认值,读起来就像 AI 生成的。回应人的动作的动效(打开、展开、确认)是受欢迎的,只要它展示了什么发生了变化。

认真对待文案。设计简报往往不含真实内容,得由你来想文案和占位内容。文案可以让一个设计显得和设计本身一样模板化。更多指引见下面关于写作的那一节。

流程:规划、对照简报审视、动手构建、自我批评

先做个校准:当下 AI 生成的设计会聚在几个特征上:

  1. 奶油色暖底(接近 #F4F1EA),配高对比的衬线大标题,加陶土色或暖泥色点缀(常在 #D97757 附近——那是 Anthropic 自家 Claude 的交互色,所以用在用户的简报上会读作破绽);
  2. 近黑底,配一个明亮的酸绿或朱红点缀;
  3. 大报式的布局:发丝线、零圆角、密排的报刊式分栏;
  4. SaaS 卡片套件:内容切成一张张一模一样的圆角卡,不分层级全用同一个圆角半径,每张卡下面都压着同一层柔灰阴影(rgba(0,0,0,.1)),再用渐变洗色做装饰;
  5. 不管什么主题都会出现的模板化配件:每个标题上方一条拉宽字距的全大写引题;用中点串起来的信息串('A · B · C');'WORD — fragment' 这种带空格破折号的标签;用带色调的近黑(#0B0B0B、#111)冒充纯黑;小号数据标签用等宽字体;链接和按钮文字尾巴上挂一个 '→'。

这些特征在某些简报下都是合理的,但它们是默认值而不是选择,而且不管主题是什么都会出现。当简报已经把视觉方向钉死,就严格照做——简报自己的措辞永远优先,包括它要求就要其中某一种风格的时候。当它把某条轴留空,别把这份自由花在这些默认值上。就像请一位真人设计师一样,「做自己擅长的事」和「把每个项目当成一次实验与学习的机会」之间,通常有个需要拿捏的平衡。

分两遍做。第一遍,基于客户的设计简报头脑风暴出一份简短的设计方案:建立一套紧凑的 token 系统,包含颜色、字体、布局和原则。

  • 颜色:把核心基础配色描述为 4–6 个命名的十六进制值。
  • 字体:用哪些字体族,各自承担什么角色。
  • 布局:一个布局概念,用一句话的散文描述和 ASCII 线框来推演、比较。要包含对齐指引:内容应该左对齐、居中,还是两端对齐?
  • 原则:让这个页面独一无二的高层指引。

然后在动手之前,拿这份方案对照简报再审一遍:如果其中有任何一部分读起来像你会为任何相似页面产出的通用默认值(走一遍相似的提示词,看自己是不是会落到同一个地方),而不是为这份特定简报做的选择——就把那部分改掉,说明你改了什么、为什么改。只有在确认你的设计方案具有相对独特性之后,才开始写代码,并按修订后的方案执行。

写代码时,注意组织好 CSS 选择器的优先级。很容易写出互相抵消的 CSS 类(尤其是像 .section 这种基于类型的选择器和像 .cta 这种基于元素的选择器混用)。在区块之间的 padding/margin 上,这个问题尤其常见。

克制与自我批评

把大胆用在一个地方。让一个元素成为值得记住的东西,把周围的一切保持安静、有纪律,并砍掉任何不为简报服务的装饰。在不声张的前提下达到质量底线:能响应到手机、键盘焦点可见、尊重 reduced motion、视觉上可访问、配色和谐。边写边批评自己的作品,如果环境支持就截图来审视——一张图胜过 1000 个 token。想想 Chanel 的建议:出门前照照镜子,摘掉一件配饰。人类创作者有记忆,也总想做点新的,所以如果你有地方能随手记下试过什么,这对之后的几轮会有帮助。

再谈设计中的写作

文字出现在设计里只有一个理由:让人更容易理解和使用。它们是设计内容,不是装饰。把你在间距和颜色上投入的那份用心与极简,同样投入到文案上。动笔之前先问:这个设计需要说什么,怎么才能最好地说出来、帮人把这段体验走通。

从终端用户的视角写。用用户能听懂的简单语言给东西命名,而不是按系统是怎么建的来命名。用户管理的是通知,不是 webhook 配置。平实地描述某个东西是什么、做什么,而不是推销它。具体、对新用户可读,永远比机灵更好。

默认用主动语态。CTA 要准确说出用了会发生什么:「保存更改」,而不是「提交」。一个动作在整个流程里保持同一个名字,所以写着「发布」的按钮,产出的 toast 就该写「已发布」。界面的词汇是给人在产品里导航的路标。内聚与一致,是人学着认路的方式。

把失败和空白当作给出方向的机会,而不是抒发情绪的地方。解释出了什么问题、怎么修,用界面的口吻而不是某个人的口吻。错误不道歉,也从不含糊其辞地说发生了什么。空屏是邀请人去行动。

语气保持口语化:朴素的动词、句首大写、不加废话,语气与品牌和受众匹配。让每个文字元素只做一件事。

展开未渲染的 Markdown 原文(英文)
---
name: frontend-design
description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
license: Complete terms in LICENSE.txt
---

# Frontend Design

Approach this as the design lead at a design studio known for giving every client a distinct visual identity that is not mistaken for anyone else's. This client has already rejected proposals that felt cliché or templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take aesthetic risk if justified.

## Ground your designs in the subject matter

If the brief does not identify what the product or subject matter is, identify it yourself before designing, and confirm with the client. You can come up with one concrete subject, the design's audience, and the design's primary job, as a proposal. If there's any information in your memory about the client's preferences or context about what they're building, use that as a hint. The subject's industry, subject matter, materials, and vernacular are where distinctive visual choices come from — a design for a toy for girls aged 8–11 will be very aesthetically different from a dashboard for financial analysts. Build with the brief's real content and subject matter throughout.

## Design principles

For web designs, the hero is the first thing viewers will see. Open with the most characteristic thing in the subject's world, in the form that is most appropriate: a headline, an image, an animation, a live demo, an interactive moment, or other treatments. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the default treatment, so only use it if that's truly the best option.

Typography carries the personality of the page. You don't need a different typeface for display or headline text and body content: use one family or two, and if two, make them clearly distinct.

Choose your typefaces deliberately, not the default families you would reach for on any other project, and set a clear type scale following the default guidance of The Elements of Typographic Style with intentional weights, widths, and spacing. When type is used as a headline or visual element, use the type treatment itself as an active part of the design, not a neutral delivery vehicle for the content.

Default to line lengths of less than 80 characters. Serif typefaces can have slightly longer line lengths; give serif body text slightly more line-height than a sans-serif.

Avoid these default typographic treatments; they are the commonest tells of a generated page:
- Accenting just a single word or phrase in a headline, like putting one word in italic/bold or a different color.
- Using all caps for labels.
- Adding unnecessary typographic labels above content.

Visual structure is information. Structural devices like outlines, borders, numbering, eyebrows, dividers, labels, etc., encode useful information about the content rather than decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence — like a stepped process or a timeline. Before adding numbered markers, check the content really is a sequence.

Use non-user-triggered motion sparingly and deliberately, only to draw attention. A single orchestrated moment — one page-load sequence or one reveal — lands better than scattered effects; fade-and-slide-up entrances on each section and hover transitions on every card are the generic default and read as AI-generated. Motion that answers a person's action (opening, expanding, confirming) is welcome when it shows what changed.

Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy and placeholder content. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.

## Process: plan, review against the brief, build, critique

For calibration, AI-generated design right now clusters around some traits:
1. a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta or warm-clay accent (often near #D97757 — Anthropic's own Claude-interaction accent, so on a user's brief it reads as a tell);
2. a near-black background with a single bright acid-green or vermilion accent;
3. a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns;
4. the SaaS-card kit: content chopped into identical rounded cards, one border-radius on everything regardless of hierarchy, the same soft grey shadow (rgba(0,0,0,.1)) under each, and gradient washes as decoration;
5. template chrome that appears whatever the subject: a tracked-out ALL-CAPS eyebrow label above every heading; meta strings joined with middle dots ('A · B · C'); labels built as 'WORD — fragment' with a spaced em dash; tinted near-black (#0B0B0B, #111) standing in for black; a monospace face for small data labels; a '→' appended to link and button text.

All traits are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. As with a hired human designer, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.

Work in two passes. First, brainstorm a short design plan based on the client's design brief: create a compact token system with color, type, layout, and principles.
- Color: describe the core base palette as 4–6 named hex values.
- Type: the typefaces and their roles.
- Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Include alignment guidance; should the content be left aligned, center aligned, justified?
- Principles: the high-level guidance for what makes this page unique.

Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan.

When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and an element-based selector like .cta). This can happen often with padding/margin between sections.

## Restraint and self-critique

Spend your boldness in one place. Let one element be the memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected, visually accessible, harmonious color palettes. Critique your own work as you build, taking screenshots to review if your environment supports it — a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creatives have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.

## More on writing in design

Words appear in a design for one reason: to make it easier to understand and use. They are design content, not decoration. Bring the same intentionality and minimalism to copywriting that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.

Write from the end user's perspective. Name things by what users will understand in simple language, not by how the system is built. A user manages notifications, not webhook config. Describe what something is or does in plain terms rather than selling it. Being specific and legible to new users is always better than being clever.

Use active voice as default. A CTA says exactly what happens when it is used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.

Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.

Keep the tone conversational: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each written element do exactly one job.

这份文件本身就是全部交付物:没有脚本、没有资源、没有 evals。它的质量只能从文字里看出来——所以把原文摆在这里,而不是替你总结。