UI Hub 是一个每日更新的免费 UI 资源目录,给设计师、前端开发者和做界面的 AI Agent 用:共 2,395 条资源,其中 133 个组件库、1,929 个带明暗预览的组件样式示例,另有设计 skill 与 AI 设计技巧文章。UI Hub 是一個每日更新的免費 UI 資源目錄,給設計師、前端開發者和做介面的 AI Agent 用:共 2,395 條資源,其中 133 個元件庫、1,929 個附明暗預覽的元件樣式示例,另有設計 skill 與 AI 設計技巧文章。UI Hub is a free, daily-updated directory of UI resources for designers, front-end developers and AI agents that build interfaces: 2,395 resources, including 133 component libraries and 1,929 component style demos with light/dark previews, plus design skills and AI design articles.UI Hub は、デザイナー・フロントエンド開発者・UI を作る AI エージェント向けの、毎日更新される無料の UI リソース集です。全 2,395 件(コンポーネントライブラリ 133 件、ライト/ダーク対応のスタイルデモ 1,929 件)に加え、デザインスキルと AI デザイン記事を掲載しています。UI Hub는 디자이너, 프론트엔드 개발자, 인터페이스를 만드는 AI 에이전트를 위한 매일 업데이트되는 무료 UI 리소스 디렉터리입니다. 총 2,395개 리소스(컴포넌트 라이브러리 133개, 라이트/다크 미리보기가 있는 스타일 데모 1,929개)와 디자인 스킬, AI 디자인 글을 제공합니다.UI Hub ialah direktori sumber UI percuma yang dikemas kini setiap hari untuk pereka, pembangun front-end dan ejen AI yang membina antara muka: 2,395 sumber, termasuk 133 pustaka komponen dan 1,929 demo gaya komponen dengan pratonton terang/gelap, serta kemahiran reka bentuk dan artikel reka bentuk AI.UI Hub là danh mục tài nguyên UI miễn phí, cập nhật hằng ngày, dành cho nhà thiết kế, lập trình viên front-end và AI agent dựng giao diện: 2,395 tài nguyên, gồm 133 thư viện component và 1,929 mẫu phong cách component có xem trước sáng/tối, cùng skill thiết kế và bài viết về thiết kế với AI.UI Hub est un annuaire gratuit de ressources UI, mis à jour chaque jour, pour designers, développeurs front-end et agents IA qui construisent des interfaces : 2,395 ressources, dont 133 bibliothèques de composants et 1,929 démos de styles avec aperçus clair/sombre, plus des skills de design et des articles sur le design avec l’IA.UI Hub es un directorio gratuito de recursos de UI, actualizado a diario, para diseñadores, desarrolladores front-end y agentes de IA que construyen interfaces: 2,395 recursos, incluidas 133 bibliotecas de componentes y 1,929 demos de estilos con vista clara/oscura, además de skills de diseño y artículos de diseño con IA.UI Hub ist ein kostenloses, täglich aktualisiertes Verzeichnis von UI-Ressourcen für Designer, Frontend-Entwickler und KI-Agents, die Oberflächen bauen: 2,395 Ressourcen, darunter 133 Komponentenbibliotheken und 1,929 Komponenten-Stildemos mit Hell/Dunkel-Vorschau, dazu Design-Skills und Artikel zu KI-Design.

← 返回博客返回部落格Back to blogブログへ戻る블로그로Kembali ke blogVề blogRetour au blogVolver al blogZurück zum Blog · 设计手艺設計手藝Craftクラフト디자인 기본기KemahiranTay nghềSavoir-faireOficioHandwerk · 2026-10-14 · 8 分钟阅读8 分鐘閱讀6 min read6 分で読めます6 분 읽기6 min bacaan6 phút đọc6 min de lecture6 min de lectura6 Min. Lesezeit

