Vale construir sua versão de Sleek?

Build me a mobile app screen designer to replace Sleek. Requirements:

- A local Next.js app (App Router) calling the Anthropic API (claude-opus-5,
  key in .env). Stream it with max_tokens 32000 · a screen plus its thinking
  share that budget, and it rejects sampling params and assistant prefills
  outright. Screens are files on disk, no database.
- One route handler takes a plain-language description of the app, or a sketch
  I drop on the page, and answers with a screen list first: 6 to 10 names, one
  line of purpose each. I edit that list, then it builds every screen on it.
- That same first call writes design-system.json (5 hex colors, 2 fonts with a
  6-step type scale, radius, spacing unit, icon set) and _nav.html, and nothing
  regenerates either afterwards · every later call gets both pasted in verbatim,
  which is what stops screen 9 drifting away from screen 1.
- Each screen is public/screens/<name>.html: one standalone file, Tailwind via
  CDN, Lucide icons, a 402x874 viewport with 62px top and 34px bottom insets as
  CSS variables, 44px minimum tap targets, and that same nav.
- Edits re-send the current file plus my instruction and overwrite it in place,
  so untouched parts stay put; every version lands in screens/.history/.
- The page is a gallery: each screen in an iframe inside a phone frame, side by
  side, a text box under each for the next edit. `npm run export` runs
  Playwright at deviceScaleFactor 3 into exports/ plus a contact sheet.
- A "copy all to Figma" button: @figit/dom-to-figma (MIT), one frame per screen
  passing that iframe's contentDocument.body, convert({ frames }), then
  clipboard.write with its toClipboardItem(). Cmd+V in Figma lands the whole
  set as editable layers. Keep it in a client component and fire it from a real
  click, or the write is blocked.
- Out of scope, do not build: a click-to-edit canvas, share links, or hosting.
  Runs on my machine, no accounts, no telemetry.
- README: the API key, `npx playwright install chromium`, where files land, and
  that remote images need an imageLoader proxying around CORS.