The highest-leverage design work is choosing which constraints to impose — they determine what the system discovers on its own.
The Breakthrough
When building a topology visualization for a data analytics platform, the initial approach was hardcoding known relationships — manually listing which tables feed which functions. This was incomplete within days. The breakthrough was switching to constraint-based design: define parsing rules (regex patterns, parameter defaults) and let the system discover relationships automatically. It found 2-3x more connections than manual effort ever could.
This generalizes far beyond code. Designing good constraints — in systems, processes, organizations, or even personal workflows — is the meta-skill. A well-chosen constraint doesn’t limit; it channels energy toward emergent behavior you couldn’t have predicted or enumerated.
System Convergence in the AI Era
AI-Ghost-Lab’s “system convergence” concept is constraint design applied to AI-era development. His earlier mistake: relying on broad test coverage to contain AI-generated chaos. An AI agent might take three different paths from A to B, tripling the test burden. The fix: funnel similar functionality through unified entry points — control the core nodes, everything else can flex.
The specific constraints that work:
- Clear module boundaries
- Centralized state management
- Unified extension points
- Unified error handling
His metaphor captures it perfectly: “AI can make a mess, but only where you allow it — not in the living room.”
Constraining Agents, Not Railroading Them
Anthropic’s skill-writing advice embodies constraint design for AI agents. Two key principles:
- “Don’t state the obvious” — Don’t constrain what the model already does well. Focus constraints on where its defaults are wrong.
- “Avoid railroading” — Overly specific instructions limit adaptability.
The art is constraining where the model goes wrong while leaving freedom where it goes right. The frontend-design skill is a perfect example: it doesn’t teach CSS (Claude knows CSS). It specifically corrects Claude’s aesthetic defaults — the tendency toward Inter font and purple gradients. That surgical constraint produces better results than a wall of instructions ever could.
The Principle
The best designers — of systems, organizations, or AI workflows — don’t enumerate every behavior they want. They choose a small number of constraints that make the right behaviors emerge naturally. The meta-skill isn’t building; it’s knowing where to put the walls.
最高杠杆的设计工作是选择施加哪些约束——它们决定了系统自己能发现什么。
突破
在构建数据分析平台的拓扑可视化时，最初的方法是硬编码已知关系——手动列出哪些表喂哪些函数。这在几天内就过时了。突破在于切换到基于约束的设计：定义解析规则（正则模式、参数默认值），让系统自动发现关系。它发现的连接比手动方式多 2-3 倍。
这个原则超越了代码。在系统、流程、组织甚至个人工作流中设计好的约束，就是元技能。一个精选的约束不是限制——它将能量引导向你无法预测或穷举的涌现行为。
AI 时代的系统收敛
AI-Ghost-Lab 的”系统收敛”概念是约束设计在 AI 时代开发中的应用。他曾犯的错误：依靠广泛的测试覆盖来兜底 AI 产生的混乱。AI 从 A 到 B 可能走三条不同的路，测试负担成倍增长。正确做法：让相同功能走同一个入口——控制住核心节点，其余随意。
有效的具体约束手段：
- 明确模块边界
- 集中状态管理
- 统一扩展入口
- 统一错误处理
他的比喻很到位：”AI 可以拉屎，但必须在你指定的地方拉，不能在客厅拉。”
约束 Agent，而非束缚 Agent
Anthropic 的技能编写建议体现了面向 AI agent 的约束设计。两个关键原则：
- “不要说显而易见的” — 不要约束模型本来就做得好的地方。把约束集中在它默认行为有偏差的地方。
- “避免过度指令” — 过于具体的指令会限制适应性。
技巧在于：在模型出错的地方设置约束，在它做得好的地方留出自由。frontend-design 技能是个好例子：它不教 CSS（Claude 懂 CSS），而是专门纠正 Claude 的审美默认值——总是倾向 Inter 字体和紫色渐变。这种精准的约束比一堵墙的指令产生更好的效果。
原则
最好的设计师——无论是设计系统、组织还是 AI 工作流——不会穷举他们想要的每一种行为。他们选择少量约束，让正确的行为自然涌现。元技能不是建造，而是知道把墙放在哪里。