让动效"对味":目的、时长、缓动与克制讓動效「對味」:目的、時長、緩動與克制Motion that feels right: purpose, duration, easing, restraintしっくりくるモーション:目的・時間・イージング・抑制자연스러운 모션: 목적, 시간, 이징, 절제Gerakan yang terasa betul: tujuan, tempoh, easing, kawalanChuyển động đúng cảm giác: mục đích, thời lượng, easing, tiết chếUn mouvement juste : intention, durée, easing, retenueMovimiento que se siente bien: propósito, duración, easing, contenciónBewegung, die sich richtig anfühlt: Zweck, Dauer, Easing, Zurückhaltung

大多数界面动效应在 300ms 内、用 ease-out,高频操作干脆不做。炫技属于营销页,不属于工具。大多數介面動效應在 300ms 內、用 ease-out,高頻操作乾脆不做。Most UI motion should be under 300ms, ease-out, and skipped for frequent actions. Spectacle belongs on marketing pages, not in tools.UIモーションは300ms以内・ease-out、頻繁な操作には付けない。UI 모션은 300ms 이하, ease-out, 잦은 동작엔 생략.Kebanyakan gerakan UI di bawah 300ms, ease-out, dan dilangkau untuk tindakan kerap.Hầu hết chuyển động dưới 300ms, ease-out, bỏ qua với thao tác thường xuyên.Moins de 300 ms, ease-out, et rien pour les actions fréquentes.Menos de 300 ms, ease-out, y nada en acciones frecuentes.Unter 300 ms, ease-out, und keine Animation für häufige Aktionen.

Motion that feels right: purpose, duration, easing, restraint

正文以簡體中文顯示。

本文は英語で表示しています。

본문은 영어로 표시됩니다.

Kandungan dipaparkan dalam bahasa Inggeris.

Nội dung hiển thị bằng tiếng Anh.

Le corps de l’article est en anglais.

El cuerpo del artículo está en inglés.

Der Beitragstext ist auf Englisch.

Emil Kowalski's rule of thumb is blunt: if a user triggers something a hundred times a day, do not animate it. Motion in an interface has three legitimate jobs: orientation (where did this come from and where did it go?), feedback (your action worked) and, sparingly, delight. Everything else is decoration that costs time on every interaction. This post gives starting numbers, a step-by-step way to add motion to a component, code you can paste, and the mistakes that make AI-generated pages feel cheap.

Three easing curves compared: linear, ease-in, ease-out
Three easing curves compared: linear, ease-in, ease-out · Diagram: original by UI Hub, CC BY 4.0

Decide the job before the animation

Before writing a transition, write one sentence: "This animates so the user understands ___." If you cannot fill the blank, leave it static. Some examples:

Emil Kowalski’s “Great Animations” article
Emil Kowalski’s “Great Animations” article · Screenshot: Emil Kowalski (emilkowal.ski), captured 2026-10-14. © the original site.

A command palette that opens 50 times a day should appear almost instantly. Keep frequent surfaces fast and spend motion on rare moments.

Numbers to start from

Step by step: a dropdown that feels right

Step 1: set the origin. Scale from the trigger, not from the centre. Radix and similar libraries expose the transform origin as a CSS variable you can use.

Step 2: write enter and exit separately. Exits should be faster than entries; the user has already decided to move on.

.menu {
  transform-origin: var(--radix-dropdown-menu-content-transform-origin, top left);
}
.menu[data-state="open"] {
  animation: menu-in 180ms cubic-bezier(0.16, 1, 0.3, 1);
}
.menu[data-state="closed"] {
  animation: menu-out 120ms ease-in;
}
@keyframes menu-in {
  from { opacity: 0; transform: scale(0.96) translateY(-4px); }
  to   { opacity: 1; transform: none; }
}
@keyframes menu-out {
  to { opacity: 0; transform: scale(0.98); }
}

Step 3: respect reduced motion. Some users get motion sickness from movement. Keep the opacity change, drop the movement:

@media (prefers-reduced-motion: reduce) {
  .menu[data-state="open"],
  .menu[data-state="closed"] {
    animation-name: fade;
  }
  @keyframes fade { from { opacity: 0; } to { opacity: 1; } }
}

