Quickstart: from nothing to your first site

What you need

• An AI coding assistant. Claude Code is the one Croftweaver is developed and used with. There are install guides for Codex and Antigravity too.
• A GitHub account. Free. Your site's files live there, and the account is yours.
• A computer. macOS, Linux or Windows. On Windows, WSL2 is the smoothest route.
• Later, a Cloudflare account. Free. You need it when you publish, not on the first day.

You do not have to install Node, git or anything else first. The assistant installs a tool only when the site needs it, and asks you before it does.

The guides for Codex and Antigravity exist, but Croftweaver has not been tested from start to finish with either of them yet. If you try one, an issue on GitHub saying how it went is welcome.

The easy way: one prompt

1. Install an assistant and open it.
2. Paste this prompt and send it:

I want to use the Croftweaver skill suite (https://github.com/karero/croftweaver) to create a new website. Please guide me step by step in plain language. First, check which required tools this computer already has. Explain every command before you run it, and install missing tools only when they are actually needed. Then install the Croftweaver skills, tell me when to restart or reopen you so the skills load, and continue from there: start a fresh site by running "new website" in a new, empty folder.

3. Answer its questions. It builds the site from your answers.

Or install by hand

Get the repository first:

git clone https://github.com/karero/croftweaver.git
cd croftweaver

Then run the installer for your assistant:

Claude Code

./scripts/install.sh

Links every skill into the folder Claude Code reads.

Codex

./scripts/install-codex.sh

Links every skill into the folder Codex reads.

Antigravity

mkdir -p ~/.gemini/config/skills
cp -R skills/* ~/.gemini/config/skills/

Copies the skills into the folder Antigravity reads.

Restart the assistant, open it in a new, empty folder, and say new website.

The six questions it asks

Before any code, the assistant asks six questions. They are decisions, not commands, and it records your answers in the README of your project.

1. Which pages do you need, and does anything repeat? Fixed pages, or content with one shape and many entries, such as posts or events.
2. Does a server have to do anything? Most sites are static. A form that emails you or one live widget needs a single small function.
3. Who edits the content after launch? You and your assistant in files, or a person who needs an editor.
4. One language or several, and which language is the copy in? A second language can be added later without moving existing addresses.
5. Do you need analytics? Google Search Console alone is free and needs no script and no banner.
6. Which domain, and how do changes go live? Recommended: a preview that search engines do not index, then one command to publish.

What happens then

The assistant works out with you what you offer and for whom, drafts the pages, adds the search and AI work, and runs the tests. Then it helps you publish. The skills, by stage shows which skill does which part, and the test gate shows what is checked.