When I use a coding agent on an Expo app, the slow part is often describing what I’m looking at: “the second card, in this state, after opening that sheet.” A screenshot helps, but the agent still has to guess which part of the project it belongs to.
I’m building Monad Design around a simpler idea: the app is the canvas.
It opens an existing Expo iOS project, connects to the running Simulator, and lets me select or annotate the UI in the exact state I care about. That context goes to the coding agent I already use. The agent edits the real repository, the app rebuilds, and I can compare the original with a few working variants before keeping one.
The useful part for me is that it doesn’t generate a separate prototype. The result stays in the Expo project, so there’s no design-to-code handoff afterward.
Current scope is local iOS development on macOS. It’s open source and works alongside Codex, Claude Code, or Cursor.
Repo:
I’m the creator. Happy to explain the Expo integration or any of the tradeoffs behind it.
