iPhone Duo Skills
Eleven skills teach an agent to adapt apps to the foldable iPhone Duo: layout, hinge, cameras, games and cross-platform stacks.
- 318 ★ on the repository
- Last commit
Minimal access
Why this level
- The skills contain only instructions and reference material and run nothing themselves.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/iphone-duo-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills contain only instructions and reference material and run nothing themselves.
This is third-party code. Review the repository files before installing.
What it does
iPhone Duo Skills distils Apple's material on the foldable iPhone Duo into structured instructions for an agent. The base is six Tech Talk videos, a Human Interface Guidelines page, a preparation checklist and an API reference. The last two arrived after the project started and are already reflected, and the API reference corrected three claims recorded earlier. The entry skill `iphone-duo-readiness` audits or ports an existing app and routes to the rest. Separate skills cover adaptive layout and reserved regions, vertical bars, hinge and scenes, cameras, dual-pane patterns and design review. There are variants for games on Unity, Unreal, Godot, SpriteKit and Metal, and for Flutter, React Native and Capacitor. The references hold device facts, an API index and a source list.
Who it is for. iOS developers and teams on Flutter, React Native or Capacitor who prepare an app for the foldable iPhone Duo.
Good fit when
- An existing app is audited for fixed assumptions about screen width and insets.
- Content lands in the fold and you need to know which regions to reserve.
- A capture app has to deal with two front cameras.
- A game must fill the screen in different poses with no touches in the fold area.
Not a fit when
- The app targets regular iPhones only with no foldable plans.
- You need working code for an API missing in your SDK version: the skills give guidance and reference.
- You expect Flutter or React Native to support the foldable iPhone already without a bridge.
Example request
Audit my SwiftUI app for assumptions that will break on the foldable iPhone Duo and write a prioritised list of fixes.Limitations
The skills describe the device and APIs from Apple's public material and diverge from it if Apple updates the reference. For Flutter and React Native the README states plainly that foldable iPhone support is not there yet: `MediaQuery.displayFeatures` in Flutter is populated only on Android and React Native has no fold API, so a native bridge is needed. The project is not affiliated with or endorsed by Apple. The repository metadata does not define a licence. The last commit dates from November 2026.
How to disable. Delete the installed `iphone-duo-*` skill folders from the agent's skills directory, for example `~/.claude/skills/`. Clean the project `.claude/skills/` directory the same way.
FAQ
How do I install all skills at once?
`npx skills add mirzaaghazadeh/iphone-duo-skills` installs all eleven and puts them where the agent looks. One skill is chosen with `--skill`.
Which skill should I start with?
With `iphone-duo-readiness`: it audits the app and routes to the other skills for your stack.
Can I try a skill without installing?
Yes, `npx skills use mirzaaghazadeh/iphone-duo-skills@iphone-duo-readiness` runs a skill without a permanent install.
Are there cross-platform skills?
Yes: `iphone-duo-flutter`, `iphone-duo-react-native` and `iphone-duo-capacitor`. Kotlin Multiplatform and .NET MAUI have no dedicated skill, and the neighbouring pattern carries over.
What is in the references?
The `reference/` folder has three files: device facts (displays, dimensions, cameras, poses), an API index by task and a source list.
Discussion
No questions or reviews yet.
Related
SkillsTwo SwiftUI skills: native Liquid Glass for iOS 26 and adaptive layout for the foldable iPhone Duo with no separate app version
Skills for Apple development: SwiftUI, UIKit and Liquid Glass references, Swift 6 guides and a router for iOS 26+ tasks
A set of skills for iOS 26+, Swift 6.3 and SwiftUI that gives the agent knowledge of modern Apple frameworks
A skill that gives the agent Apple's own SwiftUI guidance, which the installer extracts from your local Xcode
157 condensed Apple HIG references for an agent and a /duo command that adapts an existing iOS app to the folding iPhone
A skill with scripts for building iOS apps and driving the simulator through the accessibility tree, with compact output for agents
README in short
Skills are self-contained, each with its own `SKILL.md` carrying a YAML header, and work anywhere Markdown instructions are read. The developer takeaway: an app should no longer assume a fixed width, orientation or symmetric insets.
README badge
Original SKILL.md
--- name: iphone-duo-readiness description: Audit and port an iOS app to iPhone Duo, Apple's first foldable iPhone. Use when asked to support, adapt, prepare, test, or review an app for iPhone Duo, foldable iPhone, the inner/outer display, device poses, or the fold. Entry point that routes to the layout, bars, hinge/scenes, camera, and design skills. --- # Get an iOS app ready for iPhone Duo iPhone Duo is Apple's first foldable iPhone: a 5.4-inch outer display and a 7.6-inch inner display sharing one aspect ratio, joined by a hinge the user can leave at any angle. An existing iPhone app runs on it unchanged — but it will look like an app that has not been thought about. This skill is the entry point. Work the checklist, then hand off to the specialist skill for whatever the app actually does. ## The one idea to hold onto **iPhone Duo is not a new idiom. It is a wider continuum of sizes.** Every mistake in this port comes from an app asserting something fixed: this idiom, this orientation, this screen, this width, this symmetric inset. Every fix is the same shape — replace the assertion with a question about the space actually available right now. If you find yourself writing a branch that means "if iPhone Duo", stop. Write a branch on size class or available space instead, and it will be right on iPad, in Split View, under iPhone mirroring, and on whatever ships next. ## Step 1 — Establish the baseline Find out what the app is building against, because the SDK is the gate: | Built against | Behavior on iPhone Duo | |---|---| | iOS 26 SDK or earlier | Runs, but doesn't adapt. Open, the app sits **centered with empty space around it**. Closed, content shows to the left of the status bar and camera. | | iOS 27 SDK | Resizes to fill most of the inner display, but still avoids the status bar on the right edge. | | **iOS 27.1 SDK or later** | Extends to the full display, with toolbars and tab bars vertical below the status bar. Unlocks the reserved-region and arrangement APIs. | Check the deployment target and the SDK in the project, then say plainly which tier the app is in. Getting to the 27.1 tier is the single highest-leverage change; almost everything else in this skill assumes it. One caution before you ship at the 27.1 tier: that's the point where the bars go vertical, so confirm the content adapts to that before releasing. Jumping tiers without checking is how an app ends up with controls overlapping its own layout.