apple-design-principles

Apply Apple’s Human Interface Guidelines design principles to product concepts, design tradeoffs, or interface critiques for Apple platforms. Use for reasoning about experience quality rather than det

SKILL.md

GitHub

Apple Design Principles

Apply the skill

Identify the person, task, context, and intended feeling before evaluating the interface. Read the principles reference and choose the principles that explain the actual decision; do not force an eight-part report onto every request.

For competing proposals, state what each improves, what it costs, and which tradeoff best serves the product’s purpose. Tie every critique to an observable behavior or a concrete revision. Preserve the product’s identity and the user’s requested scope. A design recommendation does not authorize redesigning unrelated flows.

When producing a concept, show how the proposed interaction resolves the decision. When reviewing, lead with consequential problems and actionable changes; distinguish observed failures from questions that need user testing.

Topic references

Select the topic that matches the design decision; do not load this entire list by default.

Source use

These references are original operational summaries of Apple’s public HIG, checked on 2026-09-08. They are guidance for design decisions, not a reproduced manual or a guarantee of App Store acceptance.

Read only the topic references relevant to the current task. Each links to the full official page. Consult that page for exact specifications, platform exceptions, assets, and version-sensitive behavior; use current official developer documentation for APIs and availability. If live documentation is unavailable, state the snapshot date and identify assumptions instead of inventing current requirements.

The user’s product goals, selected framework, and authorized scope remain controlling. Distinguish a source recommendation from a hard platform requirement and from your own proposed implementation.