AI app designer: mobile screens, built and checked in the simulator

What an AI app designer does

It designs in the app's code, so what you review is what ships.

• Lays out new screens and polishes existing ones with your components.
• Follows iOS and Android conventions: navigation, safe areas, Dynamic Type and touch targets.
• Runs the app in the simulator or emulator and screenshots each change.
• Checks dark mode, small and large screens, and accessibility labels.
• Prepares App Store and Play Store screenshots.

Goals to give it

Give an AI employee one number to move, the way you would a new hire, and review it every week. Pick one of these to start.

Its daily routine

• Take the next screen from the board.
• Build or adjust it with the app's components.
• Run it in the simulator on a small and a large device, light and dark.
• Fix what looks off, then screenshot the result.
• Open a pull request with the screenshots.

How to set up an AI app designer with Claude Code or Codex

1. Write the role brief

   Save it as CLAUDE.md (Claude Code) or AGENTS.md (Codex) in the repository the employee works in, so every session starts with its job, goal and rules. See the CLAUDE.md guide.

   # Role: App UI designer
   Goal: 2 app screens a week.
   
   ## For every screen
   1. Build it with our components and platform conventions.
   2. Run it in the simulator: small and large device, light and dark.
   3. Check safe areas, Dynamic Type, touch targets and labels.
   4. Open a PR with simulator screenshots.
   
   ## Rules
   - Don't change navigation structure or onboarding without asking.
   - Don't submit builds to the App Store or Play Store.

2. Give it the tools it needs

   The app's repository, Xcode and the iOS Simulator or Android Studio and an emulator on the machine it runs on, a way to take screenshots, and your component library.

3. Decide what needs your yes

   Ask before changing navigation, onboarding or paywall screens, and never let it submit builds or edit store listings itself.

4. Put it on a schedule

   A role needs a rhythm, not a single prompt. Use /loop or scheduled tasks for one recurring prompt, or give it working hours, a heartbeat and a board of issues; see how to make Claude Code proactive.

Related guides

For the engineer who wires up the logic behind its screens, see the AI software engineer. For web interfaces, see the AI UI designer. For the skills to install, see the best Claude skills for mobile app design.

Hire an AI app designer instead of scripting one

Crewmark has an AI app designer ready to hire. It runs in your Claude Code, Codex, DeepSeek Harness or OpenCode session, on the subscription you already pay for, wakes on a heartbeat during working hours, takes the next issue from a shared board and messages you when it needs a decision.

1. Pick the role

   Its skills, goal and schedule come set up. Change the goal to your own number.

2. Connect your project

   Run the setup command in the repository or folder it works in. It gets its own session and checkout.

3. Review, don't babysit

   It comments on its issues as it works and asks before anything on your approval list. Read what an AI employee is.

AI app designer FAQ