# Design Apple Technology Experiences

Apple technology integrations can become inconsistent, inaccessible, or unclear. This skill turns Apple HIG references into implementation, privacy, flow, and testing guidance.

## Install

```bash
npx skillstore add sickn33/hig-technologies
```

## Metadata

- Status: approved
- Slug: sickn33-hig-technologies
- Skillstore revision: r2
- Version status: missing
- Tree hash: 51b50add24bbb2f32f8226c2d85065a87eb51e8406937599f38107b80614b7a4
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/hig-technologies
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, env\_access, external\_commands
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/sickn33-hig-technologies
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-hig-technologies/manifest

## Capabilities

- Selects focused guidance for Siri, payments, health, HomeKit, augmented reality, machine learning, and other Apple technologies.
- Produces step-by-step implementation checklists grounded in the included Apple HIG references.
- Separates required considerations from optional enhancements for the requested integration.
- Maps privacy, permission, and data handling needs across sensitive Apple technologies.
- Describes user flows from permission or setup through completion and error recovery.
- Suggests tests for accessibility, edge cases, device capabilities, connectivity, and platform behavior.

## Use Cases

- Plan a Siri Integration: Turn a voice use case into intent, phrasing, confirmation, fallback, and testing recommendations.
- Review a Payment Flow: Assess Apple Pay or Tap to Pay screens for clarity, standard controls, recovery, and privacy.
- Audit a Sensitive Feature: Review health, identity, smart home, or machine learning experiences for permission, trust, accessibility, and control.

## Prompt Templates

### Find Relevant Guidance

```
I am adding [Apple technology] to [app type] on [platform]. Identify the relevant HIG principles and create a short checklist.
```

### Design the User Flow

```
Design the user flow for [feature] using [Apple technology]. Cover setup, permissions, main action, confirmation, errors, and accessibility.
```

### Review an Existing Specification

```
Review this feature specification for [Apple technology]: [specification]. Separate required corrections, optional improvements, privacy concerns, and testing gaps.
```

### Create a Cross-Technology Audit

```
Audit [product] across [technology list] for HIG consistency. Resolve conflicts and prioritize risks by user impact, privacy, accessibility, and implementation effort.
```

## Limitations

- Provides design guidance, not current API documentation, entitlement approval, or App Store review decisions.
- Does not validate compiled applications, runtime behavior, accessibility trees, or platform availability.
- Reference content can become outdated when Apple changes its guidelines or frameworks.
- Needs product context, target platforms, permissions, and an intended technology for tailored recommendations.

## Best Practices

- Provide the Apple technology, target platforms, core task, required data, and known entitlements.
- Share existing product context and constraints before requesting detailed recommendations.
- Verify recommendations against current Apple documentation and test them on supported devices.

## Anti Patterns

- Do not request a generic HIG review without naming the feature, platform, or user goal.
- Do not treat design guidance as proof that an entitlement or App Store submission will be approved.
- Do not omit privacy, permission, accessibility, failure, or recovery behavior from implementation planning.

## Security Audit

- Audited at: 2026-07-23T23:59:07.117\+00:00
- Summary: All 170 static findings are false positives caused by Markdown prose, image descriptions, inline-code formatting, or documentation links. The reviewed files contain no executable scripts, operational network requests, environment-variable access, reconnaissance, or prompt injection evidence. No semantic security findings were identified.

## Stats

- Views: 107
- Downloads: 8
- Favorites: 0
- Popularity score: 0