DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to keep game touch controls clear of the fold with Iphone Duo Skills

Check a game's screen filling, aspect ratio and on-screen controls against iPhone Duo poses.

Who it is forA game developer using Unity, Unreal, Godot, SpriteKit or Metal who has on-screen touch controls and needs them usable on iPhone Duo.

The problemGames sidestep most UI guidance but still need to resize, and the fold is a real hazard for touch controls placed across it.

The outcomeA list of changes to screen filling, letterboxing and touch control placement so controls sit clear of the fold in each pose.

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

  1. Run npx skills add mirzaaghazadeh/iphone-duo-skills --skill iphone-duo-games (inferred, check the README)
  2. Restart your agent session.
  3. Point the agent at your project's input and UI scene setup.
  4. Ask for a check of screen fill, aspect ratio and letterboxing per pose.
  5. Move any touch control that sits across the fold and test it on a physical device.

Prompt for your agent

Using the iphone-duo-games skill from mirzaaghazadeh/iphone-duo-skills, review <path-to-game-project> for how the game fills the screen across poses, handles aspect ratio and letterboxing, and places on-screen touch controls. Output the changes needed, and verify that no touch control is placed across the fold in any listed pose.

Caveat. The README does not give exact fold dimensions in this entry, so pick control positions using the device facts reference and test on hardware.

Share: 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