Lesson 4 of 7
Propose, then wait
Every message to the agent ends where it must stop. Every proposal comes back to you, and then to chat, before anything is built.
1Guess first
The agent has read the seed. Its reply ends like this:
Found it: title.textWrap.
I'll now apply this to all 52 tiles and commit.
What do you do?
2Anatomy of a message
This is the message that should have gone first. Chat drafts it. Open all four parts.
The seed is saved. In seed\Seed.pbip I turned on
Title > Text wrap for visual S16.
1. Read the seed and tell me which file and property changed.
2. Propose how you'd apply it to the tiles in report\Report.pbip:
which files, how many.
3. Don't edit anything. Stop after the proposal and wait
for my go-ahead.
Tap a part to see its job.
0 of 4
3Spot the line
A real reply from the project. Which line should worry you?
Auto mode is a too: a second model decides which commands look safe enough to run unasked. It's a good net. It's just not your decision, and in this loop you wanted every decision.
4When the plan is a guess
Proposals can be wrong with total confidence. The agent twice estimated the gap that would line the "i" button up with the tile title. Both times Desktop disagreed.
Proposal: a spacing of 12 px will align the button
with the title on every card.
It's the third estimate. What now?