The most detailed free FDE + DevOps library: 140+ lessons, 70+ labs and 80 long-form articles, in English and Turkish. Start learning →

TürkçeSearch

Build with AI: From Zero to Your First App · Module 6: Working reliably with AI coding tools · Lab

Fresh-Chat Move With Quota Log

30 min hands-on · Core

Browser only. Move your project to a fresh chat on summary alone; count every message for the quota log.

Three ways to do this lab. A: the browser steps below, the main path, free with no account. B: try the same task with your own AI tool if you have one (its terms and quotas apply). C: work from the provided material and the worked solution below, which teaches the same skill. No path claims you used a live AI tool when you did not.

Objectives

  • Write the five-line summary under 150 words
  • Continue one real task in a fresh chat with summary plus one change
  • Log every message with its purpose for the quota record

  1. Step 1

    Write the summary

    Five lines: what it is, files, decisions (out-list, browser-only), unfinished with criterion, never-include respected. Under 150 words, in your notes.

    summary-template.mdmarkdown
    SUMMARY TEMPLATE (max 150 words)
---
What: ____
Files: ____
Decisions: ____
Unfinished: ____ (criterion: ____)
Never included: passwords, keys, personal data.

  2. Step 2

    Move chats

    Open a fresh chat, paste the summary, add one single-change request. Record the tool's first answer: on-track, or corrected with one pointer. No whole-project dumps.

  3. Step 3

    Log the quota

    Log every message of the move with purpose (summary, edit, follow-up, correction). Count total generations spent and state whether a rewrite was avoided.

How to confirm it worked

  • Summary with five lines under 150 words
  • Fresh chat continued without whole-project dump
  • First-answer quality recorded
  • Quota log complete with rewrite-avoided statement

Workspace

0/2 checks passing · Coverage only, not a quality score.

Draft kept in this browser.

Hints, in three stages

Stage 1: a nudge

If the tool re-suggests a parked item, point at the decision line once. That correction is the summary paying rent.

Stage 2: a direction

One change only in the move message. Moves fail when they smuggle new scope.

Stage 3: almost the answer

Count honestly, including corrections. The log is for your budgeting, not your image.

Worked solution (open after an honest attempt)

Worked solution. Summary example: 'Bakery one-page site (index, styles, app, one image, README). Out: payment, accounts, tracking. Browser-only. Unfinished: button reach at 360px; criterion reachable without scrolling. Files listed.' Fresh chat: summary plus styles.css-only button-spacing change. First answer on-track, one generation. Log: summary (1), edit (1), verification follow-up (1); rewrite avoided, three generations total.