Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

duo-design-review

Reviews screenshots, simulator captures and Figma frames for iPhone Duo, Apple's foldable, against a 15-point checklist (letterboxing, state lost on fold and unfold, sizing from UIScreen.main, text or buttons in the fold via reservedRegions .division and .occlusion, odd grid columns, vertical toolbars with symbols and titles, tabletop and book layouts with ArrangementView overlay, camera preview rotation, outer display feature parity, multiple windows with UIWindowScene.ActivationAction, transitions, 44 pt touch targets, hardware keyboard, drag and drop) and writes findings with severity, rule, where and fix. Use it when someone asks to critique, audit or review a design, mockup, concept or Dribbble shot for the foldable, the outer display or the inner display, or asks what breaks when the phone is closed, open, partly folded like a book, propped on a table, in Split View or under Picture in Picture.

Kimeur · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add Kimeur/duology --skill duo-design-review

About this skill


name: duo-design-review description: Reviews screenshots, simulator captures and Figma frames for iPhone Duo, Apple's foldable, against a 15-point checklist (letterboxing, state lost on fold and unfold, sizing from UIScreen.main, text or buttons in the fold via reservedRegions .division and .occlusion, odd grid columns, vertical toolbars with symbols and titles, tabletop and book layouts with ArrangementView overlay, camera preview rotation, outer display feature parity, multiple windows with UIWindowScene.ActivationAction, transitions, 44 pt touch targets, hardware keyboard, drag and drop) and writes findings with severity, rule, where and fix. Use it when someone asks to critique, audit or review a design, mockup, concept or Dribbble shot for the foldable, the outer display or the inner display, or asks what breaks when the phone is closed, open, partly folded like a book, propped on a table, in Split View or under Picture in Picture. metadata: verified: "Xcode 27.1 (27A9275), iOS 27.1 simulator, device: no" sources: "https://github.com/Kimeur/duology/blob/main/reference/sources.md"

Duo design review

Use this skill to critique pictures of an app on iPhone Duo: PNG screenshots, simulator captures, screen recordings or Figma frames. You compare what you see against 15 rules and write a report. Each finding names its severity, the rule, where it is and how to fix it.

This skill reviews what people see. To review code, load duo-lint and duo-layout. To fix what the review finds, load the skill each rule points to.

Step 1: Collect the review set

A Duo app runs in many shapes. One frame per screen is not enough. Ask for these, per screen under review:

FrameWhy
Closed, portrait (outer display)The main compact layout; bars on the trailing side
Closed, landscapeShort and wide; bars still on the side, more overflow
Open, flat, held wide (inner display)Regular width; vertical bars on the side
Open, flat, held tallInner portrait keeps horizontal bars
Partly folded like a book (held wide)The fold runs top to bottom through the middle
Propped on a table like a laptop (held tall)The fold runs side to side; top to look at, bottom to touch
Split View, left and right half50/50 on the inner display; bars on the app's outer edge
Under a pinned Picture in Picture videoThe app gets a shorter window
Closed then open (and back), same momentShows whether state survives
A recording of fold and unfoldShows the transition

Camera apps also need: the capture screen closed, open, and open turned around (a rear camera faces the person).

If a frame is missing, don't guess. Mark the rules it would prove as Check and list the frame in the report. "Book" and "tabletop" are Duology's shorthand. Apple only describes these ways of holding the phone, as "partially folded, like a book" or "seated on a table like a laptop" (HIG, Device poses, talk 111466). The SDK has no posture API (API index).

Tell the frames apart

Pixel sizeDisplayPoints (÷ 3)
1398 × 2034Outer, portrait466 × 678 pt
2034 × 1398Outer, landscape678 × 466 pt
2853 × 2007Inner, held wide951 × 669 pt
2007 × 2853Inner, held tall669 × 951 pt

These are Apple's App Store screenshot sizes and the simulator's own sizes (screenshot specifications). Both displays render at scale 3. A frame of any other size is a mockup: ask which display it stands for. A screenshot of the display that is off comes out black.

Capture from the simulator

The iPhone Duo simulator needs Xcode 27.1. Poses change in Device Hub: the Closed, Partially Open and Open buttons under the bezel, or Option-drag on the slider for any angle (Device Hub). simctl has no pose command (we checked in Xcode 27.1). Ask the person to set each pose, then capture both displays. With their Accessibility permission, duo-pose-matrix (/duo-poses) presses the pose buttons and saves every frame for you. Use the Duo's UDID, because booted is ambiguous when several simulators run:

export DEVELOPER_DIR=/Applications/Xcode-27.1.app/Contents/Developer
xcrun simctl list devices booted                       # find the iPhone Duo's UDID
xcrun simctl io <UDID> screenshot --display=primary   outer.png   # outer display
xcrun simctl io <UDID> screenshot --display=primary-1 inner.png   # inner display
xcrun simctl io <UDID> recordVideo --display=primary-1 --force fold.mov   # stop with Ctrl-C

If you can change the app, add this debug overlay to its root view. It tints the fold red and the camera regions blue, so every screenshot shows where they are. Stronger tint means the region is active. We ran it on the iPhone Duo simulator (iOS 27.1): closed, it drew the outer camera and the top of the trailing status bar column, and no fold.

import SwiftUI

/// Debug only. Tints the fold (red) and camera regions (blue) so a simulator
/// screenshot shows where they are. Stronger tint = active region.
@available(iOS 27.1, *)
struct ReservedRegionOverlay: ViewModifier {
    func body(content: Content) -> some View {
        content.overlay {
            GeometryReader { proxy in
                let folds = proxy.reservedRegions(kind: .division, options: .includeInactive)
                let cameras = proxy.reservedRegions(kind: .occlusion, options: .includeInactive)
           
Read the complete source ↗