Lesson 02 of 5 in Module 03

⏱️ 02 Mins read

Wire AI into your workspace

Lesson 1 named the roles. This lesson gets one tool talking to your my-static-site folder from Module 02 — or records honestly what stopped you.

See Practice site thread if you need the bigger picture.

Do this — setup checklist (20 minutes)

Work through the list. Skip steps that do not apply (Cursor users often skip third-party extensions).

  • Open my-static-site as your IDE workspace (File → Open Folder).
  • Pick one path below: IDE-integrated AI, terminal CLI, or browser-only — and note why.
  • Complete sign-in if the tool asks (command palette → extension name + “Sign in”).
  • Smoke test: ask “Explain index.html in this project” — confirm answers reference your files, not generic advice.
  • Write one limitation you noticed (policy, cost, region, account, hallucination).

Install steps go stale fast. Official starting points: AI tool setup links.

Pick one path

IDE-integrated (preferred for this course)

Cursor — AI is built in. Sign in, pick model/privacy settings, open my-static-site, run the smoke test.

VS Code + extension — install from a recognised publisher only (e.g. GitHub Copilot, Anthropic, Google Gemini extensions). Reload → sign in → same smoke test.

The win: edits land in files you can refresh in the browser.

Terminal CLI (paired with IDE)

Example: Gemini CLI in a terminal tab beside your editor. Good for questions and tasks; the IDE still holds files and diffs. See AI tool setup links for install docs — do not memorise commands here.

Browser chat (supplemental)

ChatGPT, Claude, Gemini in the browser — fine for explain and rough generate. Three problems if you stop there:

  1. No file truth — which version is current after ten chat turns?
  2. No project context — the model forgets your folder unless you re-paste it.
  3. No clean diff — you cannot git diff a chat.

Rule: browser for drafts; IDE + folder for the ship.

When it breaks (quick fixes)

  • Extension idle → Sign in first.
  • npm / npx not found → install Node.js LTS, restart terminal.
  • OAuth fails at work → ask IT; do not route employer data through personal accounts.

Do this — reflect (10 minutes)

  1. Which path did you complete — or what blocked you?
  2. Four limitations in your own words.
  3. One sentence: why IDE + folder still matters if browser chat feels faster.

What's next

Next up: Privacy, policy, and workplace reality