Skip to content
Back to skills

Apple Hig Tab Views

ASecurity

Use when choosing, reviewing, or adapting mutually exclusive related content panes within a shared view.

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 26, 2026
ai-agentsgoswiftapi

Works with

  • api

Security analysis

A100/100

Scanned October 26, 2026

npx -y skills add AyushRajSinghParihar/apple-human-interface-skills --skill apple-hig-tab-views --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apple Hig Tab Views?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Apple Hig Tab Views
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ayushrajsinghparihar-apple-hig-tab-views/badge)](https://www.skillsdirectory.com/skills/ayushrajsinghparihar-apple-hig-tab-views)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: apple-hig-tab-views
description: Use when choosing, reviewing, or adapting mutually exclusive related content panes within a shared view.
---

# Keep pane switching distinct from app navigation

Read [the tab-view guide](../../references/tab-views.md). This procedure is application advice; distinguish the conventional Mac pane control from top-level tab bars and framework names.

Inspect the pane contents, affected controls, platform, and create/review/adapt request. Determine whether the choices are self-contained related views or unrelated app destinations. Count meaningful choices, record their labels, and identify any action that affects another pane.

Use tabs for a small set of related panes, with short predictive labels and controls scoped to their pane. Keep the tab control visible unless switching is programmatic; otherwise people lose the route among choices. Evaluate another presentation already at six or more choices rather than squeezing a growing category list. Normally inset the content within window margins. Conventional pane-style tabs belong to macOS; evaluate segmented controls on iOS/iPadOS, appropriate navigation elsewhere, and page behavior for watch SwiftUI tab views. Do not equate every `TabView` API with the Mac component.

Implement the pane switch, produce a pane/control ownership specification, or review specific category/scope defects. Preserve the intended state of each pane when changing views, documenting that application choice rather than assuming automatic persistence.

**Worked transformation:** Before: a Mac audio inspector has nine tabs and a gain control in “Metadata” that unexpectedly changes “Mix.” Decision: choice count and cross-pane scope obscure the model. After: group related inspector content into fewer coherent panes or a view-choice pop-up, and place gain with the mix controls it affects.

Deliver the artifact, labels, ownership, and switching/state policy. Verify every choice is reachable, labels fit localization, and controls affect only their documented scope. Fail for hidden user-driven navigation, misclassified app destinations, or effects in an unrelated pane. Report native page/Crown behavior only when exercised.

Use [tab-bars](../../../apple-hig-navigation-and-search/.topics/apple-hig-tab-bars/SKILL.md) for top-level navigation or [segmented-controls](../../../apple-hig-selection-and-input/.topics/apple-hig-segmented-controls/SKILL.md) for a supported related-view switch.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.