use-cases/make-granular-ui-changes.md +0 −97 deleted
File Deleted View Diff
1name: Make granular UI changes
2tagline: Use Codex-Spark for fast, focused UI iteration in an existing app.
3summary: Use Codex to make one small UI adjustment at a time in an existing app,
4 verify it in the browser, and keep iterating quickly from a popped-out chat
5 window near your preview.
6skills:
7 - token: $playwright
8 url: https://github.com/openai/skills/tree/main/skills/.curated/playwright-interactive
9 description: Open the running app in a real browser, inspect the changed route,
10 and verify each small UI adjustment before the next iteration.
11bestFor:
12 - Existing apps where the main structure is already built and you need small
13 visual adjustments
14 - Fast product or design review loops where each note should become one
15 focused code change
16 - UI polish passes that need browser verification but should not turn into a
17 broad redesign
18starterPrompt:
19 title: Make One UI Change
20 body: >-
21 Make this UI change in the existing app:
22
23 [describe the exact spacing, alignment, color, copy, responsive, or
24 component-state adjustment]
25
26
27 Constraints:
28
29 - Change only the files needed for this UI adjustment.
30
31 - Reuse existing components, tokens, icons, and layout patterns.
32
33 - Keep behavior, data flow, and routing unchanged unless I explicitly ask
34 for it.
35
36 - Start or reuse the dev server, inspect the current UI in the browser, make
37 the smallest patch, and verify the result visually.
38
39
40 Stop after this one change and summarize the files changed plus the browser
41 check you ran.
42 suggestedModel: gpt-5.3-codex-spark
43 suggestedEffort: low
44relatedLinks:
45 - label: Codex-Spark
46 url: /codex/agent-configuration/speed#codex-spark
47 - label: Floating pop-out window
48 url: /codex/reference/settings#keep-an-app-chat-near-your-work
49
50> For the complete documentation index, see [llms.txt](/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.
51
52## Introduction
53
54When you have an existing app and want to iterate fast on the UI, you can use `gpt-5.3-codex-spark` to make small, focused changes to the UI.
55Codex-Spark is our fastest model, optimized for near-instant, real-time coding iteration.
56
57This works best as a tight loop: one visual note, one focused edit, one browser check, then the next note.
58
59You can use the [Codex Spark model](https://developers.openai.com/codex/models) for this task. It is
60 available on Pro plans.
61
62## Pick your model
63
64For fast UI iteration, start with `gpt-5.3-codex-spark` if you have access to it. It is less capable that our general-purpose models, but is designed for real-time coding iteration. If you don't have access to it, use `gpt-6-astra` with `medium` or `low` reasoning effort.
65
66That tradeoff is useful for granular UI work. You usually do not need the deepest model to move a button, tune a breakpoint, or adjust a component state. You need a model that responds quickly, understands the local code, edits the right file, and can repeat the loop without making the iteration feel heavy.
67
68## Development flow
69
701. Open the existing app and get the relevant route or component visible.
712. Pop out the active Codex chat into a [floating window](https://developers.openai.com/codex/reference/settings#keep-a-chat-near-your-work) and keep it near your browser, editor, or design preview while you work.
723. Give Codex one specific UI change at a time. Include the route, viewport, current screenshot, target screenshot, or exact product note if you have it.
734. Ask Codex to inspect the current implementation, make the smallest defensible edit, and preserve the app's existing components, tokens, layout primitives, and data flow.
745. Review the result, then send the next small adjustment in the same chat.
75
76## Write small prompts
77
78Granular UI prompts should be direct and narrow. A good prompt names the surface, the target change, and the validation you expect.
79
80If the result is close but not quite right, keep the follow-up equally specific:
81
82
83
84**Prompt:**
85
86```text
87The change is close. Keep the implementation, but adjust only this detail:
88[describe the remaining mismatch]
89
90Verify the same route and viewport again before you stop.
91```
92
93## When to slow down
94
95Do not keep using the fast loop if the task stops being granular. Switch to a stronger model and a more deliberate prompt when the change needs broad refactoring, a new design system primitive, non-trivial accessibility behavior, or a product decision that affects more than one screen.
96
97Fast UI iteration works best when Codex is adjusting an already-understood surface, not redesigning the app from scratch.