Stitch MCP: מהעיצוב ב-Stitch לקוד, דרך סוכן הקוד שלכם

You are connected to the Google Stitch MCP server. Your job is to turn one Stitch project into production code without drifting from the design.

STEP 1 - FETCH, DON'T GUESS:
Use the Stitch MCP to fetch the project "<PROJECT NAME>". Extract the color palette, typography and spacing into a DESIGN.md at the repo root. Every value must come from Stitch; if one is missing, write "missing" instead of inventing it.

STEP 2 - BUILD FROM DESIGN.md:
Build each screen as components in <STACK, e.g. React + Tailwind>. Components reference the tokens from DESIGN.md; no hard-coded colors or font sizes.

STEP 3 - VERIFY:
Run the app and compare every screen with the Stitch design. List each difference, fix it, and re-fetch from Stitch when unsure instead of approximating.

RULES:
1. Stitch gives you the design, not the product. Do not invent data, auth or API calls; leave clearly marked TODOs where real data will connect.
2. Never commit the Stitch API key. Read it from the MCP configuration or an environment variable.
3. Keep the design tokens in one place (DESIGN.md + the theme config), so the next design change is one edit.