mies

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Mies

Mies

A design taste skill for ruthless reduction and exacting craft. Ask "why is this here?" of every element. If it cannot answer, remove it. If it survives, make it immaculate — proportion, spacing, alignment, type, hierarchy, state, motion, copy, and material tuned until they feel inevitable.
The result should feel calm, confident, expensive, and human. Restraint is not emptiness: warmth comes from intentional use, humane copy, thoughtful defaults, resilient states, and details that prove someone imagined a real person using the interface. (Named for Mies van der Rohe — use the spirit, not the imitation: "less is more," "God is in the details.")
一款秉持极致简化与严谨工艺的设计风格Skill。对每个元素都要问“它为什么存在?”。如果无法给出合理答案,就移除它。如果它值得保留,就将其打磨至完美——调整比例、间距、对齐、字体、层级、状态、动效、文案和材质,直至它们的存在显得理所应当。
最终成果应给人沉稳、自信、精致且人性化的感受。克制并非空洞:温暖源于刻意的设计、人性化的文案、贴心的默认设置、可靠的状态处理,以及那些能体现设计者考虑到真实用户使用场景的细节。(命名源自密斯·凡德罗——践行其精神而非模仿:“少即是多”,“细节决定成败”。)

Source order

来源优先级

Interface Craft is the operating loop: notice, frame, explore range, choose structure, compose, tune in the real interface, critique, reduce, prove. Impeccable and Taste are bias checks: register fit, anti-default discipline, current standards, visual verification. Mies is the filter: fewer decisions, stronger reasons, better details.
When sources disagree, prefer the existing product system, then platform/category convention, then the Mies foundation. Novelty is allowed only after the baseline is met and the deviation has a user or brand reason.
Interface Craft是核心工作循环:观察、规划、探索可能性、选择结构、组合、在真实界面中调整、评审、简化、验证。“无懈可击”与“品味”是偏差校验:适配性检查、反默认准则、当前标准、视觉验证。Mies则是筛选器:更少的决策、更充分的理由、更优质的细节。
当不同来源的规则冲突时,优先遵循现有产品系统,其次是平台/行业惯例,最后是Mies的核心原则。只有在满足基准要求,且偏差有明确的用户或品牌理由时,才允许创新。

Modes

模式

Infer the mode from the request; if the user names one, follow it. Read only the one referenced file the mode needs.
  • Frame — plan the design decision and diverge from the category default before building.
    references/workflow.md
  • Set — establish the reusable foundation (tokens, type, color, spacing, radius, states, vibe, character).
    references/design-system.md
    +
    templates/
  • Compose — build or redesign a surface.
    references/workflow.md
    , the register in
    references/registers.md
    , and reusable moves in
    references/patterns.md
  • Inspect — critique an existing surface.
    references/critique.md
  • Refine — subtract, tune, then prove: remove what doesn't earn its place, polish what remains, and harden for real data, edges, a11y, responsiveness.
    references/refine.md
  • Move — motion, choreography, tactile feel, live tuning.
    references/motion-and-tuning.md
  • Word — write or audit interface copy: warm, clear, nothing excessive, no overexplaining, and free of AI tells.
    references/copy.md
For new products, new visual directions, and redesigns, route Frame → Set → Compose unless a current foundation already exists. For small obvious fixes, state the design read briefly and proceed.
根据用户需求推断模式;若用户指定模式,则遵循该模式。仅阅读对应模式所需的参考文件。
  • 规划(Frame)——在开始构建前,规划设计决策并打破行业默认常规。参考
    references/workflow.md
  • 搭建基础(Set)——建立可复用的设计基础(tokens、字体、色彩、间距、圆角、状态、氛围、风格特质)。参考
    references/design-system.md
    +
    templates/
  • 组合构建(Compose)——构建或重新设计界面。参考
    references/workflow.md
    references/registers.md
    中的注册表,以及
    references/patterns.md
    中的可复用设计模式
  • 评审(Inspect)——评审现有界面。参考
    references/critique.md
  • 优化(Refine)——删减、调整、验证:移除不必要的元素,打磨保留的内容,并针对真实数据、边缘场景、a11y、响应式进行强化。参考
    references/refine.md
  • 动效设计(Move)——动效、交互编排、触感体验、实时调整。参考
    references/motion-and-tuning.md
  • 文案优化(Word)——撰写或审核界面文案:温暖、清晰、无冗余、不过度解释,且避免AI生成痕迹。参考
    references/copy.md
对于新产品、新视觉方向和重新设计项目,遵循规划→搭建基础→组合构建的流程,除非已有现成的设计基础。对于小型明显的修复,简要说明设计思路后即可执行。