Step 4: test at speed. Open and close it ten times quickly. If the animation ever blocks the next click, it is too long or not interruptible.

Springs and layout animation

For elements that move between positions (a reordered list item, an expanding card, a tab indicator), springs feel more natural than fixed curves because they respond to interruption. Motion (formerly Framer Motion) makes layout animation one prop:

import { motion } from "motion/react";

<motion.div
  layout
  transition={{ type: "spring", stiffness: 500, damping: 40 }}
  className="tab-indicator"
/>

Keep springs stiff and well damped for UI. A bouncy spring is fun once and annoying the twentieth time.

One hero moment per page

Aceternity- and Magic UI-style effects (beams, spotlights, meteor showers, marquees) are designed to impress. They work as one hero moment per page. Put a spotlight on the hero and a marquee on the logo strip and an animated gradient border on every card, and the page reads as a template. When an AI generator gives you three effects, keep the one closest to your story and make the rest static.

A quick motion audit

To review an existing page, list every animation in a table with four columns: element, trigger, duration and job. Anything without a job is deleted. Anything triggered often gets shortened to near-instant. Anything over 400ms needs a reason. Then record the screen at normal speed and watch it back at half speed: you will see easing problems, overlapping animations and elements that move in different directions at once, which are hard to notice live.

Pitfalls

Questions we get

CSS transitions or a JavaScript library? Use CSS for simple state changes (hover, open/close, fades): it is cheap and runs off the main thread for transform and opacity. Reach for a library like Motion when you need layout animation, shared-element transitions, gestures or interruptible springs.

How do I find janky animations? Open the browser's performance panel, record while triggering the animation, and look for long frames and layout or paint work on every frame. On a real mid-range phone, jank you cannot see on a laptop becomes obvious.

What about loading states? Skeletons with a subtle shimmer are fine, but the shimmer should be slow and low-contrast. Better still, show content as soon as it arrives instead of fading everything in together.

Should marketing pages follow the same rules? Mostly. Marketing pages can afford one bigger moment because they are visited rarely, but the same limits on duration, easing and reduced motion still apply to buttons, menus and navigation on those pages.

How do I brief an AI generator about motion? Give it the numbers: durations, the easing curve, "transform and opacity only", "one hero effect", and a reduced-motion requirement. Without numbers, generators default to slow, floaty transitions on everything.

Our take

Good motion is mostly invisible: users notice that the interface feels responsive, not that it animates. Start every component static, add motion only where you can name its job, keep it short and ease-out, and spend your one big effect where the story needs it. Josh Comeau's interactive guide to CSS transitions is the best explanation of why easing curves matter; read it once and you will see bad easing everywhere.

Josh Comeau’s interactive guide to CSS transitions
Josh Comeau’s interactive guide to CSS transitions · Screenshot: Josh W. Comeau (www.joshwcomeau.com), captured 2026-10-14. © the original site.

Checklist

AI 提示词AI 提示詞AI promptAIプロンプトAI 프롬프트Prompt AIPrompt cho AIPrompt IAPrompt de IAKI-Prompt

