Ask Claude Code to "build a website for my company" and the first result usually looks convincing: a hero, a services grid, a contact section. Then you click around. The contact form submits to nothing. The bookings page has no empty state because there are no bookings and no code path for that. There is no admin, no login, and the second page is a thinner copy of the first. You got a screenshot of a website, not a website.
The problem is not the model. A bare prompt carries no scope, no structure, and no definition of done. A skill fixes that by giving the agent a procedure to follow instead of a vibe to improvise around. This tutorial uses Web Builder, an open-source skill (MIT) built for exactly this job, and walks through a real build: a services site for a UK repair company, with case studies, bookings, customer inquiries, and an admin area.
What a skill actually is
A skill is a directory your coding agent loads as working instructions. Web Builder's repository has SKILL.md at the root as the entry point, plus references/ (type and module definitions, implementation and verification guidance), config/ (the catalog of types, modules, and dependencies), scripts/ (the executable tooling), assets/ (foundation layers), and tests/.
Scope is defined as website types × functional modules. There are 11 types — landing, business, commerce, content, booking, education, directory, dashboard, tool, community, marketplace — and 26 modules grouped by concern: admin, authentication, tenancy; content, taxonomy, search, seo; commerce, payments, shipping, after-sales; inquiries, bookings, learning; subscriptions, entitlements; notifications, sms; and a few platform ones (directory, execution, community, marketplace, analytics). You compose the modules your site needs instead of bolting commerce or membership onto every project.
Install
npx skills add https://github.com/skillux-hub/web-builder --skill web-builder Pick your agent and install scope when prompted. Cloning the repo and installing the directory manually also works — just preserve the relative structure of SKILL.md, references, config, scripts, and assets, because the scripts resolve paths against it.
Two runtime requirements worth knowing before you start: the skill's generation tools need Python 3.10+, and generated applications need Node.js 22.12+ with npm and an environment that supports SQLite native dependencies.
Step 1: Log in and write a brief, not a prompt
Web Builder verifies a Skillux session before anything else, because template downloads later in the flow are entitlement-checked:
python scripts/skillux.py login Then write the brief as a JSON file, saved outside the repository (for example ../brief.json):
{ "brand": "Example Services", "business": "Service presentation, case studies, and customer inquiries", "locale": "en-GB", "region": "United Kingdom", "websiteType": "business", "adminRequired": true, "adminRequirementSource": "user", "modules": ["services", "cases", "inquiries", "categories"] } Two fields deserve attention. adminRequired forces the admin decision up front, in writing — if a project has no admin area, the generator omits the management pages, APIs, admin data models, and admin credentials entirely rather than scaffolding them and leaving them for you to delete. And region/locale are not decoration: the skill's SMS recommendations are based on merchant country and recipient destinations, and its shipping recommendations on merchant country, warehouse origin, and destination.
Inside the agent, the equivalent conversational request looks like this (this is the skill's own documented example):
Use $web-builder to build a website for a repair company serving the UK. The site should be in English, with services, case studies, bookings, customer inquiries, and an admin area. Help me choose frontend and admin templates, implement and verify the workflows, and deliver a local project first. Step 2: Preview the composition before generating anything
python scripts/composition.py --brief ../brief.json The composition resolver takes the website type, the explicit modules, their dependencies and exclusions, and the admin decision, and produces a plan you can inspect before a single file is generated. This is the cheapest point in the whole process to catch a scope mistake — say, asking for a directory and assuming multi-seller transactions come with it. They don't; that's marketplace, with seller onboarding, commissions, and settlement, and the type definitions are explicit about the boundary.
Step 3: Choose templates, with the entitlement check in the open
python scripts/skillux.py catalog --role frontend --industry services python scripts/skillux.py catalog --role admin python scripts/skillux.py check <template-slug> python scripts/skillux.py fetch <template-slug> --role frontend --project ../example-site You pick the frontend design first, then the admin design, from the Skillux catalog with previews where available. check verifies your account actually has access to a template before fetch downloads it into the project's private template directory. Installing the skill does not grant the template library and nothing gets purchased automatically; if entitlement is missing, the flow sends you to the template's page to sort it out and only continues after access is granted server-side. Skip the admin catalog entirely if the project has no admin area.
Step 4: Generate the foundation and run it
python scripts/create_project.py ../example-site --brief ../brief.json cd ../example-site npm install npm run setup npm run dev Generate into an empty directory outside the skill repository — the generator refuses to overwrite a nonempty directory, and it does not migrate existing applications. The executable standard foundation today is Next.js, TypeScript, Prisma, and SQLite, with site settings and optional admin scaffolding. If you enabled admin, it lives at /admin, and the generated credentials are in the project's LOCAL_ACCESS.md. Keep that file and .env private; they are the keys to the local site.
Step 5: Verify workflows, not just the build
The skill records everything in .web-builder/project.json: the original brief, the composition plan, the actual template versions used, implementation status, and checks. Statuses are kept honest on purpose — pending means implementation is still required, scaffolded means a foundation exists, and a business workflow can only be marked complete after its checks pass.
# inside the generated project npm run typecheck npm test npm run build Then go past the build. Submit the inquiry form and confirm the record is actually saved. Log in as an administrator and as a customer and confirm the permissions differ. Submit the form with bad input and read the error state. The repository's own verification guidance is blunt about this: a successful build does not prove every business workflow works, and HTTP checks should run against isolated local test projects, with provider sandboxes or local sinks for external services.
Four traps that cost people an afternoon
- Selecting a module does not implement it. A module in the brief is a plan plus instructions loaded at implementation time. Only the
standardandcommercefoundations are executable scaffolds today; the rest is guided implementation, and the project record tracks which state each piece is in. -
websiteType: "commerce"does not switch the foundation. For the commerce foundation (example products, SKUs, stock, cart, orders, access keys, simulated payments), the brief must explicitly includeordersand a three-lettercurrency, and you add--foundation commerceto the preview and generation commands. - Simulated payments do not charge money. Real payments, SMS, email, and shipping each need valid provider configuration and their own verification. An unconfigured service should show up as a blocker in the handover, not as a surprise after launch.
- Single-page sites need an explicit admin decision. For
landing, setadminRequireddeliberately —falsegives you a genuinely admin-free project instead of a site with a forgotten/adminroute.
What you end up with
A local, runnable project: the frontend and admin templates you chose, integrated against shared data and authentication; the business workflows from the brief implemented and checked; and a project.json that says what is verified and what is still pending. Deployment is a separate step, on your terms. When you come back to the project next week, the agent reads .web-builder/project.json first and reuses the recorded language, template, module, and provider decisions instead of interviewing you again.
If you want the guided version of this flow, the Web Builder overview on Skillux lays out the same brief-to-verified-handover path, and you can get the Web Builder skill on Skillux itself — it is listed there free — or install it straight from GitHub as shown above.
I work on Skillux, a catalog and marketplace of AI design skills for Claude Code, Cursor, and Codex. Web Builder is the skill we built for going from a business brief to a complete, verified website inside your coding agent.