Takeaway: Next time I'd point directly at the CSS variables involved (--tool-output-bg, --shiki-dark-bg) since the agent had to spend a lot of turns grepping through multiple components to find the source of the color mismatch.
Takeaway: Next time I'd point directly at the CSS variable names (--rail-bg vs --bg) and the exact selector since the agent spent most of the session just searching files to find the relevant style.
Takeaway: Next time I'd describe the corner/divider interaction more precisely upfront — screenshots after each change helped catch when the agent's approach (adding radius to the whole sidebar) visually broke things.
Takeaway: Next time I'd paste the workflow files alongside the error so the agent doesn't have to go fetch them itself.
Takeaway: I'd tell it upfront to double-check tool call argument names against the schema before batching reads, since the file/path mixup cost a whole retry cycle.
Takeaway: I'd start by asking it to both audit and fix in one pass, since the audit alone took a long time reading every file before finding just two real issues.
Takeaway: Next time I'd put the full spec in the first prompt — I ended up repeating the same 'init only fetches workspaces, expand lazily loads 5 sessions, delete rename' request three times before the agent actually executed it instead of just re-designing.
Takeaway: Next time I'd ask upfront for click-outside-to-close behavior along with the lightbox feature, since it's an obvious pairing.
Takeaway: Next time I'd describe the exact final look I want (no border, transparent by default, hover background) in one prompt instead of iterating three times.
Takeaway: Next time I'd start the prompt by naming the exact package to delete (packages/web) since the agent had to spend a lot of turns just grepping the whole repo to figure out where Vue was referenced.
Takeaway: Next time I'd be more specific upfront about exactly which padding/corners to change and preview before committing, since I ended up reverting two of the four style tweaks.
Takeaway: Next time I'd point straight at the @pierre/diffs type declarations instead of letting the agent search node_modules from scratch through several pnpm-hashed paths.
Takeaway: I'd start by pointing out the uncommitted package.json/pnpm-lock.yaml changes myself so the agent doesn't have to pause and ask — that stop-and-ask was reasonable but cost time I could've saved with more context up front.
Takeaway: Next time I'd describe the exact observed behavior up front — 'streaming shows no queue, only cancel reveals it' — instead of a vague 'steering shows late', since the agent latched onto the wrong direction and built a whole feature before I could correct it.
Takeaway: I kept re-asking the same question about uncommitted changes because the answers felt inconsistent between runs, and I never actually got the agent to do anything with them.
Takeaway: Next time I'd just point directly at the file (ChatTranscript.vue) and mention both the web and svelte packages need the same fix, since that's where all the search time went.
Takeaway: Next time I'd specify upfront whether I mean horizontal or vertical centering, since my first ask about 'centering' the title was ambiguous and the agent guessed wrong direction.