复制给 Claude、Cursor、v0 等 AI 助手,让它按本文的方法处理你的项目。尖括号里的内容换成你自己的。複製給 Claude、Cursor、v0 等 AI 助手,讓它按本文的方法處理你的專案。尖括號裡的內容換成你自己的。Paste this into Claude, Cursor, v0 or another assistant to apply this post to your own project. Replace the parts in angle brackets.Claude・Cursor・v0 などのAIアシスタントに貼り付けると、この記事の方法をあなたのプロジェクトに適用できます。山括弧の部分は自分の内容に置き換えてください。Claude, Cursor, v0 같은 AI 도우미에 붙여 넣으면 이 글의 방법을 내 프로젝트에 적용할 수 있습니다. 꺾쇠괄호 안은 내 내용으로 바꾸세요.Tampal ke Claude, Cursor, v0 atau pembantu lain untuk menggunakan kaedah artikel ini pada projek anda. Gantikan bahagian dalam kurungan sudut.Dán vào Claude, Cursor, v0 hoặc trợ lý khác để áp dụng bài này cho dự án của bạn. Thay phần trong dấu ngoặc nhọn bằng nội dung của bạn.Collez-le dans Claude, Cursor, v0 ou un autre assistant pour appliquer cet article à votre projet. Remplacez les parties entre chevrons.Pégalo en Claude, Cursor, v0 u otro asistente para aplicar este artículo a tu proyecto. Sustituye lo que está entre corchetes angulares.In Claude, Cursor, v0 oder einen anderen Assistenten einfügen, um diesen Beitrag auf dein Projekt anzuwenden. Teile in spitzen Klammern ersetzen.

