Your agent builds the site.Your team gets the editor.
Hand your coding agent a prompt. It creates a normal React and Vite project, reads the manual that comes with it, checks its work and commits as it goes.
Create a project with the open-source Uniweb framework, using npx uniweb@latest create . --template starter, or a template from npx uniweb@latest template list if one fits. Read Part 0 of its AGENTS.md before writing code.
Check your work with npx uniweb inspect and in a browser, and commit each time something works. Don't sign in or deploy anything: I'll choose where it goes.
What I'm building: Replace this: what the site is, who it's for, and what you already have.
Create a documentation site with the open-source Uniweb framework, using npx uniweb@latest create . --template docs. Read Part 0 of its AGENTS.md before writing code.
Keep the pages as plain Markdown, and keep their addresses if they already exist. Check your work with npx uniweb inspect and in a browser, and commit each time something works. Don't sign in or deploy anything: I'll choose where it goes.
What it documents: Replace this: the project, who reads it, and where any existing docs are: a folder, a repository, or a site built with Docusaurus, VitePress or anything else.
Bring my React code into the open-source Uniweb framework, using npx uniweb@latest create . --template paste. Read Part 0 of its AGENTS.md before writing code, and https://uniweb.io/docs/development/converting-existing.md for how to convert it.
Keep how it looks. Split it into named section types, with their text in Markdown and their colors in theme.yml, and tell me about anything that doesn't carry over rather than dropping it. Check your work with npx uniweb inspect and in a browser, and commit each time something works. Don't sign in or deploy anything: I'll choose where it goes.
My code: Replace this: where it is (a file, a folder or a repository), what it's built with, and what else the site needs.
This is a project built with the open-source Uniweb framework. Bring it into the Uniweb app, so people who don't code can edit it there. Learn how from the guide provided by npx uniweb@latest start.
First make sure what they should change lives in Markdown or in a param its meta.js declares, not in component code, and check it with npx uniweb validate. Show me what you changed and commit it before you sign me in. Don't take the site live unless I ask.
Who edits what: Replace this: who will edit the site, what they should be able to change, and what should stay fixed. Name the organization if it belongs to one.
What you need: an agent that can run commands in a folder, such as Claude Code, Codex or Cursor, with Node.js 22.12 or later and Git. Open it in an empty folder, or in your project for the last prompt.
A project it can check for itself.
A build can pass while a page is wrong: an unknown section type or param builds fine and renders wrong. So the tooling is made for confirming, not guessing.
A manual for this project
create writes it into every project, matched to the version it runs, and uniweb update refreshes it. It routes the agent to the part its task needs.
Print it, don't predict it
Shows how a page or section really parses, so the agent confirms where content lands instead of working it out from memory.
Content against its schemas
Checks the content against the data schemas your foundation declares. uniweb doctor does the same for the project's configuration.
What changed, and what to run
Reads Git, the app and the latest release, changes nothing, and ends with the commands to run next, in order.
A server it can run in the background
Takes a free port and prints the address once it's listening. --status reports it and --stop ends it.
Docs it can fetch
An index of the documentation: every page, with a line about it and a link to its Markdown. The manual points there for whatever it doesn't cover.
What happens next
Nothing goes anywhere until you say so.
- 1
Paste the prompt
Open your agent, paste the prompt and replace the highlighted part with what you want.
- 2
It builds and checks
It creates the project, reads the manual, writes section types in React and pages in Markdown, and looks at the result. Each step that works is a commit.
- 3
You review it
It's a normal project in a Git repository. Read the commits, run it, and change what you like, by hand or by asking again.
Prints the address the site is running at.$npx uniweb dev - 4
You choose where it goes
Any static host, for free and with no account. Or Uniweb Cloud, which brings the visual app and the live database, when your team needs them.
Or$npx uniweb deploy --host cloudflare-pagesuniweb publishfor Uniweb Cloud.
You, your agent and your authors, on one site.
Your agent works in files, like you do, so its changes go through Git and you review them as you would anyone's. Bring the project into the visual app, and authors can edit the same site without touching either.
uniweb pull merges their edits into your branch as a commit. Edits to different sections combine. If one section changed on both sides, a push is refused and the pull leaves ordinary conflict markers to settle.
- You and your agent: React, Markdown and Git
- Authors: the visual app, with no Git and no Markdown
uniweb statussays what changed where, and what to run
Before you paste a prompt
Do I need a Uniweb account?
No. Creating, running and building a project takes no account, and neither does a static host: uniweb export builds a dist/ for any host, and uniweb deploy --host=<adapter> or uniweb add ci --host=<adapter> handle Cloudflare Pages, Netlify, Vercel and GitHub Pages. You sign in only to use the visual app or Uniweb Cloud.
What will the code look like?
Standard React and Tailwind. A section type receives its content as props, and from there it's ordinary React: import any library, use any pattern. Pages are Markdown files, and configuration is YAML.
What does it cost?
The framework is free and open source, under Apache-2.0. A Uniweb account is free too, and you can keep drafts in the app. You pay when a site goes live on Uniweb Cloud. Your agent is separate, with its own pricing.
Can the agent take my site live by itself?
These prompts tell it not to. On Uniweb Cloud, uniweb push only sends a draft, uniweb publish is what takes a site live, and a first publish stops at a payment page in your browser.
Does it work with a cloud agent?
For building, yes: an agent in a cloud workspace made from your repository can create the project, build it and commit. It can't sign you in to Uniweb from there yet, because uniweb login --browser finishes on a local port, so do that part on your own computer.
Can it work in a repository I already have?
If it's already a Uniweb project, yes: open your agent there and ask, and npx uniweb@latest start orients it. A new project needs a folder of its own, because create stops rather than overwrite a file and doesn't make a project inside another workspace. To bring in code you already have, use the React prompt.
Where do my own conventions go?
In a file of your own, such as NOTES.md. uniweb update rewrites AGENTS.md for each new version and keeps only a block between <!-- project-notes:start --> and <!-- project-notes:end -->, which is the place for a line pointing to your notes.
I'm building for someone who won't open a terminal.
Send them to uniwebapp.com/ai: the same workflow in their words, with prompts that bring the site into their Uniweb account.
Prefer to start by hand?
It's the same project either way, and you can bring an agent in whenever you like.
$npm create uniweb