Craftby ZakaCoding
A thinking partner.
On your canvas.
An AI companion for turning ideas into editable designs, with you in control.
The idea behind Craft
The space between
“what if” and “there it is.”
You have the idea. Then come the blank canvas, the first draft, the copy tweaks, and all the little decisions in between.
Craft brings a conversation into that space. It lives inside Design Studio, so you can ask for a plan, work through your copy, review suggested edits, or create a first design without leaving the editor.
I’m building it for independent makers and small teams who move between design and development. The goal is a shorter path to a useful first version, while keeping the result open to your own judgment.
A little less explaining.
Let’s see it move.
Ask in plain words. Review the suggestion. Choose what makes it onto your canvas.
Play Craft’s product film ↘Meet your canvas companion.
Ask, review, and make it yours.
A short look inside Craft.
A conversation.
With a clear next step.
The useful part isn’t just getting an answer. It’s knowing what Craft understood, what it intends to change, and when you’re ready to let it.
See the before and after.
Ask for a clearer headline or better layer names. Craft inspects the active page and puts the proposed changes in front of you, with checkboxes for each one.
A suggestion becomes an edit only after your approval.
Screenshots of the running Craft UI in an isolated test environment, using sample content and an offline model fixture.
From brief to native layers
The beginning of
something you can make yours.
A coffee shop. A software product. A creative studio. Different briefs, compiled into desktop and mobile boards you can keep editing.
Compiler examples from real Penpot acceptance tests, using curated offline model responses. These demonstrate editable output, rather than live model quality.
AI can make a suggestion.
You make the call.
Approval is part of the product’s architecture. Craft shows its intention before an edit, applies your selected changes, and reads the canvas again to check the result.
Your work stays editable. New designs become native boards, text and shapes. You can refine them directly in the editor.
The scope stays visible. Proposals identify the target page and intended changes. New-design proposals add boards alongside existing work.
The engineering behind the experience
A small interface.
A considered system underneath.
Craft connects a hosted design editor, a bounded AI workflow, and a gateway that turns approved intentions into canvas operations.
Penpot editor + Craft panel
Context, proposals & usage ledger
Through Cloudflare AI Gateway
Apply, inspect & verify
01 Let the model describe. Let the compiler build.
For new designs, the model produces a structured brief: copy, palette, typography and section choices. Craft’s compiler turns that brief into a validated layout, then fixed gateway scripts create native Penpot layers.
This separates a model’s language output from the geometry and code that touch a design. The compiler handles layout rules, font selection and contrast checks. Today’s library is bounded; broader layout variety and iterative refinement remain development work.
02 Make approval a boundary the system enforces.
Reading a page and proposing a change are separate from applying it. Proposals are bound to the user and target, expire, and can be applied once. The canvas gateway checks the active file and page before writing.
After applying, Craft reads the affected layers to verify the outcome. Partial or uncertain operations are reported explicitly, so an incomplete edit is not presented as a successful one.
03 Account for usage before sending the request.
Craft Managed uses Cloudflare Workers AI through AI Gateway. The application reserves an estimated allowance before inference and settles confirmed usage afterwards. Studio Credits & Usage makes that accounting visible.
Application budgets sit alongside provider controls. The system handles exhausted limits and unresolved usage as explicit states. Applying an already-approved proposal does not trigger another model call.
04 Build the operational layer around the product.
Cloudflare protects the public entry with DNS, edge controls and a separate Access-protected developer gateway. R2 holds encrypted off-server backups. The editor and Craft application run on VPS infrastructure.
Penpot provides the open-source design foundation. ZakaCoding develops and operates the hosted experience, Craft, account flows, usage accounting and the gateway integration independently.
CraftBuilt on Penpot. Craft by ZakaCoding.
Let’s make room
for your next idea.
Explore the studio, or talk with me about the product, the technology, and where it goes next.