Back to Skills

hig-components-layout

raintree-technology
Updated 4 days ago
78
9
78
View on GitHub
Metadesign

About

This skill provides Apple's Human Interface Guidelines for layout and navigation components like sidebars, tab bars, and split views. Use it when designing app structure, choosing navigation patterns, or solving adaptive layout issues across Apple platforms. It references related HIG skills for foundations, platforms, and content display.

Quick Install

Claude Code

Recommended
Primary
npx skills add raintree-technology/claude-starter -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/raintree-technology/claude-starter
Git CloneAlternative
git clone https://github.com/raintree-technology/claude-starter.git ~/.claude/skills/hig-components-layout

Copy and paste this command in Claude Code to install this skill

Documentation

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

ReferenceTopicKey content
sidebars.mdSidebarsSource lists, selection state, collapsible sections, iPad/Mac patterns
column-views.mdColumn ViewsFinder-style browsing, progressive disclosure through columns
outline-views.mdOutline ViewsExpandable hierarchies, disclosure triangles, tree structures
split-views.mdSplit ViewsTwo/three column layouts, NavigationSplitView, adaptive collapse
tab-views.mdTab ViewsSegmented tabs, page-style tabs, macOS tab grouping
tab-bars.mdTab BarsBottom tab bars (iOS), badge counts, max tab count
scroll-views.mdScroll ViewsPaging, scroll indicators, content insets, pull-to-refresh
windows.mdWindowsmacOS/visionOS window management, sizing, full-screen, restoration
panels.mdPanelsInspector panels, utility panels, floating panels, macOS conventions
lists-and-tables.mdLists and TablesPlain/grouped/inset-grouped styles, swipe actions, section headers
boxes.mdBoxesContent grouping containers, labeled boxes, macOS grouping
ornaments.mdOrnamentsvisionOS toolbar attachments, positioning, visibility

Navigation Pattern Selection

App StructureRecommended PatternPlatform Adaptation
3-5 peer top-level sectionsTab BariPhone: bottom tab bar. iPad: sidebar (.sidebarAdaptable, iPadOS 18+). Mac: sidebar or toolbar tabs
Deep hierarchical contentSidebar + NavigationSplitViewiPhone: single column stack. iPad: two/three columns. Mac: full multi-column
Deep file/folder treeColumn ViewMac: Finder-style. iPad: adaptable. iPhone: push navigation
Flat list with detailSplit View (two column)iPhone: push/pop stack. iPad/Mac: primary + detail columns
Document-based with inspectorsWindow + PanelsMac: main window with inspector. iPad: sheet or popover
Spatial app with toolsWindow + OrnamentsvisionOS: 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 · More developer tools

GitHub Repository

raintree-technology/claude-starter
Path: templates/.claude/skills/hig-components-layout
0
ai-toolsanthropicclaudeclaude-aiclaude-codedeveloper-tools

Related Skills

content-collections

Meta

This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.

View skill

polymarket

Meta

This skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.

View skill

creating-opencode-plugins

Meta

This skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.

View skill

sglang

Meta

SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.

View skill