The gap between "I installed it" and "I feel comfortable using it" is mostly just not knowing what the first few minutes look like. Here's exactly that, no surprises left out.
A prompt waiting for plain-English input — not a command syntax to memorize. You type what you want in normal sentences, the same way you'd describe a task to a colleague.
Something that costs nothing to get wrong: "explain what this file does" or "what does this function do." No files change, nothing to undo — just a chance to see how it responds before anything's at stake.
Explain what the file at src/utils/format.js does,
in plain language.Once you ask for an actual change, you'll see a plain-English description of the proposed edit — which file, what changes, sometimes a preview of the specific lines — before anything happens. It's usually a short, specific sentence, not a wall of code to decode.
Most early uncertainty isn't about the tool — it's the shift from thinking in exact instructions to describing what you actually want. "Fix the broken link on the pricing page" works better than trying to specify the exact technical steps yourself.
The free guide walks through an actual first task from start to finish — a better starting point than guessing.
Get the Free Guide →Something small and read-only to start — ask it to explain what a specific file does, before asking it to change anything. This costs nothing to get wrong and builds a feel for how it responds.
A plain-English description of the proposed action — which file, what change, sometimes a preview of the actual diff — with a yes/no choice. It's not a wall of code to interpret; it's usually a short, specific sentence.
Yes, and it passes fast. Describing an outcome in plain language, not a specific technical instruction, is the actual skill — most of the early uncertainty is about that shift, not about the tool itself.
For a small, scoped first task, undoing it is straightforward — that's exactly why starting small matters. The review step is there so "wrong" gets caught before it happens, not after.