Should you build your own Sleek?
Prompt-to-design tool for multi-screen mobile app UI, with Figma and code export
One screen is already a yes, and you do not need this site for it: paste "design me a settings screen for an iOS app, Tailwind, 402x874" into the agent you already pay for and you get something decent. What Sleek sells is everything that makes twelve screens look like the same app, and most of that turns out to be prompt discipline rather than product. Decide the design system once, paste it verbatim into every later call, and hand the model the mobile conventions it does not apply unprompted: safe areas, 44px tap targets, native navigation instead of a website cropped to phone width. Two gaps survive that. There is no canvas, so every change is a re-prompt of a whole file rather than a click, and one call to one model is a rougher first draft than a tuned chain of them, which you pay for in your own iteration time. The Figma handoff is not one of the gaps: Sleek's own team ships the converter as MIT on npm, so the DIY build gets editable layers from one install.
ENOriginal research content in English. Original prompt preserved in English.
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.The prompt opens pre-filled in your agent. Review it before running.
What would building your own look like?
Generate one design system, generate each mobile screen as a standalone Tailwind HTML file against it, review them together in phone frames, and export PNGs plus editable Figma layers.
What you will need
- LLM API key
- Node 22+
- Playwright for screenshot export
Nobody pays for one screen, and that is the honest read on this category: the single-screen version got free the day coding agents got good. What is left is thinner than it looks. There is no network here, no proprietary dataset, no integration treadmill, and the Figma converter that used to be the hard part is MIT on npm. What is left is real work all the same. The prompt below is one call to one model; the product is a chain of them, each step routed to whichever model is the right trade of quality against speed for that step, with the prompts behind each layer rewritten over months of iteration. None of that shows up on screen one. It shows up on screen nine, and in how many re-prompts it took to get there. The other thing money buys is a canvas, where a change is a click instead of a whole file re-prompted. Neither is a moat, and the prompt below is the honest test of what they are worth to you.
xclicking an element to change it instead of re-prompting the whole file
xa tuned multi-step pipeline · you get one prompt on one model, and you close the gap in your own iteration time
xsketch input · photograph a hand-drawn screen and get it back as a design
xshare links, project history, and team seats
Prefer something ready-made?
Google StitchPrompt or screenshot to multi-screen UI, editable canvas, prototypes, Figma copy, and frontend code export; usage is capped, not trialled.Free↗License, setup, and limitations for each alternative.
How much does Sleek cost?
- Monthly billing
- $29/mo$29/mo
- Per year
- $348/yr$348/yr
- Annual billing
- $240/yr31% cheaper than paying monthly
- On a Brazilian card, with 3.5% IOF
- R$152/moR$1,254/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Sleek’s site. Vibe Radar does not handle payments.
| Plan | Monthly | Annual (per month) | What is included |
|---|---|---|---|
| free | $0/workspace | $0/workspace | 1 project and one-time credits for about 1 design; limited exports; credits do not renew. |
| starter | $29/workspace≈ $29 | $20/workspace≈ $20 | 3,000 credits/month, about 100 screens, and 5 projects. |
| pro | $69/workspace≈ $69 | $30/workspace≈ $30 | 20,000 credits/month, about 650 screens, and unlimited projects. |
| team | $99/user≈ $99 | $40.83/user≈ $40.83 | 30,000 credits/seat/month, about 1,000 screens per seat, and unlimited projects. |
Free tier1 project and one-time trial credits for about 1 design; credits never reset.
Billing termsStarter/Pro monthly + annual; Team annual price published; refunds only within 24 hours
Additional costsA generation uses about 30 credits and edits use 5–30. Pro and Team can buy 5,000 non-expiring credits for $15; Starter cannot buy extra credits.
Price historyStarter, month-to-month: $24.99 → $29 (2026-10)
verified 2026-10-20 · source ↗
Is it cheaper to build or buy Sleek?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (weekend). Does not price what you give up (support, integrations, security).
Is Sleek free?
The free plan is one project on one-time trial credits; nothing renews. The paid plan is Starter at $29/mo (checked 10/20/2026).
Can I rebuild Sleek?
Kinda. The core of Sleek is buildable in a weekend with the prompt on this page, but there are real gaps: clicking an element to change it instead of re-prompting the whole file, a tuned multi-step pipeline · you get one prompt on one model, and you close the gap in your own iteration time. Read the honest list above before committing.
How much does Sleek cost?
Sleek costs about $29/mo (Starter, checked 10/20/2026), which is $240 per year.
What do I lose by replacing Sleek?
Honestly: clicking an element to change it instead of re-prompting the whole file; a tuned multi-step pipeline · you get one prompt on one model, and you close the gap in your own iteration time; sketch input · photograph a hand-drawn screen and get it back as a design; share links, project history, and team seats. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Sleek?
Yes: Google Stitch (Prompt or screenshot to multi-screen UI, editable canvas, prototypes, Figma copy, and frontend code export; usage is capped, not trialled.) The prompt is for when you want it exactly your way.