Skills hig-inputs

📦

hig-inputs

Name: hig-inputs
Author: sickn33

Content revision r2 Safe ⚙️ External commands🌐 Network access

Design Better Apple Input Experiences

Apple applications must support different input methods without breaking platform conventions or accessibility. This skill produces focused recommendations based on Apple Human Interface Guidelines.

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

Test it

Using "hig-inputs". Review zoom controls for an iPad drawing application that supports touch, trackpad, and Apple Pencil.

Expected outcome:

Use pinch to zoom with touch and trackpad.
Keep Pencil input dedicated to drawing unless the user selects another tool.
Provide visible zoom controls and keyboard shortcuts as alternatives.
Preserve the zoom focal point and show immediate visual feedback.

Using "hig-inputs". Recommend navigation inputs for a media application on tvOS and visionOS.

Expected outcome:

Use predictable focus movement and a clear focus indicator on both platforms.
Support the Siri Remote clickpad and Back button conventions on tvOS.
Use look and pinch with generous targets on visionOS.
Avoid sustained gaze activation and provide an alternate way to complete every task.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 64 static findings are false positives caused by Markdown paths, documentation links, screenshots, and Apple HIG terminology. The skill contains design guidance only; no command execution, upload behavior, reconnaissance, exfiltration, or prompt injection was found.

Files scanned

1,789

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (1)

SKILL.md:11

🌐 Network access (1)

SKILL.md:107

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

HTML badge

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

Embed card

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

BibTeX citation

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

Map touch, keyboard, pointer, Pencil, and controller support across an Apple application.

Review Interaction Specifications

Check gestures, focus behavior, shortcuts, and feedback before implementation.

Audit Accessible Alternatives

Identify tasks that require alternate controls for different devices, abilities, or interaction modes.

Try These Prompts

Review One Interaction

Review this interaction for [platform]: [interaction]. Recommend the expected input behavior, feedback, and one accessible alternative.

Compare Platform Inputs

Compare input requirements for [feature] on [platforms]. Cover primary inputs, keyboard or pointer support, feedback, and platform-specific constraints.

Create an Input Specification

Create an input specification for [product flow]. Include platform recommendations, a gesture table, keyboard shortcuts, focus behavior, and accessibility alternatives.

Audit a Complex Input System

Audit this input design: [design details]. Find convention conflicts, inaccessible dependencies, destructive actions, discoverability gaps, and device-specific failures. Prioritize fixes by user impact.

Best Practices

State the target platforms, supported devices, and primary user tasks.
Describe custom gestures and destructive actions so the review can assess discoverability and recovery.
Validate recommendations on physical devices with keyboard, pointer, and assistive technologies.

Avoid

Do not request one universal interaction model without identifying platform differences.
Do not make custom gestures the only way to complete an essential task.
Do not treat guidance as proof that an interaction works on every device or accessibility configuration.