走查并修正 <组件或页面> 里的动效。
对你找到的每个动画或过渡:
1. 说出它的用途:定位、反馈还是愉悦。没有用途,或者这个操作一天会发生很多次(切标签、折叠侧栏、命令面板),就删掉,或改成几乎瞬间(<100ms)。
2. 时长:小界面 150–250ms,大面 300–400ms;退出比进入快约 30%。
3. 缓动:进入和响应用 ease-out(如 cubic-bezier(0.16,1,0.3,1));响应绝不用 ease-in。
4. 只动 transform 和 opacity。替换掉 width/height/top/box-shadow 动画。
5. 加一段 prefers-reduced-motion,保留透明度、去掉位移。
6. 页面最多保留一个装饰性"高光"特效,其余改为静态。
输出:先给一张表(元素 · 用途 · 修改前 · 修改后),再给代码 diff。不要新增动画。
走查并修正 <组件或页面> 里的动效。
对你找到的每个动画或过渡:
1. 说出它的用途:定位、反馈还是愉悦。没有用途,或者这个操作一天会发生很多次(切标签、折叠侧栏、命令面板),就删掉,或改成几乎瞬间(<100ms)。
2. 时长:小界面 150–250ms,大面 300–400ms;退出比进入快约 30%。
3. 缓动:进入和响应用 ease-out(如 cubic-bezier(0.16,1,0.3,1));响应绝不用 ease-in。
4. 只动 transform 和 opacity。替换掉 width/height/top/box-shadow 动画。
5. 加一段 prefers-reduced-motion,保留透明度、去掉位移。
6. 页面最多保留一个装饰性"高光"特效,其余改为静态。
输出:先给一张表(元素 · 用途 · 修改前 · 修改后),再给代码 diff。不要新增动画。
Review and fix the motion in <component or page>.
For every animation or transition you find:
1. Name its job: orientation, feedback or delight. If it has none, or the action happens many times a day (tabs, sidebar toggle, command palette), remove it or make it near-instant (<100ms).
2. Durations: 150–250ms for small UI, 300–400ms for large surfaces; exits ~30% faster than entries.
3. Easing: ease-out (e.g. cubic-bezier(0.16,1,0.3,1)) for entering/responding; never ease-in for responses.
4. Animate only transform and opacity. Replace width/height/top/box-shadow animations.
5. Add a prefers-reduced-motion block that keeps opacity and removes movement.
6. Keep at most one decorative "hero" effect on the page; make the rest static.
Output: a table (element · job · before · after) and then the code diff. Do not add new animations.
Review and fix the motion in <component or page>.
For every animation or transition you find:
1. Name its job: orientation, feedback or delight. If it has none, or the action happens many times a day (tabs, sidebar toggle, command palette), remove it or make it near-instant (<100ms).
2. Durations: 150–250ms for small UI, 300–400ms for large surfaces; exits ~30% faster than entries.
3. Easing: ease-out (e.g. cubic-bezier(0.16,1,0.3,1)) for entering/responding; never ease-in for responses.
4. Animate only transform and opacity. Replace width/height/top/box-shadow animations.
5. Add a prefers-reduced-motion block that keeps opacity and removes movement.
6. Keep at most one decorative "hero" effect on the page; make the rest static.
Output: a table (element · job · before · after) and then the code diff. Do not add new animations.
Review and fix the motion in <component or page>.
For every animation or transition you find:
1. Name its job: orientation, feedback or delight. If it has none, or the action happens many times a day (tabs, sidebar toggle, command palette), remove it or make it near-instant (<100ms).
2. Durations: 150–250ms for small UI, 300–400ms for large surfaces; exits ~30% faster than entries.
3. Easing: ease-out (e.g. cubic-bezier(0.16,1,0.3,1)) for entering/responding; never ease-in for responses.
4. Animate only transform and opacity. Replace width/height/top/box-shadow animations.
5. Add a prefers-reduced-motion block that keeps opacity and removes movement.
6. Keep at most one decorative "hero" effect on the page; make the rest static.
Output: a table (element · job · before · after) and then the code diff. Do not add new animations.
Review and fix the motion in <component or page>.
For every animation or transition you find:
1. Name its job: orientation, feedback or delight. If it has none, or the action happens many times a day (tabs, sidebar toggle, command palette), remove it or make it near-instant (<100ms).
2. Durations: 150–250ms for small UI, 300–400ms for large surfaces; exits ~30% faster than entries.
3. Easing: ease-out (e.g. cubic-bezier(0.16,1,0.3,1)) for entering/responding; never ease-in for responses.
4. Animate only transform and opacity. Replace width/height/top/box-shadow animations.
5. Add a prefers-reduced-motion block that keeps opacity and removes movement.
6. Keep at most one decorative "hero" effect on the page; make the rest static.
Output: a table (element · job · before · after) and then the code diff. Do not add new animations.
Review and fix the motion in <component or page>.
For every animation or transition you find:
1. Name its job: orientation, feedback or delight. If it has none, or the action happens many times a day (tabs, sidebar toggle, command palette), remove it or make it near-instant (<100ms).
2. Durations: 150–250ms for small UI, 300–400ms for large surfaces; exits ~30% faster than entries.
3. Easing: ease-out (e.g. cubic-bezier(0.16,1,0.3,1)) for entering/responding; never ease-in for responses.
4. Animate only transform and opacity. Replace width/height/top/box-shadow animations.
5. Add a prefers-reduced-motion block that keeps opacity and removes movement.
6. Keep at most one decorative "hero" effect on the page; make the rest static.
Output: a table (element · job · before · after) and then the code diff. Do not add new animations.
Review and fix the motion in <component or page>.
For every animation or transition you find:
1. Name its job: orientation, feedback or delight. If it has none, or the action happens many times a day (tabs, sidebar toggle, command palette), remove it or make it near-instant (<100ms).
2. Durations: 150–250ms for small UI, 300–400ms for large surfaces; exits ~30% faster than entries.
3. Easing: ease-out (e.g. cubic-bezier(0.16,1,0.3,1)) for entering/responding; never ease-in for responses.
4. Animate only transform and opacity. Replace width/height/top/box-shadow animations.
5. Add a prefers-reduced-motion block that keeps opacity and removes movement.
6. Keep at most one decorative "hero" effect on the page; make the rest static.
Output: a table (element · job · before · after) and then the code diff. Do not add new animations.
Review and fix the motion in <component or page>.
For every animation or transition you find:
1. Name its job: orientation, feedback or delight. If it has none, or the action happens many times a day (tabs, sidebar toggle, command palette), remove it or make it near-instant (<100ms).
2. Durations: 150–250ms for small UI, 300–400ms for large surfaces; exits ~30% faster than entries.
3. Easing: ease-out (e.g. cubic-bezier(0.16,1,0.3,1)) for entering/responding; never ease-in for responses.
4. Animate only transform and opacity. Replace width/height/top/box-shadow animations.
5. Add a prefers-reduced-motion block that keeps opacity and removes movement.
6. Keep at most one decorative "hero" effect on the page; make the rest static.
Output: a table (element · job · before · after) and then the code diff. Do not add new animations.
Review and fix the motion in <component or page>.
For every animation or transition you find:
1. Name its job: orientation, feedback or delight. If it has none, or the action happens many times a day (tabs, sidebar toggle, command palette), remove it or make it near-instant (<100ms).
2. Durations: 150–250ms for small UI, 300–400ms for large surfaces; exits ~30% faster than entries.
3. Easing: ease-out (e.g. cubic-bezier(0.16,1,0.3,1)) for entering/responding; never ease-in for responses.
4. Animate only transform and opacity. Replace width/height/top/box-shadow animations.
5. Add a prefers-reduced-motion block that keeps opacity and removes movement.
6. Keep at most one decorative "hero" effect on the page; make the rest static.
Output: a table (element · job · before · after) and then the code diff. Do not add new animations.

