Skills hig-patterns

📦

hig-patterns

Name: hig-patterns
Author: sickn33

Content revision r2 Safe ⚙️ External commands🌐 Network access

Design Apple Experiences with HIG Patterns

Apple interaction decisions can become inconsistent across flows and platforms. This skill recommends HIG-aligned patterns, implementation steps, platform variations, and common pitfalls.

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-patterns" from https://skillstore.io/skills/sickn33-hig-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-hig-patterns/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-patterns.md Signed manifest GET /api/skills/sickn33-hig-patterns/manifest Signed lockfile GET /api/skills/sickn33-hig-patterns/lockfile

Test it

Using "hig-patterns". Recommend an onboarding pattern for an iPhone budgeting app that needs notification permission.

Expected outcome:

Start with the primary budgeting task and defer permission requests. Ask for notifications when alerts become relevant, explain the value, and provide a skip path.

Using "hig-patterns". Review a permanent delete action that uses a confirmation alert.

Expected outcome:

Prefer immediate deletion with a visible undo action when recovery is feasible. Keep confirmation for irreversible loss, then state the consequence and destructive action clearly.

Using "hig-patterns". Adapt a video playback flow for tvOS and visionOS.

Expected outcome:

Use familiar playback controls and preserve continuity on tvOS. In visionOS, let people enter immersion and keep transport controls visible and unobstructed.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 99 static findings are false positives. The flagged passages are Apple interface-design prose, Markdown media descriptions, a local context filename, and attribution links without executable or exfiltration behavior.

Files scanned

2,575

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (1)

SKILL.md:11

🌐 Network access (1)

SKILL.md:96

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-patterns/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-patterns/security.svg)](https://skillstore.io/skills/sickn33-hig-patterns?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-hig-patterns.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-patterns security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-hig-patterns/audits/5

BibTeX citation

@techreport{sickn33-sickn33-hig-patterns-2026,
  author = {sickn33},
  title = {hig-patterns security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-hig-patterns/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-patterns 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-patterns/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-hig-patterns: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

Plan a New Interaction

Select suitable patterns and define screens, states, feedback, and recovery before visual design begins.

Prepare an Implementation

Translate a feature flow into platform-aware interaction requirements and edge cases for engineering.

Review an Existing Flow

Compare onboarding, settings, media, or account flows with HIG guidance and prioritize corrections.

Try These Prompts

Choose a Pattern

Recommend an Apple HIG pattern for [user goal] on [platform]. Explain the rationale and list the core screens or states.

Improve a Flow

Review this [flow] for [platform]: [description]. Identify HIG issues and recommend changes for feedback, loading, recovery, and user control.

Adapt Across Platforms

Adapt [interaction] for [Apple platforms]. Detail differences in modality, input, layout, interruptions, and system behavior.

Write an Interaction Specification

Create an implementation-ready interaction specification for [feature] across [platforms]. Include state transitions, edge cases, permissions, undo, accessibility considerations, and reference topics.

Best Practices

Provide the target platform, user goal, preceding state, and following state.
Describe destructive actions, permissions, payments, and other sensitive moments explicitly.
Validate recommendations against current Apple documentation and test them with representative users.

Avoid

Do not request generic HIG advice without describing the feature or workflow.
Do not apply one platform interaction unchanged across every Apple device.
Do not treat guideline recommendations as proof of accessibility or App Review approval.