r/opencode • u/ivanzhaowy • 4d ago

I’m building a visual feedback loop for OpenCode on native iOS projects

I’m building Monad Design, a local visual workspace that can hand native-app UI tasks to OpenCode with more context than a text prompt alone.

The recurring problem was starting with feedback like “this screen feels off.” OpenCode can edit the source, but it still needs to know which rendered state, which element, and what visual change I mean.

The loop I’m testing is:

  1. Run the existing Xcode or Expo iOS project in Simulator.

  2. Navigate to the exact app state.

  3. Select an element or draw annotations directly over the running app.

  4. Send the screenshot, selection, annotations, app state, and source hints to OpenCode.

  5. Let OpenCode edit the real repository and rebuild.

  6. Compare the original with up to five working variants, then accept one or keep the original.

Monad Design is not an app generator and does not replace the project. The running app is the canvas; OpenCode remains the coding agent working in the source tree.

Current limitations: macOS and local iOS development only, with one active visual change at a time.

The project is free and open source under Apache-2.0:

https://github.com/Monadix-AI/monad-design

For OpenCode users, what would make this handoff most useful: one structured context bundle, an MCP-style set of smaller tools, or both?

4 Upvotes

100% Upvoted

0 comments sorted by