Working with an AI Coding Assistant in Your Editor
Updated · Tech checked
Introduce your files, keep each task narrow, read the diff, and roll back cleanly when a change breaks things.
The direct answer
An editor assistant edits your files. It works best with introduced files, one narrow task per request, and a diff you actually read. Before any risky change, keep a snapshot copy of the working files.
Step by step
- Introduce the files: names plus one line each on what they do.
- Ask for one change in named files only; list behaviors that must keep working.
- Read the diff: every hunk gets a what, a why and a covering check.
- Run the old checks after the change, not just the new one.
- Restore the snapshot when the fix loop repeats twice.
Worked example
Tracker filter: allowed file (task list render), forbidden file (save logic). The assistant adds filter buttons; the save checks still pass on reload. Lab A16 practices rejecting unrelated hunks.
Errors to avoid
- Sending the whole project with fix everything. Narrow scope wins.
- Accepting long diffs unread. Unread diffs break working features.
- No snapshot before the experiment. Copy the folder first.
Frequently asked questions
Free or paid assistant? Free tiers exist with daily limits (checked 2026-10-04); this course needs no paid plan. The browser labs teach the same skills.
Does the assistant replace learning? No. You still verify: preview, checks, and the M07 debugging loop.
Sources
- Course lessons M06 and labs A16-A18 (this site).
- Assistant terms: the official docs of the tool you use (checked 2026-10-04).