designer-app-flow (Claude Code plugin)Partly tested🌏 World

caiman, a visual designer who doesn't code, used Claude Code to get an iOS app approved on the App Store in 11 days, then open-sourced the six-agent workflow as a plugin

caiman (@caiman__) is a brand and motion designer who doesn't write Swift. With Claude Code he built BeanDance, a native iOS app that remembers the grind size for each bag of coffee: 11 days from new project to first approval, 5 releases and 21 TestFlight builds in a month, live in 175 storefronts including mainland China, with 320 rule tests. He says the hard part wasn't code but three questions: who decides, how to know it's right, and how to ship. So he set rules: every screen starts as 2–3 directions on a canvas and code is written only after he picks one; decisions go into docs, and thinking out loud in chat doesn't count; the agent that writes code doesn't approve its own work, because a read-only review agent and a black-box tester that only taps through the simulator check it; uploading, submitting and releasing are triggered only by him. He packaged the roles, doc templates and 150+ lessons as the Claude Code plugin designer-app-flow. We cloned it and ran its init script in an empty folder: the 6 agents and 3 skills were renamed for the new app, and the script listed the placeholders still to fill (Team ID, Bundle ID and so on). We did not build an iOS app or go through App Store submission.

Visit site designer-app-flow (Claude Code plugin) ↗
Pricing
Free
Region
Global
Where it's from
Overseas
Added
Nov 12, 2026
Tested on
Nov 12, 2026
Version we used
designer-app-flow git 22193ac (template/scripts/init-starter.sh)
Categories
CodingDesign
Original author
caiman @caiman__ ↗
Our test
Partly tested
Cost / time
The plugin is MIT and free. You need a Claude plan, a Mac that runs Xcode, and an Apple Developer account to publish (annual fee at Apple's current price). asc is a third-party open-source tool (MIT).
Source
X @caiman__ ↗GitHub caiman001/designer-app-flow ↗

The task

Let someone who can't code use Claude Code to build a native iOS app that reaches the App Store, while avoiding fast-but-wrong code, agents approving their own work, and releases nobody approved.

Steps

  1. In Claude Code, add the marketplace and install: /plugin marketplace add caiman001/designer-app-flow, then /plugin install designer-app-flow@designer-app-flow.
  2. Open Claude Code in an empty folder and run /designer-app-flow:new "App Name" shortname. It lays out the template, renames agents to <shortname>-product, <shortname>-qa and so on, and the release command becomes /<shortname>-release.
  3. Fill the placeholders it lists: Team ID, Bundle ID, default branch, website, minimum OS version and so on.
  4. Day to day you only talk to the main session: the product agent proposes 2–3 directions, writes code after you pick one and self-tests; the review agent (reads code) and the tester (only taps through the simulator) check in parallel and send it back if it fails.
  5. For TestFlight, you type /<shortname>-release yourself; screenshots and submission go through asc, a third-party open-source App Store Connect CLI that is read-only by default, with every write previewed and run only after you confirm.
  6. After launch, the feedback agent gathers reviews, the marketing agent plans posts and the archivist records the process; new ideas go to "open" and only what you confirm enters the decision log.

What the author says

caiman @caiman__ (X article, 11 Nov 2026): BeanDance took 11 days from new project to first approval; 5 releases and 21 TestFlight builds in a month; 175 storefronts including mainland China (the README says via Apple's ICP filing exemption); 320 rule tests and 20+ UI test suites; 150+ lessons, each one line of symptom and one line of fix. He stresses the point isn't "AI built an app for me" but judgment on every decision; once the AI treated his "maybe we could do this" as final, wrote it into the decisions and handed it to another agent, which led to the rule that ideas under discussion aren't decisions.

Our test

On 12 Nov 2026 on Linux we git-cloned https://github.com/caiman001/designer-app-flow (22193ac, MIT). Both .claude-plugin/plugin.json and marketplace.json are named designer-app-flow; skills/new/SKILL.md is the entry for /designer-app-flow:new. We copied template/ to a temp folder and ran sh scripts/init-starter.sh "Bean Test" beantest: the 6 agents became beantest-archivist, -feedback, -marketing, -product, -qa and -review, and the 3 skills beantest-promo, -release and -verify-ios; the {App名}/{app} placeholders were all replaced (only the script itself still mentions them); the script listed the placeholders left to fill, such as {Team ID}, {UDID}, {默认分支} (default branch), {网站地址} (website) and {最低版本} (minimum version). template/LESSONS.md has 200 lines, 169 of them list items. We did not install the plugin in Claude Code, build with Xcode or touch App Store Connect.

What we found when we tried it:The template and init script match the README: one command gives you 6 agents, 3 skills and the full doc set named for your app; what's left to fill by hand is Apple account and repo details.

How to get in

Public X article and GitHub repo with an English README.

Who it suits

Designers and others with a clear product idea who can't code, and indie developers who want roles, review and release gates around AI coding. Not useful without a Mac or for web-only apps.

Pitfalls

  • The workflow is written around native iOS (SwiftUI, Xcode, App Store Connect); Android or web projects need template changes.
  • After init, more than a dozen placeholders still need filling; the release skill fails without them.
  • When the coding agent checks its own work, problems reach the phone, which is why he added separate review and tester roles; dropping them removes most of the value.
  • We only ran the init script on Linux and inspected the files; we did not build an app, test on a device or verify the store numbers.

More in this category