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 8: Finish, publish and present · Lab

Checklist Plus README Review

45 min hands-on · Core

Browser only. Run the six-area checklist on your project, fix singly, sign, then review the README aloud.

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

  • Check six areas with per-line pass or fail
  • Fix findings singly with area re-runs and sign
  • Review the five-section README in a two-minute read-aloud

  1. Step 1

    Run the six areas

    Content true, layout two widths, behavior routine green, storage reload plus corrupt, safety sweep for secrets and personal data, words honest. Log every line.

    checklist.mdmarkdown
    PRE-RELEASE CHECKLIST (template)
---
Content: ____
Layout (360px + desktop): ____
Behavior (normal/edge/invalid/old): ____
Storage (reload/corrupt/delete/limits): ____
Safety (secrets/personal/screenshots): ____
Words (README five sections): ____
Signature: date ____ snapshot ____

  2. Step 2

    Fix singly and sign

    Each failing line becomes one single-change fix with its area re-run plus neighbors. Sign with date and snapshot name when green.

  3. Step 3

    Read the README aloud

    Five sections under one page with AI help in two sentences and limits named. Read aloud under two minutes; cut anything that fails the read.

How to confirm it worked

  • Six areas logged per line
  • Findings fixed singly with re-runs
  • Signature with date plus snapshot present
  • README passes the two-minute read-aloud

Workspace

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

Draft kept in this browser.

Hints, in three stages

Stage 1: a nudge

The safety sweep finds the embarrassing one: a real phone in an old screenshot. Replace with the cropped table-only image.

Stage 2: a direction

Re-run neighbors after each fix. Pre-release batching repeats course-old chaos at the worst moment.

Stage 3: almost the answer

Read aloud literally. Eyes skip hype; ears catch it. Cut every sentence that performs instead of informs.

Worked solution (open after an honest attempt)

Worked solution. Run example: content pass, layout pass, behavior green, storage pass plus corrupt pass, safety one finding (old screenshot with real phone, replaced singly, area re-run), words pass. Signed with date and snapshot. README: five sections, AI help two sentences, limits named, read in ninety seconds. Release is a fact, not a mood.