Devlooper

Turns your Figma into production-ready code, then grades every section against the design until it passes. Mac app. Built by @_ArturGrzeda at @wearetonik

[Devlooper @_devlooper]

Introducing devlooper

The whole path from a design to a deployed site

The first full version of a page comes out of one run, overnight, with nobody in the room.

Point it at a Figma file and walk away. It builds the page section by section in Next or Astro, straight into your repo, grades every section against the design at every breakpoint, and keeps fixing until it clears the bar. Roughly 80% of the page is done before you look at it. Not one output handed over and called done. A loop that stops when the work matches.

→ A whole site, not one page. List the pages and it builds them, each held to the same bar
→ Every section graded against the design at every breakpoint, and fixed until it passes
→ The pages nobody designed, a privacy policy or a blog index, you describe in a sentence and it builds them to match the rest
→ Then you take over. Pick any element on the live page, give notes like you would to a designer, it edits the real source
→ Commit, CI gate, deploy to Vercel, without leaving the app

It built its own landing page last week: 18 rounds, 113 minutes, 86 against a bar of 85. It still needed a person for the last 20%, which is the part that needs taste.

No API keys. It runs on the Claude plan you already have, and your files never leave your Mac.

Built at @wearetonik, the studio behind the Supabase, LangChain and LlamaIndex front ends.

Designed by you. Built without you.

Waitlist: https://t.co/uD44RrpmGB

[Devlooper @_devlooper]

https://t.co/xvNTbGiFc9

[Devlooper @_devlooper]

100 on the waitlist.

If you're seeing this for the first time: devlooper turns a Figma file into production code. You point it at the design at the end of the day and walk away. Overnight it builds the page, scores every section against what you drew, and keeps fixing until it matches. In the morning you have a repo you own and a deployed link.

Thank you.

https://t.co/uD44RrpmGB

[Devlooper @_devlooper]

Introducing devlooper

The whole path from a design to a deployed site

The first full version of a page comes out of one run, overnight, with nobody in the room.

Point it at a Figma file and walk away. It builds the page section by section in Next or Astro, straight into your repo, grades every section against the design at every breakpoint, and keeps fixing until it clears the bar. Roughly 80% of the page is done before you look at it. Not one output handed over and called done. A loop that stops when the work matches.

→ A whole site, not one page. List the pages and it builds them, each held to the same bar
→ Every section graded against the design at every breakpoint, and fixed until it passes
→ The pages nobody designed, a privacy policy or a blog index, you describe in a sentence and it builds them to match the rest
→ Then you take over. Pick any element on the live page, give notes like you would to a designer, it edits the real source
→ Commit, CI gate, deploy to Vercel, without leaving the app

It built its own landing page last week: 18 rounds, 113 minutes, 86 against a bar of 85. It still needed a person for the last 20%, which is the part that needs taste.

No API keys. It runs on the Claude plan you already have, and your files never leave your Mac.

Built at @wearetonik, the studio behind the Supabase, LangChain and LlamaIndex front ends.

Designed by you. Built without you.

Waitlist: https://t.co/uD44RrpmGB

[SpaceXAI @SpaceXAI]

Introducing Grok 4.6.

It delivers frontier intelligence and is a significant improvement over Grok 4.5 at the same price.

[tonik - design for startups @wearetonik]

We got tired of choosing between shipping fast and owning the code. So our own @_ArturGrzeda built Devlooper: one agent turns your Figma into code, a second grades it against the design until it passes. We've been shipping our own client work with it. Now we're letting people in. Waitlist now open 👇 https://t.co/DKkh37UVys

[Devlooper @_devlooper]

I built a tool that turns a Figma file into production code. The part I'm proudest of is what it won't do. It never invents the design.

That wasn't laziness. A brand isn't a logo or a palette. It's the hundred choices a designer makes and the thousand they rule out, and that's the whole distance between a site that's unmistakable and one that's interchangeable.

A model can't work that way. A model averages. It hands you the middle of everything it has ever seen, which is why the pages it invents all arrive the same: gradient hero, three icon cards, a stat bar nobody asked for, centred CTA. Your client pays to stand apart and receives their competitor's website.

You cannot average your way to a decision.

So devlooper starts where your file ends. Point it at the design when you finish for the day, and go home. Overnight it builds, scores every section against what you drew, and keeps fixing until it clears the bar. By morning: production code in your repo, and a link.

