Baseline Design

RSS: https://newsletter.baselinedesign.com/rss/
Thoughts on design systems, craft, and the people behind the work.

不读代码而读 JSON

JSON 读起来像代码，但设计师不需要会写代码，只需要能读懂它的结构：大括号表示对象，方括号表示列表，冒号连接名称和值。 这套阅读方式直接对应设计系统里三类文件：设计令牌文件、API 响应和代码评审里的数据。 读懂它们后，设计师可以把抽象的"数据可能很长"变成具体的判断，比如显示名没有固定长度，组件要决定如何截断或换行；bio 为空时卡片必须容纳无简介状态。 设计令牌分两层。基础令牌（如 blue/500）存一个具体值，语义令牌（如 background/brand）不存值，而是指向基础令牌。改变基础值会影响所有引用它的语义令牌；只改语义令牌的引用，则只影响那一个决定。 读令牌 diff 时，设计师能看出一次小改动实际波及的范围是否超出预期。 2025 年底，Design Tokens Community Group 发布了首个稳定格式规范：每个令牌带 $value 和 $type，引用仍用大括号。 类型被显式写出，工具不必再猜值是颜色、尺寸还是时长。该规范要求颜色用色彩空间和原始分量描述，hex 仅作回退。同一份清晰的数据也喂给机器和 AI 工具；一个组件可以写成"它是什么、接受什么参数、怎么用"的纯数据契约，例如 disabled 只用于不可交互状态、不能代替 loading。 规范目标是让人和工具读同一份文件。
评论点赞收藏30 天前

延伸范围与配方

MCP 和 Skills 是当前 AI 工具中两个常被混淆的机制。MCP（Model Context Protocol）让 AI 直接连接外部软件，解决每个工具各自写定制连接器的碎片问题； Skills 让 AI 按既定流程执行任务，省去在每次提示中重复说明团队规范。 MCP 解决访问层问题。接入前，想让 AI 读取 Figma 文件需逐个构建连接器，实际操作退化为截图粘贴加文字描述。 MCP 以开放标准建立统一接口，后台进程向 AI 列出可访问的资源，AI 提出查询，服务器处理权限并返回数据。 作者实测：连接 Figma MCP 后询问某按钮组哪些图层仍用原始十六进制色值而非变量，AI 数秒内返回 14 处，并指出都位于悬停和禁用状态。 Skills 解决执行层问题。团队文档格式、组件命名规则等约束过去要写进长提示词或项目指令。 Skills 把这些规则写成文件，顶部描述匹配任务时自动载入，让 AI 按同一套标准输出。 作者以设计系统为例：团队有固定六段式组件文档结构，接入 Skill 后 AI 生成文档时直接套用，无需逐条纠正。 两者互补：Skill 可指示 AI 何时调用哪个 MCP 工具。比如审计组件时用 Figma MCP 拉取变体属性，再对照弃用清单校验。作者给出筛选规则：第三次发现自己在向 AI 重复同一偏好时，就该把它写成 Skill。
评论点赞收藏48 天前

命名中间层

设计系统中最常见的命名问题不是 token 太多或太少，而是语义层没有对准设计师做决策时用的词汇。作者把 token 分三层：原始值描述数值（Blue/500），语义层描述角色（Surface/Interactive），组件级 token 描述特定组件的所有权（Button/Background/Hover）。 语义层只在前两层不够用时才需要第三层。 两种常见失败模式：语义 token 膨胀到 150–300 个，每个状态都有独立名称，设计师在变量面板里找不到合适项就直接抓一个原始值，漂移开始；或者只保留 20–30 个语义 token，一旦组件需要区别于默认值，组件级 token 就迅速膨胀到 400 个，承担了本应由语义层承载的含义。 作者给出的原则是：语义名称应描述决策（"这是一个用于分组内容的高亮表面"→ Surface/Elevated），而不是元素标签（"卡片"）。元素下季度改名，决策不变，token 仍适用。 组件级 token 是"泄压阀"，只在组件真正偏离语义层时使用；找不到合适语义名就加组件级 token，说明语义层缺了或命名错了。 当 AI 代理开始读取设计系统元数据时，描述性文字从可选项变成必要项。 Text/Primary 单独对代理来说信息不足，但加一句"浅色背景上的默认正文颜色，不用于链接、交互文本或强调状态"，人和代理都能正确选用。
评论点赞收藏56 天前

Room to Be Loud

👋 A quick note before we get into this week’s post: You’ll notice a few new faces start popping up as authors on our newsletters — including me! I'm Murphy, and I'm the Director of Design Systems her...
评论点赞收藏70 天前

Between the Lines: July 2026

It's been a busy stretch since Config: new client conversations, a new project kicking off with two more starting in the coming weeks, and a course going into production. Here's a look at what we've b...
评论点赞收藏78 天前

The Project We Walked Away From

There's a project the team and I still think about often, one that never moved forward at all. It's stuck with me for what it taught us about the questions we ask before the work ever begins. A little...
评论点赞收藏84 天前

The Guess Dressed Up As A Plan

Every proposal has a line you're not sure about yet. Maybe it's how many components a mobile app needs before anyone's designed it. Maybe it's whether the client's team can carry the system forward on...
评论点赞收藏91 天前

Naming Is The Argument

You can't get very far into a design system before you're talking about naming. Not the clever kind, but the everyday kind: what we call the components in a new system, the tokens, the layers undernea...
评论点赞收藏98 天前

Config 2026: Everything New in Figma

I just got back from 2026’s Figma Config, held in San Francisco, and I’m still sorting through everything I saw and heard while I was there. But after some rest and getting over the annual Config Cold...
评论点赞收藏105 天前

Between the Lines: June 2026

It's been a busy June: we announced a partnership, kicked off new engagements, held several Figma workshops, and are now heading into Config. Here’s a look at what we’ve been working on and thinking a...
评论点赞收藏114 天前

What Being Ready Actually Means

The question we hear most often right now is some version of: are we ready for this? And the honest answer is almost never about how clean the system is. Most design system teams are carrying a lot. T...
评论点赞收藏119 天前

Governance Without Gatekeeping

Governance is one of those topics I find myself coming back to on almost every engagement. Not because teams ask about it directly, but because the effects of getting it wrong show up everywhere else:...
评论点赞收藏125 天前

Six Months Later

I’ve been thinking a lot lately about what happens after we wrap up an engagement. Not the final presentation or the handoff, but six months later, when the team is on their own. I've been in consulti...
评论点赞收藏133 天前

Between the Lines: May 2026

This is the first edition of Between the Lines, our monthly series from inside the practice. Expect a mix of what we've been building, what's been on our minds, and a few things we think are worth you...
评论点赞收藏140 天前

What the System Is Trying to Tell You

Every design system audit starts the same way. You open the file expecting to spend an hour taking notes, and two hours later you're still pulling on threads, finding components that reference tokens ...
评论点赞收藏147 天前

登录芦苇

登录后关注作者、收藏内容和参与讨论。

热门话题

人工智能12,865 人关注AI 会怎样改变日常工作？产品思考8,243 人关注怎样判断一个产品值得长期做？独立开发5,917 人关注一个人如何持续完成作品？
关于芦苇 · 联系我们 · © 2026 芦苇