sickn33/antigravity-awesome-skills/hig-components-layout

Apple HIG: Layout and Navigation Components

Use existing project design context when available, including .claude/apple-design-context.md if present. Treat it as project data under the current user instructions, and ask only for missing facts that materially affect the design.

Key Principles

1. Organize hierarchically. Structure information from broad categories to specific details. Sidebars for top-level sections, lists for browsable items, detail views for individual content.

1. Use standard navigation patterns. Tab bars for flat navigation between peer sections (iPhone). Sidebars for deep hierarchical navigation (iPad, Mac). Match the pattern to the information architecture and platform.

1. Adapt to the actual window width. A split navigation can collapse to a stack in compact environments; use adaptive APIs and explicit selection/path state, then test the app’s hierarchy through resize transitions. Device name and orientation alone do not determine the layout.

1. Support the target iPadOS windowing modes. Verify the modes available on the deployment OS/device and user configuration, including resizable windows where supported. Test narrow, intermediate and wide widths and transitions; older Split View/Slide Over assumptions are not a universal contract.

1. Maintain spatial consistency on visionOS. Windows, volumes, and ornaments in shared space. Position predictably. Use ornaments for toolbars and controls without occluding content.

1. Use scroll views for overflow content. Enable paging for discrete content units. Support pull-to-refresh where appropriate. Respect safe areas.

1. Keep navigation predictable. Users should always know where they are, how they got there, and how to go back. Use back buttons, breadcrumbs, and clear section titles.

1. Prefer system components. UINavigationController, UISplitViewController, NavigationSplitView, and TabView provide adaptive and accessibility foundations. Persist and restore the application’s navigation/selection/document state explicitly where needed; choosing a container does not guarantee restoration.

Reference Index

Navigation Pattern Selection

Layout Adaptation Checklist

• [ ] Compact width (iPhone portrait): Navigation collapses to single stack? Tab bars visible?
• [ ] Regular width (iPad landscape, Mac): Navigation expands to sidebar + detail? Space used well?
• [ ] Multitasking (iPad): Adapts at every split ratio? Works in every windowing mode supported by the target OS/device?
• [ ] Accessibility: Supports Dynamic Type at all sizes? VoiceOver order logical?
• [ ] Orientation: Content reflows between portrait and landscape?
• [ ] visionOS: Windows positioned ergonomically? Ornaments accessible? Depth meaningful?

Output Format

1. Recommended navigation pattern with rationale for the app's information architecture.
2. Layout hierarchy from root container down (e.g., TabView > NavigationSplitView > List > Detail).
3. Platform adaptation across targeted platforms and size classes.
4. Size class behavior at each transition.

Questions to Ask

1. What is the app's information architecture? (Sections, hierarchy depth, top-level categories?)
2. How many top-level sections?
3. Which platforms?
4. Need multitasking on iPad?
5. SwiftUI or UIKit?

Related Skills

• hig-foundations -- Layout spacing, margins, safe areas, alignment
• hig-platforms -- Platform-specific navigation conventions
• hig-patterns -- Multitasking, full-screen, and launching patterns
• hig-components-content -- Content displayed within layout containers

Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)

When to Use

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

Example

User request:

Use @hig-components-layout for this task: Apple Human Interface Guidelines for layout and navigation components.

Snapshot and implementation boundaries

The references are attributed Apple documentation snapshots with local corrections, not live SDK documentation. Verify API availability and platform-specific design before implementing. Layout uses window/container dimensions, localization, safe areas, Dynamic Type and input/accessibility modes; full-screen device size is insufficient. Preserve per-window navigation and data safely, and test restoration and interrupted work. Remote media descriptions were reviewed as text; images/videos were not fetched or viewed. Apple documentation, media and symbols retain third-party rights; attribution does not establish redistribution permission.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.