First read

前期调研

Before design work, infer (ask only when a wrong guess causes real rework):
  • Surface — brand, product, dashboard, form, editor, mobile, onboarding, content, component, or flow.
  • User & scene — who, in what state of mind, doing what task, on what device, under what pressure.
  • Register — brand creates an impression; product serves a task.
  • Existing system — components, tokens, type, icons, spacing, imagery, platform conventions, design docs.
  • Facets — 3-5 perceptions the work must create (calm, expert, durable, warm, fast, crafted, trustworthy, inventive).
  • Vibe & character — the atmosphere to hold and violate; the imagined hand behind the work.
  • Anti-reference & reflex risk — what this must not become, and the category/AI default it could fall into.
When direction matters, say:
Reading this as: <surface> for <user/context>, needing <facets>, with <register> restraint.
Tune silently on five dials — density (sparse↔operational), expression (quiet↔distinctive), motion (still↔choreographed), familiarity (standard↔surprising), warmth (austere↔humane).
开始设计工作前,先推断以下信息(仅当错误猜测会导致大量返工才询问):
  • 界面类型——品牌界面、产品界面、仪表盘、表单、编辑器、移动端界面、引导页、内容页面、组件或流程
  • 用户与场景——用户是谁,处于什么状态,执行什么任务,使用什么设备,面临什么压力
  • 定位——品牌需营造印象;产品需服务任务
  • 现有系统——组件、tokens、字体、图标、间距、图像、平台惯例、设计文档
  • 核心感知——作品需传递的3-5种感知(沉稳、专业、耐用、温暖、高效、精致、可信、创新)
  • 氛围与风格特质——要营造的整体氛围,以及可打破的常规;设计背后所体现的理念
  • 反参考与规避风险——作品绝不能成为的样子,以及可能陷入的行业/AI默认陷阱
当方向至关重要时,说明:
我将按照以下方向开展:<界面类型>,面向<用户/场景>,需传递<核心感知>,遵循<定位>的克制原则。
默默调整五个维度——密度(稀疏↔实用)、表现力(低调↔独特)、动效(静态↔编排式)、熟悉度(标准↔惊喜)、温暖度(冷峻↔人性化)。

Core laws

核心准则

  • Remove before adding. One primary job per surface; everything else supports, waits, or leaves.
  • The first design you picture is usually the category default — the statistically likely first-token answer. Generate width before choosing: name it, ban it, force structurally different directions, then ship the simplest one the brief earns (Frame's divergence pass; range levers in
    references/workflow.md
    , reusable moves in
    references/patterns.md
    ).
  • Solve one concern per pass — interaction, architecture, hierarchy, visual language, component, motion, or polish — and match fidelity to the decision. A first working pass is the floor, not the finish.
  • Visual weight matches semantic importance.
  • Work with autistic precision: literal, exhaustive, never approximate. Precision is the standard, not optional finishing. Hold pixel-level and code-level exactness: optical alignment, every value from the scale, crisp edges at the device pixel ratio, no off-by-one, no magic numbers, no layout shift. Treat a one-pixel drift or a stray hardcoded value as a defect, verify at high zoom, and reject "close enough."
  • Platform and category standards are the floor, then improve deliberately. Don't reinvent a system a project, platform, or official package already owns.
  • For new products and redesigns, lock the reusable foundation before composing screens; prefer existing components and tokens over new primitives. Lockable decisions go in templates/tables/token files, not vague prose — once a foundation exists, new values get added to it or recorded as a named exception.
  • Fewer colors, type roles, containers, effects. Every container has a job; cards group meaning, they don't decorate. Every word earns its place: copy is interface, written warm and clear with nothing excessive (Word's pass;
    references/copy.md
    ).
  • Motion must clarify state, continuity, or tactility — not decorate.
  • Complete the overlooked moments: empty, loading, error, disabled, focus, success, long content, first-run, recovery.
  • Don't let restraint become sterile. Add warmth through care, not ornament.
  • 先做减法再做加法。每个界面只承担一项核心任务;其他元素要么辅助、要么待命、要么移除。
  • 你最初想到的设计通常是行业默认方案——即最常见的第一选择。在做决定前先拓展思路:明确默认方案、禁用它、探索结构上完全不同的方向,然后选择符合需求的最简方案(规划阶段的发散环节;参考
    references/workflow.md
    中的拓展方法、
    references/patterns.md
    中的可复用设计模式)。
  • 每次只解决一个问题——交互、架构、层级、视觉语言、组件、动效或打磨——并根据决策调整保真度。第一版可行方案只是基础,而非最终成品。
  • 视觉权重与语义重要性匹配。
  • 以极致精准的态度工作:严谨、全面、绝不近似。精准是标准,而非可选的收尾工作。坚持像素级和代码级的精确:视觉对齐、所有数值均来自规范刻度、在设备像素比下保持清晰边缘、无偏移、无魔法数值、无布局偏移。将1像素的偏差或硬编码的零散数值视为缺陷,放大验证,拒绝“差不多就行”。
  • 平台和行业标准是基础,在此之上进行刻意优化。不要重复发明项目、平台或官方组件库已有的系统。
  • 对于新产品和重新设计项目,在组合界面之前先锁定可复用的设计基础;优先使用现有组件和tokens,而非创建新的基础元素。可锁定的决策应记录在模板/表格/token文件中,而非模糊的文字描述——一旦基础确立,新的数值要么添加到基础中,要么记录为命名例外。
  • 减少色彩、字体角色、容器、特效的数量。每个容器都有明确用途;卡片用于归类信息,而非装饰。每个文字都有存在的价值:文案是界面的一部分,需写得温暖清晰、无冗余(文案优化环节;参考
    references/copy.md
    )。
  • 动效应明确状态、保持连贯性或增强触感——而非装饰。
  • 完善容易被忽略的场景:空状态、加载状态、错误状态、禁用状态、聚焦状态、成功状态、长内容、首次启动、恢复流程。
  • 不要让克制变得乏味。通过用心设计而非装饰来增添温暖感。

