Skip to content
Back to skills

Apple Hig Path Controls

ASecurity

Use when creating, reviewing, or adapting a macOS filesystem path display or editable path selector.

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

Security analysis

A100/100

Scanned October 26, 2026

npx -y skills add AyushRajSinghParihar/apple-human-interface-skills --skill apple-hig-path-controls --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apple Hig Path Controls?

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

Security grade badge for Apple Hig Path Controls
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ayushrajsinghparihar-apple-hig-path-controls/badge)](https://www.skillsdirectory.com/skills/ayushrajsinghparihar-apple-hig-path-controls)

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-path-controls
description: Use when creating, reviewing, or adapting a macOS filesystem path display or editable path selector.
---

# Represent location without confusing selection

Read [the path-control guide](../../references/path-controls.md). The following is application advice; this component is macOS-only.

Inspect the actual file/folder location, display-versus-edit purpose, available width, platform, and create/review/adapt request. Determine whether activating a segment navigates or chooses a location and whether dropped items should change selection. Do not infer editable behavior merely from a displayed path.

Choose standard segments when visible ancestry matters; choose the pop-up form when compact display can reveal ancestry on demand. Place the control in the window body, not toolbar/status bar. In editable mode, accept supported dropped locations; a pop-up additionally needs Choose. Preserve the actual selected item's identity even when intermediate segment names hide under width pressure. Define what nonfolder or unavailable drops mean according to product requirements rather than implying arbitrary paths are valid.

Implement the control/location handling, provide a location/segment/drop specification, or review concrete ambiguity and placement defects. For another platform choose a supported navigation or file-location presentation; do not claim native path-control parity.

**Worked transformation:** Before: an export window shows a toolbar breadcrumb that appears editable but rejects drops and offers no chooser. Decision: location selection needs explicit editable behavior and body placement. After: use an editable body pop-up showing the selected folder, full hierarchy on opening, Choose, and valid folder-drop handling.

Deliver the artifact with displayed path, editability, navigation/selection, and validation contract. Verify root/deep paths, narrow width, selection by Choose/drop, and stale locations. Fail for displayed versus actual location disagreement, inaccessible hidden ancestry, or silent acceptance of an invalid destination. Native filesystem permissions and drag behavior need runtime evidence.

Load [file-management](../../../apple-hig-patterns/.topics/apple-hig-file-management/SKILL.md) for broader location/persistence work or [drag-and-drop](../../../apple-hig-patterns/.topics/apple-hig-drag-and-drop/SKILL.md) for transfer semantics.

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.