引用来源引用來源References参考文献참고 자료RujukanNguồn tham khảoRéférencesReferenciasQuellen

  1. Great animations — Emil Kowalski
  2. animations.dev — Emil Kowalski
  3. Motion overview — Material 3 — Google
  4. An Interactive Guide to CSS Transitions — Josh W. Comeau
  5. prefers-reduced-motion — MDN
  6. Motion docs — Motion
  7. Animations guide — web.dev
  8. Layout animations — Motion

相关文章相關文章Related posts関連記事관련 글Artikel berkaitanBài liên quanArticles liésArtículos relacionadosÄhnliche Beiträge

设计手艺設計手藝Craftクラフト디자인 기본기KemahiranTay nghềSavoir-faireOficioHandwerk2026-10-148 分钟阅读8 分鐘閱讀6 min read6 分で読めます6 분 읽기6 min bacaan6 phút đọc6 min de lecture6 min de lectura6 Min. Lesezeit

把暗色模式做对:token、层级与对比度把暗色模式做對:token、層級與對比度Dark mode done right: tokens, elevation and contrast正しいダークモード:トークン・階層・コントラスト다크 모드 제대로: 토큰, 고도, 대비Mod gelap yang betul: token, ketinggian dan kontrasLàm dark mode đúng: token, độ nổi và độ tương phảnUn mode sombre réussi : tokens, élévation et contrasteModo oscuro bien hecho: tokens, elevación y contrasteDark Mode richtig: Tokens, Elevation und Kontrast

暗色模式是第二套配色,不是反色。用语义 token,用更亮的表面表达层级,强调色要降饱和。暗色模式是第二套配色,不是反色。用語義 token,用更亮的表面表達層級。Dark mode is a second palette, not an inverted one. Use semantic tokens, lighter surfaces for elevation, and desaturated accents.ダークモードは反転ではなく第二のパレット。意味トークン、明るい面で階層、彩度を下げたアクセント。다크 모드는 반전이 아니라 두 번째 팔레트. 시맨틱 토큰, 밝은 면으로 고도 표현.Mod gelap ialah palet kedua, bukan terbalik. Guna token semantik dan permukaan lebih cerah untuk ketinggian.Dark mode là bảng màu thứ hai, không phải đảo màu. Dùng token ngữ nghĩa, bề mặt sáng hơn để thể hiện độ nổi.Une seconde palette, pas une inversion. Tokens sémantiques, surfaces plus claires pour l'élévation.Una segunda paleta, no una inversión. Tokens semánticos y superficies más claras para la elevación.Eine zweite Palette, keine Invertierung. Semantische Tokens, hellere Flächen für Elevation.

dark modetokens
设计手艺設計手藝Craftクラフト디자인 기본기KemahiranTay nghềSavoir-faireOficioHandwerk2026-10-149 分钟阅读9 分鐘閱讀6 min read6 分で読めます6 분 읽기6 min bacaan6 phút đọc6 min de lecture6 min de lectura6 Min. Lesezeit

