iOS Human Interface

# iOS Human Interface## UsageUse this DESIGN.md as a reusable design brief for an AI coding agent. Apply it when building a new page, restyling an existing interface, or keeping multiple screens visually consistent.## Design IntentYou are implementing an interface using the **iOS Human Interface** design language. 强调内容优先、直接操控、清晰层级、系统字体、模糊材质和一致手势，适合原生 Apple 生态体验。Treat predictability, native conventions, accessibility, and component consistency as the main design material.## Aliases- Apple HIG- iOS 风格## Category- 平台与系统## Target Platforms- 移动端- PC 端## Summary强调内容优先、直接操控、清晰层级、系统字体、模糊材质和一致手势，适合原生 Apple 生态体验。## Visual DNA- 内容优先- 系统圆角- 模糊层- 清晰触控目标## Best Use Cases- iOS App- macOS 工具- 系统级小组件- Apple 风格官网## Avoid WhenWeb 品牌需要避免像系统设置页，或跨平台体验要保持中性。## Anatomy导航、列表、分组、分割线和按钮状态要符合平台习惯，少做自创交互。## Color SystemUse a Seed → Map → Semantic → Alias token architecture. Components must consume named tokens instead of hard-coded colors.### Reference Palette- **reference-1** `#f2f2f7`- **reference-2** `#ffffff`- **reference-3** `#007aff`- **reference-4** `#34c759`- **reference-5** `#1c1c1e`### Seed Tokens- **colorBgBase** `#f2f2f7` - 页面基础背景.- **colorBgContainer** `#ebebef` - 卡片、面板与容器.- **colorFillSecondary** `#e1e1e6` - 次级填充与弱状态.- **colorPrimary** `#007aff` - 品牌主操作与选中态.- **colorTextBase** `#1c1c1e` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#e6f2ff`- **primary-2** `#c7e2ff`- **primary-3** `#a3cfff`- **primary-4** `#7abaff`- **primary-5** `#479fff`- **primary-6** `#007aff`- **primary-7** `#036fe4`- **primary-8** `#0763c9`- **primary-9** `#0a58ae`- **primary-10** `#0e4b8f`### Neutral Scale- **neutral-1** `#ffffff`- **neutral-2** `#f6f6f6`- **neutral-3** `#ededed`- **neutral-4** `#dbdbdb`- **neutral-5** `#bfbfc0`- **neutral-6** `#a0a0a1`- **neutral-7** `#7b7b7d`- **neutral-8** `#5c5c5d`- **neutral-9** `#3c3c3e`- **neutral-10** `#1c1c1e`### Semantic Tokens- **colorSuccess** `#34c759` - 成功、在线、已完成.- **colorSuccessBg** `#e7f8eb` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#faefe1` - 警告状态浅背景.- **colorError** `#dc2626` - 错误、危险、阻断.- **colorErrorBg** `#fce9e9` - 错误状态浅背景.- **colorInfo** `#007aff` - 信息、链接、进行中.- **colorInfoBg** `#e0efff` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#eeeef3` - 应用整体画布.- **colorBgElevated** `#eeeef2` - 弹层、浮层与菜单.- **colorBgSpotlight** `#3c3c3e` - Tooltip 与强提示.- **colorBorder** `#dbdbdb` - 控件与容器边框.- **colorBorderSecondary** `#ededed` - 轻分隔线.- **colorText** `#1c1c1e` - 一级文本.- **colorTextSecondary** `#606063` - 二级文本.- **colorTextTertiary** `#87878b` - 辅助说明.- **colorTextDisabled** `#a9a9ad` - 禁用文本.- **colorPrimaryHover** `#479fff` - 主操作 Hover.- **colorPrimaryActive** `#036fe4` - 主操作 Active.- **colorPrimaryBorder** `#7abaff` - 主色边框.- **colorPrimaryBg** `#e6f2ff` - 主色浅背景.- **colorLink** `#007aff` - 链接与可跳转文本.- **colorFocus** `#7abaff` - 键盘焦点环.- **colorMask** `#141416` - Modal 遮罩基础色.Color rules:- Use the palette as design tokens, not random decorative swatches.- Keep primary text and primary actions at accessible contrast.- Use primary-1 through primary-10 for interaction states instead of inventing new brand colors.- Use semantic tokens consistently for success, warning, error, and info; pair color with iconography or text.- Map component styles to Alias Tokens so theme changes do not require component-level color edits.## Typography- Use a modern system sans-serif stack by default; only introduce a custom font when the brand direction requires it.- Headings should be confident but not ornamental; body text must remain readable across mobile and desktop.- Keep labels short, high-contrast, and aligned to the component structure.## Layout And Spacing- Use an 8px spacing base; reserve 4px for micro-gaps and 32px+ for major layout separation.- Keep cards, panels, controls, and lists dimensionally stable across responsive breakpoints.- On mobile, reduce column count before reducing legibility.- Recommended radius: 8-16px radius for cards and controls; keep system consistency more important than novelty.- Elevation and shadow: Use shadows to separate interactive or elevated surfaces only; avoid stacking many shadow styles.## Component Rules- Components should reinforce the primary information structure rather than introduce a separate decorative style.- Primary actions must be visually obvious and reachable; secondary actions should be quieter but still discoverable.- Cards need a clear title, supporting text or metric, state, and one obvious next action when action is expected.- Forms and filters should use familiar controls, stable dimensions, clear labels, and visible focus states.- Empty, loading, error, and success states must use the same visual language, not generic placeholders.## Interaction And Motion- Use subtle 120-220ms transitions for hover, focus, open, close, and selection states.- Motion should clarify state changes rather than decorate the page.- Respect reduced-motion preferences.## Implementation Recipe1. Start with the real user workflow and page structure; do not make a generic landing page unless explicitly requested.2. Establish layout zones first: navigation, content, controls, feedback, and primary action.3. Apply the color tokens to semantic roles: canvas, surface, text, border, accent, danger, and success.4. Build reusable components that express this style: buttons, cards, inputs, tabs, filters, modals, empty states, and status badges.5. Verify mobile and desktop breakpoints before adding decorative polish.6. Check that the final screen still communicates 内容优先, 系统圆角, 模糊层 without relying on a single color or effect.## Quality Checklist- The screen is immediately recognizable as **iOS Human Interface**, not a generic Tailwind layout.- The design uses surface, spacing, typography, and component shape together; it does not rely only on colors.- Primary actions and navigation are clear on both mobile and desktop.- Text is readable, controls are stable, and content does not overlap or shift unexpectedly.- Empty, loading, hover, focus, selected, disabled, success, and error states are styled in the same language.- The implementation avoids the known failure mode: Web 品牌需要避免像系统设置页，或跨平台体验要保持中性。## Anti-Patterns- Do not paste this palette onto an unrelated layout and call it finished.- Do not overuse decorative effects where the user needs to read, compare, or act quickly.- Do not mix this style with unrelated visual languages unless the product explicitly requires a hybrid.- Do not hide important state behind low contrast, blur, tiny text, or animation.## Keywords- ios- apple- hig- native## Agent Prompt SnippetImplement the UI in the **iOS Human Interface** design language. Prioritize 内容优先, 系统圆角, 模糊层. Use the color roles, typography guidance, spacing rules, component rules, and anti-patterns from this DESIGN.md as hard constraints. The result should feel purpose-built for iOS App, macOS 工具, 系统级小组件, while avoiding: Web 品牌需要避免像系统设置页，或跨平台体验要保持中性。