The Basic Flow

Whether you are building or changing an app, the flow is always the same. Start by learning who does what.

How a change reaches production

1. 1
   YouAsk Claude

   Say what you want in plain words. Copy a request from this guide and use it.

2. 2
   ClaudeClaude explains its plan

   Claude explains what it will change and how. Ask about anything unclear, and reply OK once you are satisfied.

3. 3
   ClaudeClaude builds it and shows you the screen

   Claude makes the change on a working copy (a branch) and opens the app on your own computer to show you. The data in it is made-up test data.

4. 4
   YouCheck the screen

   Try the change yourself on the screen Claude opened. If something needs fixing, tell Claude.

5. 5
   ClaudeClaude proposes the change

   Claude posts a proposal on GitHub that says: please take this change into production. That proposal is called a pull request (PR).

6. 6
   AutomaticAutomatic checks

   The change is inspected automatically. This takes a few minutes. If you want to check with real data or show someone else, this is when you can ask Claude for a preview.

7. 7
   YouMerge

   If everything looks right, press Merge pull request on GitHub. The change is taken into production.

8. 8
   AutomaticProduction is updated

   The production app is updated within a few minutes. Open it from the App Portal to confirm.

Why it works this way

Your colleagues use the production apps for their daily work. So a change never goes straight into production. It moves in this order:

• It is built on a working copy. Production is not affected. If it does not work out, the copy is simply thrown away.
• It is checked on your own computer. The screen Claude opens is separate from production. It holds made-up test data, and nothing you do there changes production data.
• It is checked in a preview only when needed. When you want to see it with real data, try whether things like email work, or show it to someone else, ask Claude for a preview (a trial environment). See Check the Screen.
• It reaches production only when merged. You decide whether to merge.

Which way to work

If you are unsure, start with Small Changes. When the work is too large for one request, Claude suggests splitting it.

How to ask well

• One thing at a time. Ask for "add a column to the list" and "change the color" separately. They are also easier to check that way.
• Be specific. "Make the text in the list larger and add space between rows" works better than "make it easier to read".
• Say where. Name the screen and the spot, such as "the button at the top right of the lost items list".
• Paste a picture. A screenshot pasted into Claude Code is more exact than words alone.
• Ask about words you do not know. Send "Please explain that again without technical terms" and Claude will rephrase.

When Claude asks for permission

Before changing files or running something, Claude may ask "May I run this?"

• If it is part of the flow in this guide, you can allow it. That includes editing files, checking that the app can be assembled correctly (the build), and creating a PR.
• If words such as "delete", "production", or "database" appear and you feel unsure, ask first: "What does this do? Does it affect production?"
• If you still cannot decide, do not allow it. Ask an administrator.

Quiz

Next step

For your first time, Small Changes is a good way to go through the whole flow once.