The score measures fidelity, not quality. It will confirm the build matches your design. It will never tell you the design was any good.

That part is still yours. I've yet to see anyone take it.

What it does take is the pettier job. Opening staging next to Figma. Logging the heading that's one weight heavy, the section twelve pixels off, and the three more you delete because they sound small. All caught now, before the link reaches you.

Everything downstream of your file is becoming a commodity.

Your file isn't.

https://t.co/uD44RrpUw9

[P @_ptonik]

love how this turned out - easily one of my favorite brands we’ve done this year.

also, if you’re building sites, get on ploy asap.

[Devlooper @_devlooper]

I built a tool that turns a Figma file into production code. The part I'm proudest of is what it won't do. It never invents the design.

That wasn't laziness. A brand isn't a logo or a palette. It's the hundred choices a designer makes and the thousand they rule out, and that's the whole distance between a site that's unmistakable and one that's interchangeable.

A model can't work that way. A model averages. It hands you the middle of everything it has ever seen, which is why the pages it invents all arrive the same: gradient hero, three icon cards, a stat bar nobody asked for, centred CTA. Your client pays to stand apart and receives their competitor's website.

You cannot average your way to a decision.

So devlooper starts where your file ends. Point it at the design when you finish for the day, and go home. Overnight it builds, scores every section against what you drew, and keeps fixing until it clears the bar. By morning: production code in your repo, and a link.

The score measures fidelity, not quality. It will confirm the build matches your design. It will never tell you the design was any good.

That part is still yours. I've yet to see anyone take it.

What it does take is the pettier job. Opening staging next to Figma. Logging the heading that's one weight heavy, the section twelve pixels off, and the three more you delete because they sound small. All caught now, before the link reaches you.

Everything downstream of your file is becoming a commodity.

Your file isn't.

https://t.co/uD44RrpUw9

[Grok Bot @bot]

Introducing Grok Bot, now in early beta.

Bots are AI teammates that do real work for you. They sign in to your tools, use them just like you do, and come back with finished work.

[Devlooper @_devlooper]

@jaimintf LOADER

[Devlooper @_devlooper]

The score isn't a model's opinion. Position, size, spacing and type come straight out of the Figma file as numbers and get compared to what the browser actually rendered. A pixel diff runs alongside it, and the computed CSS gets checked against your tokens. Three independent signals, not one model saying it looks about right.

The thing that grades is not the thing that builds. Separate agent, separate context, no permission to edit anything. It isn't marking its own homework.

It also writes down the system it learned. A DESIGN.md with your colours, type scale, spacing and radii pulled out of the file, a spec for every page, and a live style guide route in the site itself. The next person to touch the repo doesn't have to guess what the rules were.

And because that system exists, the pages nobody drew don't need a design at all. Describe a privacy policy or a blog index in one sentence and it builds them to the rules it already learned, so they come out looking like the rest of the site instead of like something else.

If a fix lowers a section's score, it gets reverted automatically, so it can't break what already passed.

[Devlooper @_devlooper]

Introducing devlooper

The whole path from a design to a deployed site

The first full version of a page comes out of one run, overnight, with nobody in the room.

Point it at a Figma file and walk away. It builds the page section by section in Next or Astro, straight into your repo, grades every section against the design at every breakpoint, and keeps fixing until it clears the bar. Roughly 80% of the page is done before you look at it. Not one output handed over and called done. A loop that stops when the work matches.

→ A whole site, not one page. List the pages and it builds them, each held to the same bar
→ Every section graded against the design at every breakpoint, and fixed until it passes
→ The pages nobody designed, a privacy policy or a blog index, you describe in a sentence and it builds them to match the rest
→ Then you take over. Pick any element on the live page, give notes like you would to a designer, it edits the real source
→ Commit, CI gate, deploy to Vercel, without leaving the app

It built its own landing page last week: 18 rounds, 113 minutes, 86 against a bar of 85. It still needed a person for the last 20%, which is the part that needs taste.

No API keys. It runs on the Claude plan you already have, and your files never leave your Mac.

Built at @wearetonik, the studio behind the Supabase, LangChain and LlamaIndex front ends.

Designed by you. Built without you.

Waitlist: https://t.co/uD44RrpmGB