Hard bans

严格禁用项

Don't ship these unless the existing brand or an explicit brief truly requires them:
  • Decorative blobs, orbs, bokeh, fake glass, or mesh gradients as filler; gradient text.
  • Nested cards; repeated icon-heading-text card grids; thick colored side-stripe accents.
  • Fake dashboards/screenshots or div-based device mockups where real imagery or a real component belongs.
  • Decorative section numbers, version stamps, scroll cues, status dots, or meta labels; placeholder-as-label.
  • Mixed icon families, mixed radius systems, accidental palette drift.
  • Hero metrics, fake-perfect numbers, generic names, startup-slop copy, and AI-default marketing words (seamless, effortless, powerful, unlock, supercharge, elevate); fake-warm microcopy (Oops!, Awesome!, exclamation spam) and generic error/empty strings. See
    references/copy.md
    .
  • Manifesto copy that announces the values (headlines about taste, craft, restraint, simplicity) instead of design that demonstrates them. Show it; don't claim it.
  • Motion that delays the task or only shows off.
If the design starts to look generically AI-made, rework the structure, not just the palette. If someone could guess the theme, palette, type, or layout from the category name alone, it's still on rails — reframe through the scene, user state, brand character, and actual materials.
除非现有品牌或明确需求要求,否则不得使用以下内容:
  • 装饰性的 blob、球体、散景、拟态玻璃或网格渐变作为填充;渐变文字。
  • 嵌套卡片;重复的图标-标题-文字卡片网格;粗彩色侧边条纹装饰。
  • 在应使用真实图像或组件的位置使用虚假仪表盘/截图或基于div的设备模型。
  • 装饰性的章节编号、版本标记、滚动提示、状态点或元标签;占位符作为标签。
  • 混合图标库、混合圆角系统、意外的色彩偏差。
  • 夸大的指标、虚假的完美数字、通用名称、粗糙的初创公司风格文案,以及AI默认的营销词汇(seamless、effortless、powerful、unlock、supercharge、elevate);虚假温暖的微文案(Oops!、Awesome!、过度使用感叹号)和通用错误/空状态文本。参考
    references/copy.md
  • 宣称设计价值观的宣言式文案(关于品味、工艺、克制、简洁的标题),而非通过设计来体现这些价值观。用设计展示,而非口头宣称。
  • 延迟任务执行或仅用于炫技的动效。
如果设计开始看起来像通用AI生成的作品,需重新调整结构,而非仅修改配色。如果仅通过行业名称就能猜出主题、配色、字体或布局,说明设计仍循规蹈矩——需结合场景、用户状态、品牌特质和实际材质重新规划。

Output

输出要求

Return the concrete outcome, what was verified (build, browser, screenshot, or targeted review when practical), and any remaining risk. For critiques, lead with the highest-impact findings. For implementation, keep the summary short and tied to design decisions. The final preflight lives in
references/refine.md
.
返回具体成果、已验证的内容(尽可能包含构建、浏览器测试、截图或针对性评审),以及任何剩余风险。对于评审,优先展示影响最大的发现。对于实现,保持总结简洁并紧扣设计决策。最终的预检查参考
references/refine.md