Algoritmi AI SandboxPractice environment with sample data. Nothing here reaches the production platform.

Small Changes

How to make a change that takes one request, such as fixing wording or adding a field. You will use this the most.

When to use this

  • You want to change wording, colors, or the order of things on a screen
  • You want to add one input field or one column to a list
  • You want to fix one bug

For a feature that spans several screens, use Bigger Features.

Before you start

  • Make sure the algoritmi-sandbox-vibe-coding-platform folder is selected in Claude Code.
  • Start a new conversation. Asking for a different change in the same conversation as earlier work mixes the two changes together.
  • Decide which app, which screen, and what you want to change.

Step 1: Ask

Replace the parts in 【 】 below and send the request to Claude Code.

Ask for a small change
Claude prompt
/new-minor-feature I want to make the following change in 【app name】. What I want: 【Example: add an "Assigned to" column to the list screen】 I have no programming experience. Please work in this order. 1. First explain your plan, what you will change and how, without technical terms. Do not change any files until I say OK 2. If the plan needs a change to the database structure or to anything under shared/, say so in the plan 3. After I say OK, create a new branch from main, make the change, and confirm that the build passes 4. When it is ready, open the app locally and show me the screen that changed 5. After I check the screen and say OK, commit, create a pull request to main, and give me the PR URL

If you do not know the app name, write the name shown in the App Portal. Claude finds the matching app.

Step 2: Check the plan

Claude explains its plan. Check three things:

  • Does it match what you asked for?
  • Is it about to change something you did not ask for?
  • Are there still words you do not understand?

If it looks right, reply "OK". If something is off, say so right there.

When the plan is hard to follow
Claude prompt
Please explain that again without technical terms. Tell me which part of the screen changes and how.
If the plan includes a database change

Adding or changing a table, the container that holds data, can affect other apps. You can let the work continue, but have an administrator look at it before you merge.

Step 3: Wait while Claude builds it

Claude makes the change and checks the build. The build confirms that the app can be assembled correctly. Answer any questions or confirmations that come up.

Step 4: Check the screen

When the change is ready, Claude opens the app in the browser inside the Claude app and shows it to you. It runs only on your own computer, and the data in it is made-up test data. Try it yourself.

  • Is the change you asked for there? Check that it matches the plan Claude explained.
  • Is anything around it broken? Try the screens before and after the one that changed, and any feature that seems related.

Check the Screen explains this in more detail.

The first time takes a few minutes

Only the first time a screen is opened, the preparation takes a few minutes (a trial database is being fetched). From the second time on it opens in seconds.

If you want something changed, tell Claude in the same conversation.

Ask for a fix after seeing the screen
Claude prompt
I checked the screen. Please fix the following and show it to me again. 【Example: move the "Assigned to" column to the right of "Registered on"】

When it looks right, reply "OK". Claude creates a PR and gives you the PR URL.

If Claude asks "Do you also want to check in a preview environment?"

A preview is a trial environment prepared on the internet. You use it when you want to see the change with real data, try whether things like email arrive, or show it to someone else. It takes 10 to 20 minutes to prepare and costs money while it runs, so it is not made by default. If you are unsure, reply "Go ahead without one". You can still ask for it later.

Step 5: Check and merge

Now it is your turn. Follow Check and Merge to check the automatic checks and merge.

If you find something to fix after the PR exists

Tell Claude in the same conversation. When Claude fixes it, the same PR is updated.

Ask for a fix after the PR was created
Claude prompt
Please fix the following and add it to the same PR. When it is fixed, show it to me locally again. 【Example: move the "Assigned to" column to the right of "Registered on"】

Examples of asking

Hard to act onEasy to act on
Make the list easier to readMake the text in the list larger and add space between rows
Fix the buttonPressing Save on the registration screen does nothing. It should save and return to the list
Add another fieldAdd a Notes field to the registration screen. It is optional, and it should also appear in the list

Common mistakes

  • Packing several changes into one request
  • Replying "OK" without reading the plan
  • Merging without looking at the screen
  • Asking for a different change in the same conversation as earlier work

Quiz

Quiz

The screen Claude opened shows the column you asked for, but now you want it in a different position. What do you do?