apple-design

name	apple-design
description	Router for Apple platform design: navigation, search, typography, visual accessibility, Liquid Glass/iOS 26, brand identity, app icons, App Intents/Shortcuts, HIG lookup, and chart experience. Use for HIG/current-spec questions or Apple design decisions. Implementation/platform craft → swiftui; web counterparts → web-design. Read one named reference.

Apple Platform Design

Sources/gaps: references/sources.md maps the local Apple source corpus; references/coverage-gaps.md lists platform areas that need live HIG/doc verification before becoming reusable rules.

Read exactly one reference file below; each carries the full distillation for its area (deeper worked examples, sources, and code live in a same-named subdirectory next to it).

• Navigation & layout — structuring tabs vs sidebar, push vs modal, sheet/menu rules, destructive confirmations, iPad-native layout and iPadOS 26 windowing, the pointer: references/apple-navigation-design.md
• Search — where search lives and how placement signals scope, suggestions, recents, scope bars, tokens, no-results states: references/apple-search-design.md
• Typography — the San Francisco family, optical sizes, text styles, full Dynamic Type support incl. custom font scaling, fixing truncated/clipped text: references/apple-typography.md
• Visual accessibility — auditing/adding a11y: Bold Text, Increase Contrast, Differentiate Without Color, Reduce Motion, 4.5:1 contrast, colorblindness, Smart Invert: references/apple-visual-accessibility.md
• Liquid Glass & the 2025+ design system — the material (lensing, Regular vs Clear, tinting, never glass-on-glass), shapes/concentricity, toolbars, scroll edge effects, migration playbook: references/liquid-glass-design-system.md
• Brand identity on iOS — how much to customize without breaking the native feel: UI layer vs content layer, custom vs standard components, brand color/tint, fonts, logos, Dark Mode: references/ios-brand-identity.md
• App icons — designing/reviewing an icon: metaphor, simplicity, small-size testing, the layered Liquid Glass icon system and Icon Composer, dark/tinted/clear variants: references/app-icon-design.md
• App Intents & Shortcuts — which features to expose as intents, invocation phrases, parameters, snippets vs Live Activities, Siri/Spotlight/widgets/controls/Action button: references/app-intents-design.md
• HIG lookup — canonical/current HIG lookup — exact specs, component conventions; the live-fetch playbook: references/hig.md
• Classic HIG principles — 2014 local iOS/OS X HIG doctrine: deference, clarity, depth, aesthetic integrity, user control, Mac modality/keyboard/help conventions; current specs still defer to HIG lookup: references/classic-hig-principles.md
• Chart experience — in-app chart experience: platters, progressive disclosure, Swift Charts, Audio Graphs, chart a11y labels — general chart-type choice and Tufte critique → data-viz: references/chart-experience-design.md

Boundary splits to respect:

• Implementation and platform craft → swiftui — this skill decides the design; SwiftUI/UIKit code, gestures, widgets, SF Symbols, animation engineering live there.
• Canonical current specs → references/hig.md — talk-derived references here carry reasoning and craft; when you need Apple's exact letter-of-the-law spec (or a staleness tiebreaker), fetch the live HIG via that playbook.
• Typography split: Apple platforms → this skill's apple-typography reference; web/CSS → web-design (web-typography). Never cross-apply platform conventions.
• Accessibility split: Apple platforms → this skill's apple-visual-accessibility reference; web → web-design (web-accessibility) (same split as typography).
• Principles translate; specs don't. Apple's interaction principles (fluid response, interruptibility, momentum, spatial consistency — swiftui (touch-interaction-design)) and its eight design values (design-principles) are platform-agnostic and carry to the web, where web-design (web-animation-design) and design-craft (emil-kowalski) are their homes. Only the platform-specific specs — type tracking, a11y APIs, component conventions, the Liquid Glass material — must never cross-apply.