From a prompt to a deployed site you actually own.
Install one skill and Claude Code becomes a whole website team — strategy, design, copy, build, deploy. It works in gated stages you review, and every decision lands as an editable file in your repo. Close the chat; the work is still there.
$ npx skills add presso/presso --skill website-builder — this site was built by the product it describes.
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, so the work is deliberate and reviewable instead of a wall of generated output.
Intent lives on disk, not in a chat.
Discovery, brief, design, and voice are plain, human-editable 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. The site stays maintainable instead of frozen.
// this site was built by the product it describes — these files are in its repo.
$ npx skills add presso/presso --skill website-builder Astro, Tailwind, Cloudflare — boring on purpose.
Every site is the same plain, ownable architecture. Your code, your repo, no lock-in. The tooling is versioned with each site, so it keeps working — and you can hand it to any developer without explaining a proprietary builder.
$ npx skills add presso/presso --skill website-builder