Google · from experience
THE SOURCE · THE CASE STUDY ON KAGAMI.BGStitch: many screens in one style, one at a time
Draw 20–60 screens for a web platform in one style, without Stitch going its own way and without invented numbers.
Google Stitch in real work: 98 screens, 2 platforms
The numbers, the lessons and where each number comes from are in KAGAMI's article. Here is only the recipe. →
The prompt
Project: "<name>" — <one sentence on the purpose>. All UI text in Bulgarian (lang=bg). Rules on every screen: (1) … (2) … (3) … Visual style: <tone>. Colors: <color 1> + <color 2> + <background>. Font with good Bulgarian Cyrillic forms. No invented numbers, emails or deadlines: use placeholders [count], [email], [deadline]. Years up to 2026. We will build a numbered list of screens ONE AT A TIME. Now do ONLY screen 1, desktop: '<name>' — <content in 1–2 sentences>. Then stop and wait for my next instruction. Do not suggest or create other screens. --- every next screen --- Approved. Now do ONLY screen N as a NEW mobile screen: mobile version of desktop screen N '<name>'. Same design system, Bulgarian text only. Placeholders only, no invented numbers. Do not modify other screens. Then stop and wait. --- final pass --- Final consistency pass over ALL existing screens. Do NOT create or delete screens; only fix in place: (1) identical mobile bottom navigation (2) all years 2026 or earlier (3) replace every invented e-mail, phone, price, percentage, count and deadline with placeholders. When finished, list which screens you changed, then stop and wait.
The tool: the steps
The proof
GOOGLE · STITCHREV 0.1
- screens
- 98 in 2 projects (62 + 36)
- one run
- 44 screens in 1 h 47 min, no limit reached
- average per screen
- ≈ 2.5 min including the check
- to a live prototype
- ≈ 5 h 20 min (62 screens → 38 pages)
- date
- 04–06.11.2026
checkedrun by us; the numbers come from our records