Five stages,
one owner: you.
- 01
Brief
Say what it should do
A brief is a few sentences about behaviour: who deposits, who withdraws, what is fixed forever, what one account may do that others may not. Numbers and names in the brief are read as settings, so “a token called Harbor Coin, symbol $HRBR, 5 million supply” sets all three.
Briefs work best when they describe outcomes rather than code. “Only the owner can mint, never above 2 million” is easier to get right than “add an onlyOwner modifier to mint”.
- 02
Draft
Get one readable file
Without an AI key on the site, the drafter reads the brief, picks the closest of six templates and fills in what it understood. It tells you when the brief asked for something the templates cannot write, such as upgradeable proxies or lending, instead of pretending.
When the operator configures an AI model, the brief (and for a change request, the current file) goes to that model with fixed rules: one file, no imports, owner passed as an argument, checked calls, events for every state change. The answer replaces the editor only after you confirm.
- 03
Compile
Build it on your machine
The studio runs the official Solidity 0.8.28 WebAssembly build in a web worker. Before running it, the browser computes the file's SHA-256 and compares it with the value the Solidity project publishes. Your source is never uploaded to compile.
Errors and warnings link to their line. Each deployable contract shows its runtime size against the 24,576-byte limit, its ABI and its bytecode.
- 04
Review
Read findings and a test plan
The security tab re-checks the source as you type against the published rules: permissions through tx.origin, unchecked calls, state written after an external call, constructors that read msg.sender, ETH that can never leave, and more. Each finding points at a line and suggests a fix.
The tests tab turns the compiled interface into a Foundry test file: deployment in setUp, one test per state-changing function, one revert test per custom error, and invariants that fit the template. Fill in the TODOs and run it locally.
- 05
Sign
Deploy with your own wallet
Constructor arguments are typed and checked field by field. A short checklist asks you to confirm you read the source and the findings. Then the transaction opens in your wallet on Robinhood Chain, which shows the gas and asks you to sign. The studio never signs anything.
Deploy directly, or through WerboPress once it is live, which also records an imprint: deployer, creation-code hash, runtime-code hash and the source hash you declared. The address and transaction are saved with the project.