duo-craft

duo-craft

iPhone Duo is an iPhone to every API that names a device, so a React Native app runs on it unchanged and looks wrong in ways no simulator other than the Duo shows. The bars stand down the trailing edge and take 84pt off one side only. The open display is 951×669pt with a fold at 475.5pt, so a phone column stretched across it puts a card over the hinge. Split View hands the app a half whose side bar is on the left. And an Expo SDK 57 app built with the iOS 27 SDK does not reach its first screen at all.

This skill turns that into code. It carries a native fold module that has run on the Duo simulator in a shipping app, the layout components built on it, a static audit that finds the assumptions that break, and a starter that a fresh create-expo-app becomes in one command. React Native has no fold API of its own, and no third-party fold library has the adoption to depend on (references/libraries.md), so the module ships here as source the app owns.

Deliver what was asked, at the scope intended. Adapting one screen means that screen and the shared pieces it needs, not every screen in the app; a new app means the starter plus what the user described; a crash fix is the fix, why it works and, when the user asks for it to stay fixed, the bundled scripts/check-scene-lifecycle.mjs, which install_templates.py adds and runs before the ios script. It fails when the opt-in leaves app.json, when expo drops below 57.0.23, and when a generated ios/ still starts its own window, the half-fix that launches to a black screen. Say in one sentence where a wider change would help, then build what was asked.

Write the report for someone who has the app and not this skill: cite the app's files and Apple's or Expo's documentation, never this skill's references or this machine's paths, and leave out findings about parts of the app the task did not touch.

When the request is a question rather than a change — "should I use this library", "why does it crash" — answer it in 25 lines or fewer: the answer first, the reason, and what to do instead. Claim only what the evidence supports: a library's source read is a source read, not a test on a real device, so say "its fold path is compiled out unless you set the flag", not "it reports no fold on a real Duo". Recommend the bundled module by what it is and how to install it, since the reader may not have this skill. Answer only the question asked. Leave out other libraries, other Duo problems and the launch crash unless the user asked about them; the user asked one thing, and an answer padded with neighbouring advice reads as not having listened. The procedure below is for changing an app, not for answering a question.