hig-components-layout
Apple Human Interface Guidelines for layout and navigation components.
About this skill
This skill equips an AI agent with foundational principles and best practices from Apple's Human Interface Guidelines (HIG) specifically for layout and navigation components. It instructs the agent to consult existing design context files (e.g., `.claude/apple-design-context.md`) and apply key principles such as hierarchical information organization and the use of standard, platform-appropriate navigation patterns (like tab bars for iPhone and sidebars for iPad/Mac). The skill's primary aim is to enable the AI to provide accurate, context-aware, and platform-specific design recommendations that are aligned with Apple's official design philosophy and user experience principles.
Best use case
Guiding the AI agent to provide design feedback, suggest optimal layout structures, or advise on navigation patterns for applications targeting Apple platforms (iOS, iPadOS, macOS). It is highly useful for generating design briefs, evaluating existing UI/UX against HIG, or for learning about Apple's specific design philosophy and component usage.
Apple Human Interface Guidelines for layout and navigation components.
The AI agent will provide design recommendations and critiques that are highly consistent with Apple's Human Interface Guidelines for layout and navigation. It will demonstrate a clear understanding of platform-specific design patterns, hierarchical organization, and the appropriate use of standard UI components, ensuring its advice is practical and aligned with Apple's UX standards.
Practical example
Example input
I'm designing a new productivity app for iPad. What are the key Apple Human Interface Guidelines I should follow for its main navigation and content organization?
Example output
For an iPad productivity app, Apple's Human Interface Guidelines emphasize efficient use of screen real estate and clear hierarchical organization. Here are some key points: 1. **Sidebar for Primary Navigation:** For deep, hierarchical navigation on iPad, a **sidebar** is the standard and recommended pattern. This allows users to browse top-level sections or categories on the left while viewing detailed content on the right. It should be easily collapsible or adjustable. 2. **Organize Hierarchically:** Structure your information from broad categories to specific details. For example, your sidebar might list 'Projects,' 'Tasks,' 'Notes,' and selecting 'Projects' would show a list of projects in the main content area. Tapping a specific project would then reveal its details. 3. **Use Navigation Bars for Context:** Within each main content view, a navigation bar at the top can provide context (e.g., the current project title), back buttons for deeper views, and actions relevant to the current screen (e.g., 'Edit,' 'Add New Task'). 4. **Embrace Multi-column Layouts:** Leverage the iPad's larger screen to display multiple content panes simultaneously, like a master-detail view where the sidebar is the master, and the main area shows details, perhaps even split into two columns for richer content. Ensure responsive layouts that adapt when the sidebar is shown/hidden or in split view. By following these principles, your app will feel intuitive and familiar to iPad users, making it easy to navigate and manage their productivity tasks effectively.
When to use this skill
- When an AI agent needs to offer design advice specific to Apple platforms.
- When evaluating application layouts and navigation against Apple's official guidelines.
- When designing new features or entire applications for iOS, iPadOS, or macOS.
- When seeking to understand the rationale behind Apple's design decisions for components like tab bars and sidebars.
When not to use this skill
- When designing for non-Apple platforms (e.g., Android, Windows, web) where different design guidelines apply.
- When the design task requires creative exploration or unconventional solutions that intentionally deviate from established HIG principles.
- When the agent needs to perform an action that involves external tool usage, API calls, or complex data processing (this skill is focused on knowledge application and reasoning).
- When seeking information about specific implementation details or coding practices, rather than high-level design guidance.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hig-components-layout/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hig-components-layout Compares
| Feature / Agent | hig-components-layout | Standard Approach |
|---|---|---|
| Platform Support | Claude | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | easy | N/A |
Frequently Asked Questions
What does this skill do?
Apple Human Interface Guidelines for layout and navigation components.
Which AI agents support this skill?
This skill is designed for Claude.
How difficult is it to install?
The installation complexity is rated as easy. You can find the installation instructions above.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Apple HIG: Layout and Navigation Components Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered. ## 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. 2. **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. 3. **Adapt to screen size.** Three-column on iPad collapses to single-column on iPhone. Use size classes and adaptive APIs (NavigationSplitView) for automatic adaptation. 4. **Support multitasking on iPad.** Respond gracefully to Split View, Slide Over, and Stage Manager. Test at every split ratio and size class transition. 5. **Maintain spatial consistency on visionOS.** Windows, volumes, and ornaments in shared space. Position predictably. Use ornaments for toolbars and controls without occluding content. 6. **Use scroll views for overflow content.** Enable paging for discrete content units. Support pull-to-refresh where appropriate. Respect safe areas. 7. **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. 8. **Prefer system components.** UINavigationController, UISplitViewController, NavigationSplitView, and TabView provide built-in adaptivity, accessibility, and state restoration. ## Reference Index | Reference | Topic | Key content | |---|---|---| | [sidebars.md](references/sidebars.md) | Sidebars | Source lists, selection state, collapsible sections, iPad/Mac patterns | | [column-views.md](references/column-views.md) | Column Views | Finder-style browsing, progressive disclosure through columns | | [outline-views.md](references/outline-views.md) | Outline Views | Expandable hierarchies, disclosure triangles, tree structures | | [split-views.md](references/split-views.md) | Split Views | Two/three column layouts, NavigationSplitView, adaptive collapse | | [tab-views.md](references/tab-views.md) | Tab Views | Segmented tabs, page-style tabs, macOS tab grouping | | [tab-bars.md](references/tab-bars.md) | Tab Bars | Bottom tab bars (iOS), badge counts, max tab count | | [scroll-views.md](references/scroll-views.md) | Scroll Views | Paging, scroll indicators, content insets, pull-to-refresh | | [windows.md](references/windows.md) | Windows | macOS/visionOS window management, sizing, full-screen, restoration | | [panels.md](references/panels.md) | Panels | Inspector panels, utility panels, floating panels, macOS conventions | | [lists-and-tables.md](references/lists-and-tables.md) | Lists and Tables | Plain/grouped/inset-grouped styles, swipe actions, section headers | | [boxes.md](references/boxes.md) | Boxes | Content grouping containers, labeled boxes, macOS grouping | | [ornaments.md](references/ornaments.md) | Ornaments | visionOS toolbar attachments, positioning, visibility | ## Navigation Pattern Selection | App Structure | Recommended Pattern | Platform Adaptation | |---|---|---| | 3-5 peer top-level sections | Tab Bar | iPhone: bottom tab bar. iPad: sidebar (`.sidebarAdaptable`, iPadOS 18+). Mac: sidebar or toolbar tabs | | Deep hierarchical content | Sidebar + NavigationSplitView | iPhone: single column stack. iPad: two/three columns. Mac: full multi-column | | Deep file/folder tree | Column View | Mac: Finder-style. iPad: adaptable. iPhone: push navigation | | Flat list with detail | Split View (two column) | iPhone: push/pop stack. iPad/Mac: primary + detail columns | | Document-based with inspectors | Window + Panels | Mac: main window with inspector. iPad: sheet or popover | | Spatial app with tools | Window + Ornaments | visionOS: ornaments on window. Other platforms: toolbars | ## 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 Slide Over? - [ ] **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.
Related Skills
hig-components-status
Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings.
hig-components-menus
Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.
hig-components-controls
Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.
makepad-layout
CRITICAL: Use for Makepad layout system. Triggers on: makepad layout, makepad width, makepad height, makepad flex, makepad padding, makepad margin, makepad flow, makepad align, Fit, Fill, Size, Walk, "how to center in makepad", makepad 布局, makepad 宽度, makepad 对齐, makepad 居中
hig-components-system
Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts.
hig-components-dialogs
Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views.
hig-components-content
Apple Human Interface Guidelines for content display components.
core-components
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
nft-standards
Master ERC-721 and ERC-1155 NFT standards, metadata best practices, and advanced NFT features.
nextjs-app-router-patterns
Comprehensive patterns for Next.js 14+ App Router architecture, Server Components, and modern full-stack React development.
new-rails-project
Create a new Rails project
networkx
NetworkX is a Python package for creating, manipulating, and analyzing complex networks and graphs.