Who it is forA product designer or product manager who wants feedback on a screen before engineering starts, in any framework.
The problemA layout that looks right on a flat screen can place controls or content across the fold or behave poorly in a different pose.
The outcomeA written design critique that covers poses, side controls, asymmetry, fold avoidance and sheets, with specific changes to try.
What you need first
- An AI coding agent such as Claude Code, Cursor or Gemini
- Node.js with npx, since the README install uses npx
- An existing app or design to work on, native iOS or a supported cross-platform stack
- For native work, Xcode with the iOS 27.1 SDK, which the README calls the gate for edge-to-edge content, vertical bars, reserved regions and arrangements
Steps
- Run
npx skills add mirzaaghazadeh/iphone-duo-skills --skill iphone-duo-design-review(inferred, check the README) - Restart your agent session.
- Give the agent the screen description, screenshots or mockup files.
- Ask for a critique organized by pose, side controls, asymmetry, fold avoidance and sheets.
- Take the top items back to the design file and mark which ones need an engineering check.
Prompt for your agent
Using the iphone-duo-design-review skill from mirzaaghazadeh/iphone-duo-skills, critique the screen described in <path-to-design-notes-or-image> for how it behaves across iPhone Duo poses, with attention to side controls, asymmetry, fold avoidance and sheets. Output a prioritized list of issues with one suggested change each, and verify that the critique does not assume a specific framework.
Caveat. The skill gives design guidance based on Apple's Designing for iPhone Duo page and Tech Talks, so check each suggestion against the current Human Interface Guidelines.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page