AGENT SKILL

hig_platforms

Apple Human Interface Guidelines for platform-specific design.

使用场景视觉设计
License 许可
MIT
最近更新
2026-09-30
Stars
★ 9
Forks
0

01 前言 Front Matter

name
hig_platforms
risk
unknown
source
community
date_added
2026-02-27
description
Apple Human Interface Guidelines for platform-specific design.

02 资源文件 10

03 SKILL.md 正文

Apple HIG: Platform Design

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

  1. Each platform has a distinct identity. Do not port designs between platforms. Respect each platform's conventions, interaction models, and user expectations.

  2. iOS: touch-first. Direct manipulation on a handheld screen. Optimize for one-handed use. Navigation uses tab bars and push/pop stacks.

  3. iPadOS: expanded canvas. Support Split View, Slide Over, and Stage Manager. Use sidebars and multi-column layouts. Support pointer and keyboard alongside touch.

  4. macOS: pointer and keyboard. Dense information display is acceptable. Use menu bars, toolbars, and keyboard shortcuts extensively. Windows are resizable with precise control.

  5. tvOS: remote and focus. Viewed from a distance. Design for the Siri Remote with focus-based navigation. Large text, simple layouts, linear navigation.

  6. visionOS: spatial interaction. 3D environment using windows, volumes, and spaces. Eye tracking for targeting, indirect gestures for interaction. Respect ergonomic comfort zones.

  7. watchOS: glanceable and brief. Information consumable at a glance. Brief interactions. Digital Crown, haptics, and complications for timely content.

  8. Games: own paradigm. Free to define in-game interaction models, but still respect platform conventions for system interactions (notifications, accessibility, controllers).

Reference Index

Reference Topic Key content
designing-for-ios.md iOS Touch, tab bars, navigation stacks, gestures, screen sizes, safe areas
designing-for-ipados.md iPadOS Multitasking, sidebars, pointer, keyboard, Apple Pencil, Stage Manager
designing-for-macos.md macOS Menu bars, toolbars, window management, keyboard shortcuts, dense layouts, Dock
designing-for-tvos.md tvOS Focus engine, Siri Remote, lean-back experience, content-forward, parallax
designing-for-visionos.md visionOS Spatial computing, windows/volumes/spaces, eye tracking, hand gestures, depth
designing-for-watchos.md watchOS Glanceable UI, Digital Crown, complications, notifications, haptics
designing-for-games.md Games Controllers, immersive experiences, platform-specific conventions, accessibility

Decision Framework

  1. Identify the primary use context. On the go (iOS/watchOS), at a desk (macOS), on the couch (tvOS), spatial environment (visionOS)?

  2. Match input to interaction. Touch for direct manipulation, pointer for precision, gaze+gesture for spatial, Digital Crown for quick scrolling, remote for focus navigation.

  3. Adapt, don't replicate. A macOS sidebar becomes a tab bar on iPhone. A visionOS volume has no equivalent on watchOS. Translate intent, not implementation.

  4. Leverage platform strengths. Live Activities on iOS, Desktop Widgets on macOS, complications on watchOS, immersive spaces on visionOS.

  5. Maintain brand consistency while respecting each platform's visual language and interaction patterns.

Output Format

  1. Platform-specific recommendations citing relevant HIG sections.
  2. Platform differences table comparing navigation, input, layout, and conventions.
  3. Implementation notes per platform including recommended APIs and adaptation strategies.

Questions to Ask

  1. Which platforms are you targeting?
  2. New app or adapting an existing one? If existing, which platform is the base?
  3. SwiftUI or UIKit/AppKit?
  4. Need to support older OS versions?
  5. Primary use context? (On the go, desk, couch, spatial, glanceable?)

Related Skills

  • hig-foundations -- Shared principles (color, typography, accessibility, layout) across platforms
  • hig-patterns -- Interaction patterns that manifest differently per platform
  • hig-components-layout -- Navigation structures (tab bars, sidebars, split views) that vary by platform
  • hig-components-content -- Content display that adapts across platforms

Built by Raintree Technology · More developer tools

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

04 同仓库更多 Skills

LongLeo287
LongLeo287/OmniClaw

UI-UX Pro Max

Advanced UI/UX analysis and generation skills with data-driven patterns. Python scripts (core.py, search.py) for systematic UI pattern extraction, design system generation, and component search from curated data sources.

设计师数据分析师视觉设计Skill与智能体开发
★ 9
LongLeo287
LongLeo287/OmniClaw

shadcn-ui

Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization, and best practices.

设计师
★ 9
LongLeo287
LongLeo287/OmniClaw

zustand_store_ts

Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.

前端开发
★ 9
LongLeo287
LongLeo287/OmniClaw

zustand

Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.

★ 9
LongLeo287
LongLeo287/OmniClaw

youtube_summarizer

Automatically fetch YouTube video transcripts, generate structured summaries, and send full transcripts to messaging platforms. Detects YouTube URLs and provides metadata, key insights, and downloadable transcripts.

图像与多媒体Skill与智能体开发
★ 9
LongLeo287
LongLeo287/OmniClaw

youtube_clipper

YouTube 视频智能剪辑工具。下载视频和字幕,AI 分析生成精细章节(几分钟级别), 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频,并生成总结文案。 使用场景:当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词:视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video

★ 9