Skills hig-components-layout

📦

hig-components-layout

Name: hig-components-layout
Author: sickn33

Content revision r2 Safe ⚙️ External commands🌐 Network access

Design Adaptive Apple Layouts and Navigation

Choosing Apple navigation structures across devices is complex. This skill maps information architecture to HIG-aligned components and responsive platform behavior.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "hig-components-layout" from https://skillstore.io/skills/sickn33-hig-components-layout.md and its manifest at https://skillstore.io/api/skills/sickn33-hig-components-layout/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-hig-components-layout.md Signed manifest GET /api/skills/sickn33-hig-components-layout/manifest Signed lockfile GET /api/skills/sickn33-hig-components-layout/lockfile

Test it

Using "hig-components-layout". A five-section iPhone app where every section contains lists and detail pages.

Expected outcome:

Use a bottom tab bar for the five peer sections.
Place a navigation stack inside each section for list-to-detail movement.
Preserve each tab's navigation state when users switch sections.

Using "hig-components-layout". An iPad document manager with folders, files, previews, and multitasking support.

Expected outcome:

Use a three-column split view for folders, files, and previews.
Collapse to a navigation stack at compact widths.
Test every supported Split View ratio and orientation.

Using "hig-components-layout". A visionOS media app with persistent playback controls.

Expected outcome:

Use a window for primary content and an ornament for playback controls.
Keep the ornament visible without covering important content.
Maintain predictable placement across window sizes.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 36 static findings are false positives caused by ordinary HIG prose, Markdown code spans, and attribution links. No command execution, system reconnaissance, prompt injection, or data-exfiltration intent was found.

Files scanned

1,270

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (2)

SKILL.md:11 SKILL.md:52

🌐 Network access (1)

SKILL.md:92

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-hig-components-layout/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-hig-components-layout/security.svg)](https://skillstore.io/skills/sickn33-hig-components-layout?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-hig-components-layout?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-hig-components-layout/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-hig-components-layout.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). hig-components-layout security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-hig-components-layout/audits/5

BibTeX citation

@techreport{sickn33-sickn33-hig-components-layout-2026,
  author = {sickn33},
  title = {hig-components-layout security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-hig-components-layout/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "hig-components-layout security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-hig-components-layout/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-hig-components-layout:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Choose Mobile Navigation

Select a clear navigation model for an iPhone app with several peer sections and deeper detail screens.

Adapt an iPad Interface

Plan sidebar and split-view behavior across full screen, Split View, Slide Over, and orientation changes.

Align Multiple Apple Platforms

Define consistent navigation while respecting window, panel, and ornament conventions on Mac and visionOS.

Try These Prompts

Select a Navigation Pattern

Recommend a navigation pattern for [app type] with [number] top-level sections on [platform]. Explain the choice and basic hierarchy.

Plan Adaptive Behavior

Design the layout for [app] on iPhone and iPad. Describe compact and regular widths, orientation changes, and multitasking behavior.

Audit an Existing Layout

Review this navigation structure: [description]. Identify HIG conflicts, accessibility risks, unclear hierarchy, and platform-specific improvements. Prioritize the changes.

Create a Cross-Platform Specification

Create a navigation specification for [app] across iPhone, iPad, Mac, and visionOS. Include hierarchy, component choices, transitions, restoration, and validation cases.

Best Practices

Describe the information hierarchy, section count, target platforms, and implementation framework before requesting recommendations.
Validate every recommendation at compact and regular widths, including iPad multitasking states.
Test navigation order, labels, focus, and Dynamic Type with relevant accessibility tools.

Avoid

Do not choose a component only because it matches another platform's visual appearance.
Do not nest same-direction scroll views or hide critical actions in unstable locations.
Do not assume an iPad layout can shrink directly into an iPhone layout.