apple-design-ios
Skill1 starsChanged 52 days agoMITView on GitHub
Design, implement, or review iPhone interfaces using Apple’s iOS Human Interface Guidelines. Use for iOS screen structure, touch ergonomics, adaptive behavior including the foldable iPhone Duo, and integration with iPhone system experiences.
In this repository32 other files it gives its agents.
- grok-firstSkill
- opencode-firstSkill
- apple-design-accessibilitySkill
- apple-design-aiSkill
- apple-design-commerceSkill
- apple-design-connected-technologiesSkill
- apple-design-contentSkill
- apple-design-controlsSkill
- apple-design-foundationsSkill
- apple-design-gamesSkill
- apple-design-healthSkill
- apple-design-inputsSkill
- apple-design-mediaSkill
- apple-design-menusSkill
- apple-design-navigationSkill
- apple-design-patternsSkill
- apple-design-platformsSkill
- apple-design-presentationSkill
- apple-design-principlesSkill
- apple-design-privacy-identitySkill
- apple-design-spatialSkill
- apple-design-system-experiencesSkill
- design-maestroSkill
- forjaSkill
- product-studioSkill
- temperaSkill
- bambu-h2c-slice-printSkill
- bambu-print-troubleshootSkill
- blender-print-readySkill
- fdm-print-preflightSkill
- ads-videoSkill
- tutorial-videoSkill
The file
Files
Design for iOS
Apply the skill
Establish the primary task, supported iPhone configurations (including iPhone Duo, if the app runs on it), minimum iOS version, and existing framework. When an app or design artifact is provided, inspect it before proposing changes; for a new concept, work from the brief and state necessary assumptions. Preserve the chosen stack, including SwiftUI, UIKit, React Native, or another framework; translate native behavior into that stack instead of replacing it.
Model the main destinations, navigation state, and any scoped modal task before arranging controls. Specify what happens after Back, cancellation, backgrounding, an interrupted operation, and reentry through a deep link. Use the iOS reference for device-specific priorities.
For implementation work, use platform components where they satisfy the interaction and verify API availability against the target SDK. For visual design, annotate interaction states and adaptation instead of presenting a single idealized screenshot.
Read the implementation review reference when delivering screens or reviewing an existing flow. Inspect the relevant linked HIG component page before prescribing version-sensitive navigation, search, materials, sizes, or system integration. For companion iPad work, also read Designing for iPadOS and account for its windowing and input model.
Topic references
Select the topic that matches the design decision; do not load this entire list by default.
- Designing for iOS
- Implementation and review — for screen delivery, adaptation checks, and implementation review.
- Designing for iPhone Duo — for the two displays, device poses, the fold, and the vertical bar rail.
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

