From a prompt to a deployed site you own.
Install one skill. Claude Code becomes a website team: gated stages you review, every decision written to your repo.
$ npx skills add presso/presso --skill website-builder this page was built from these files.
You need a proper site. Every other option makes you give something up.
Generic-looking pages, and the intent evaporates the moment the chat ends. The next change starts from zero.
Wix, Squarespace, Framer: a templated look, and they own your stack. You build on rented ground.
Agency-grade work, agency-grade bill: thousands of dollars and weeks of calendar time.
A pipeline with gates, not a one-shot generation.
Strategy before design. Design before code. QA before deploy, and you approve every deploy yourself. Each stage reads what came before and writes one file your repo keeps.
- 01 discovery
truth about the product and who it’s for
writes: docs/discovery.md
- 02 brief
the plan for this site: pages, value, the one action
writes: docs/website/brief.md
- 03 design
every color and font, named. You pick the direction.
writes: docs/website/design.md
- 04 voice
how the brand sounds, everywhere
writes: docs/voice.md
- 05 build
mobile-first, built against the specs above
writes: an Astro + Tailwind site in your repo
- 06 qa
bugs and spec compliance. Nothing ships until it’s clean.
writes: a gate, not a file
- 07 deploy
only on your explicit go-ahead. The gate you hold.
writes: docs/website/deploy.md
Intent lives on disk, not in a chat.
Discovery, brief, design, and voice are plain files in your repo, plus a decision log that records why each call was made. A new session, a new developer, or a future workflow picks up exactly where things stand.
This page is the proof.
This site was built by the product it describes. The record on the right is the decision that reshaped the page you’re reading; the rest of the system of record sits next to it in the repo.
Read docs/ in the repo →Astro, Tailwind, Cloudflare. Boring on purpose.
Your code, your repo, no lock-in. Hand it to any developer; there’s no proprietary builder to explain.
The last gate is you.
Presso never ships on its own. QA runs first; the deploy waits for your explicit go-ahead. Until then, everything sits in your repo as files you can read and edit.
$ npx skills add presso/presso --skill website-builder