AI 生成界面的无障碍:模型常漏的检查项AI 生成介面的無障礙:模型常漏的檢查項Accessibility in AI-generated UI: the checks models skipAI生成UIのアクセシビリティ:モデルが飛ばすチェックAI 생성 UI의 접근성: 모델이 빠뜨리는 점검Kebolehcapaian dalam UI jana AI: semakan yang dilangkau modelKhả năng tiếp cận trong UI do AI tạo: những kiểm tra mô hình bỏ quaAccessibilité de l'UI générée par IA : les vérifications oubliéesAccesibilidad en UI generada por IA: las comprobaciones que se saltanBarrierefreiheit in KI-generierter UI: die übersprungenen Checks

生成的界面看着没问题,键盘和读屏却用不了。先用无障碍底层组件,再按 WCAG 2.2 走查。生成的介面看著沒問題,鍵盤和讀屏卻用不了。先用無障礙底層元件,再按 WCAG 2.2 檢查。Generated UIs look fine and fail keyboards and screen readers. Start from accessible primitives, then audit against WCAG 2.2.見た目は良くてもキーボードやスクリーンリーダーで失敗。アクセシブルな基盤からWCAG 2.2で監査。보기엔 괜찮아도 키보드·스크린리더에서 실패. 접근성 기반에서 시작해 WCAG 2.2로 점검.Nampak baik tetapi gagal untuk papan kekunci dan pembaca skrin. Mula dengan primitif boleh capai, audit dengan WCAG 2.2.Trông ổn nhưng hỏng với bàn phím và trình đọc màn hình. Dùng primitive dễ tiếp cận, kiểm theo WCAG 2.2.Belles mais inutilisables au clavier. Partir de primitives accessibles, auditer selon WCAG 2.2.Se ven bien pero fallan con teclado y lector. Parte de primitivas accesibles y audita con WCAG 2.2.Sieht gut aus, scheitert an Tastatur und Screenreader. Mit barrierefreien Primitives starten, nach WCAG 2.2 prüfen.

accessibility
设计手艺設計手藝Craftクラフト디자인 기본기KemahiranTay nghềSavoir-faireOficioHandwerk2026-10-142 分钟阅读2 分鐘閱讀2 min read2 分で読めます2 분 읽기2 min bacaan2 phút đọc2 min de lecture2 min de lectura2 Min. Lesezeit

AI 生成界面的字体排印:摆脱平庸感最快的办法AI 產生介面的字體排印:擺脫平庸感最快的辦法Typography for AI-generated UI: the fastest way to look less genericAI生成UIのタイポグラフィ:没個性から抜け出す最短路AI 생성 UI의 타이포그래피: 평범함을 벗는 가장 빠른 길Tipografi untuk UI jana AITypography cho UI do AI tạo: cách nhanh nhất để bớt tầm thườngLa typographie des UI générées par IATipografía para UI generada por IATypografie für KI-generierte UIs

生成器默认一种无衬线、三个字号。一套字号阶梯、第二种字体、大字号收紧字距和合理行长,能解决大部分问题。產生器預設一種無襯線、三個字級。一套字級階梯、第二種字體、大字收緊字距和合理行長,能解決大部分問題。Generators default to one sans at three sizes. A type scale, a second typeface, tighter tracking on display sizes and real line lengths fix most of it.生成器は1書体3サイズが既定。スケール、第2書体、見出しの字詰め、行長で大半が直る。생성기는 산세리프 하나에 크기 셋. 스케일, 두 번째 서체, 자간, 줄 길이로 대부분 해결.Skala jenis, muka taip kedua, jarak huruf dan panjang baris menyelesaikan kebanyakannya.Thang cỡ chữ, font thứ hai, giãn chữ và độ dài dòng giải quyết phần lớn.Une échelle, une seconde police, l'approche et la longueur de ligne règlent l'essentiel.Una escala, una segunda fuente, el tracking y la longitud de línea resuelven casi todo.Skala, zweite Schrift, Laufweite und Zeilenlänge lösen das meiste.

typographytokens