Design Is a Conversation
Generate, read it back, correct — design isn't one-shot.
The first generation is a draft, not a delivery. Read the code back, compare it to the frame, and say what's off — this gap is wrong, that color should use the token, the empty state is missing. Design-to-code gets good through a few tight rounds of correction, not one heroic prompt.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Iterate, Don't One-Shot
Claude generated a 'Profile card' from the frame and it's 80% there. Three things are off: the avatar renders as a square instead of a circle, the bio uses a raw gray (`text-gray-500`) instead of the muted-text token, and there's no spacing between the name and the role.…
Other principles in Multi-Step
Architect Before You Ask
Ask for a Plan First
Request a plan before any multi-file change — approve the approach, then let it code.
Break the Workflow into Steps
Number each step so Claude builds pieces, not monoliths.
Combine Context with Action
Coordinate Across Files
Delegate to a Subagent
Spawn a subagent for research-heavy subtasks; brief it on scope, limits, and report shape.