emil 设计 Engineer
- 作者仓库星标 0
- 作者仓库 sea-prototype-template
Emil's Design Engineering Principles
A comprehensive guide for building polished, accessible web interfaces based on Emil Kowalski's design engineering practices.
Quick Reference
| Category | When to Use |
|---|---|
| Animations | Enter/exit transitions, easing, springs, performance |
| UI Polish | Typography, visual design, layout, colors |
| Forms & Controls | Inputs, buttons, form submission |
| Touch & Accessibility | Mobile, touch devices, keyboard nav, a11y |
| Component Design | Compound components, composition, props API |
| Marketing | Landing pages, blogs, docs sites |
| Performance | Virtualization, preloading, optimization |
Core Principles
1. No Layout Shift
Dynamic elements should cause no layout shift. Use hardcoded dimensions, font-variant-numeric: tabular-nums for changing numbers, and avoid font weight changes on hover/selected states.
2. Touch-First, Hover-Enhanced
Design for touch first, then add hover enhancements. Disable hover effects on touch devices. Ensure 44px minimum tap targets. Never rely on hover for core functionality.
3. Keyboard Navigation
Tabbing should work consistently. Only allow tabbing through visible elements. Ensure keyboard navigation scrolls elements into view with scrollIntoView().
4. Accessibility by Default
Every animation needs prefers-reduced-motion support. Every icon button needs an aria label. Every interactive element needs proper focus states.
5. Speed Over Delight
Product UI should be fast and purposeful. Skip animations for frequently-used interactions. Marketing pages can be more elaborate.
Decision Flowcharts
Should I Animate This?
Will users see this 100+ times daily?
├── Yes → Don't animate
└── No
├── Is this user-initiated?
│ └── Yes → Animate with ease-out (150-250ms)
└── Is this a page transition?
└── Yes → Animate (300-400ms max)
What Easing Should I Use?
Is the element entering or exiting?
├── Yes → ease-out
└── No
├── Is it moving on screen?
│ └── Yes → ease-in-out
└── Is it a hover/color change?
├── Yes → ease
└── Default → ease-out
Common Mistakes
| Mistake | Fix |
|---|---|
transition: all |
Specify exact properties |
| Hover effects on touch | Use @media (hover: hover) |
| Font weight change on hover | Use consistent weights |
Animating height/width |
Use transform and opacity only |
| No reduced motion support | Add prefers-reduced-motion query |
| z-index: 9999 | Use fixed scale or isolation: isolate |
| Custom page scrollbars | Only customize scrollbars in small elements |
Review Checklist
When reviewing UI code, check:
- No layout shift on dynamic content
- Animations have reduced motion support
- Touch targets are 44px minimum
- Hover effects disabled on touch devices
- Keyboard navigation works properly
- Icon buttons have aria labels
- Forms submit with Enter/Cmd+Enter
- Inputs are 16px+ to prevent iOS zoom
- No
transition: all - z-index uses fixed scale
Reference Files
For detailed guidance on specific topics:
- animations.md - Easing, timing, springs, performance
- ui-polish.md - Typography, shadows, gradients, scrollbars
- forms-controls.md - Inputs, buttons, form patterns
- touch-accessibility.md - Touch devices, keyboard nav, a11y
- component-design.md - Compound components, composition, props API
- marketing.md - Landing pages, blogs, docs
- performance.md - Virtualization, preloading, optimization
- 流狐分类
- 设计与多媒体
- 作者声明 Agent
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 作者 / 版本 / 许可
- @lemu · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 Category · When to Use Animations · Enter/exit transitions, easing, springs, performance UI Polish · Typography, visual design, layout, colors
Core Principles
Dynamic elements should cause no layout shift. Use hardcoded dimensions, font-variant-numeric: tabular-nums for changing numbers, and avoid font weight changes on hover/selected states.
Design for touch first, then add hover enhancements. Disable hover effects on touch devices. Ensure 44px minimum tap targets. Never rely on hover for core functionality.
Tabbing should work consistently. Only allow tabbing through visible elements. Ensure keyboard navigation scrolls elements into view with scrollIntoView().
Every animation needs prefers-reduced-motion support. Every icon button needs an aria label. Every interactive element needs proper focus states.
# Emil's Design Engineering Principles
A comprehensive guide for building polished, accessible web interfaces based on Emil Kowalski's design engineering practices.
## Quick Reference
| Category | When to Use |
| --- | --- |
| [Animations](animations.md) | Enter/exit transitions, easing, springs, performance |
| [UI Polish](ui-polish.md) | Typography, visual design, layout, colors |
| [Forms & Controls](forms-controls.md) | Inputs, buttons, form submission |
| [Touch & Accessibility](touch-accessibility.md) | Mobile, touch devices, keyboard nav, a11y |
| [Component Design](component-design.md) | Compound components, composition, props API |
| [Marketing](marketing.md) | Landing pages, blogs, docs sites |
| [Performance](performance.md) | Virtualization, preloading, optimization |
## Core Principles
### 1. No Layout Shift
Dynamic elements should cause no layout shift. Use hardcoded dimensions, `font-variant-numeric: tabular-nums` for changing numbers, and avoid font weight changes on hover/selected states.
### 2. Touch-First, Hover-Enhanced
Design for touch first, then add hover enhancements. Disable hover effects on touch devices. Ensure 44px minimum tap targets. Never rely on hover for core functionality.
### 3. Keyboard Navigation
Tabbing should work consistently. Only allow tabbing through visible elements. Ensure keyboard navigation scrolls elements into view with `scrollIntoView()`.
### 4. Accessibility by Default
Every animation needs `prefers-reduced-motion` support. Every icon button needs an aria label. Every interactive element needs proper focus states.
### 5. Speed Over Delight
Product UI should be fast and purposeful. Skip animations for frequently-used interactions. Marketing pages can be more elaborate.
## Decision Flowcharts
… 作者原文负责流程事实;流狐只索引当前章节、要点、文件与命令。
章节 -> Quick Reference → Core Principles → 1. No Layout Shift → 2. Touch-First, Hover-Enhanced → 3. Keyboard Navigation → 4. Accessibility by Default
要点 -> A comprehensive guide for building polished, accessible web interfaces based on Emil Kowalski's design engineering practices. · Dynamic elements should cause no layout shift. · Design for touch first, then add hover enhancements. · Tabbing should work consistently. · Every animation needs prefers-reduced-motion support. · Product UI should be fast and purposeful.
文件/命令 -> font-variant-numeric: tabular-nums · scrollIntoView() · prefers-reduced-motion · transition: all · @media (hover: hover) · height · width · transform
内容 SHA-256 -> 6e853b5b0ebc
原文结构
适用与边界
原文中的明确线索
font-variant-numeric: tabular-nums、scrollIntoView()、prefers-reduced-motion、transition: all、@media (hover: hover)、height、width、transform