How do I change the look of one screen without changing the rest?
Short answer
Tell Kai-Zen which screen and what to change; it may suggest the same elsewhere, and after your go only the agreed change is built.
Before you start
Words used here (1)
- Kai-Zen
- Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Deeper
Two kinds of look.
What one screen shows and how it is laid out: its parts, their order and size, its words and pictures. Changing this changes that screen only.
What all screens share: the colours, fonts, button and window styles and the logo, kept as one style sheet that the app reads its look from each time it starts, and the parts used on many screens, such as a button, a box or the menu. Changing one of these changes it on every screen.
The same look is used all through the app: a plan for software always holds the rule that the app reuses its own buttons and ways of doing things, never a second look for the same thing, with you as the person who requires it. So a screen can have a layout of its own, such as a large picture on the start page, but not, for example, a second kind of button. If you want that anyway, say so, and ask Kai-Zen, the planning agent, what it means for the rest of the app.
How to ask. Tell Kai-Zen in your own words which screen, what you want different and why, for example: On the booking screen, put the calendar above the list and make the times larger. Kai-Zen asks all its questions in one round. In the same message it may suggest the same change on other screens, and better ways to get what you want, with why; you decide. Then it writes the change in one short statement, what changes, for whom and how you will know it works, and asks for your go once. After your go, Agent.Coder, the agent that writes your app's code, builds only that change; anything else it sees, it notes and does not do. Another agent then checks it. An agent is your AI following one written procedure, its standing instructions, for one kind of work.
See it. When a step changes a screen, Agent.Coder opens the changed screen in a real browser at phone size and takes a screenshot before it hands the step back; if it has no browser tool, it says so. Before it is live, Agent.Coder gives you an address to open in your browser on your computer. Kai-Zen never puts anything live without your go; once it is live, it asks you to check it, and fixes what you send back until you approve. A screenshot of what you mean helps; the answer Can I show examples, drawings or screenshots of what I want? shows how.
Not what you wanted? Say what you want instead; something that should only look a little different is fixed in a new change. When a whole approach was wrong, ask your AI to undo it; the answer Can I undo what I've built, or go back to an earlier version? says more. To try a look first without changing the main app, see Can I try an idea on the side without changing the main app?
To change the colours, fonts or logo of the whole app at once, change its style; see Who decides how my app looks?
GilbApp has no control that changes your app's screens: the change is made in your app's code, by your AI.
This answer is written for a computer screen.
Source: Standards: Kai-Zen.Update (Shape: Ask the requester all your clarifying questions in one round; "suggest the same change to Y and Z where X changes, and better ways to get what they want, with why"; Go: "what changes, for whom, and how you will know it works. Ask the requester for go once."; Build: Build only this change. Note anything else you see; do not do it.; Check: Agent.Scaling and Agent.Tester, not the agent that built it); Kai-Zen.ConstraintRules.Reuse; Kai-Zen.GoLive; Kai-Zen.HumanCheck; App.Style.Choose (Save, Read: one style sheet, read at start); Agent.Coder (AfterIncrement); Proc_v_Rollback. GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no control in src that edits an app's code or screens (the Style button in src/style/StyleButton.tsx styles GilbApp itself and shows only to people who may write to GilbApp's own style vault). Live help pages, sentences shared: Who decides how my app looks?; My AI changed things I did not ask for. What now?; Can I undo what I've built, or go back to an earlier version?; Can I try an idea on the side without changing the main app?; Can I show examples, drawings or screenshots of what I want?; How can I see what I've built?.
Checked against GilbApp d529620.