Dev.to AI 🤖 Ai 👁 0 📖 6 min read

From Prompt to a Full Website: A Practical Workflow for AI Coding Agents

The prompt is the smallest part of building a website with a coding agent. What decides whether you get a demo or a working site is the workflow wrapped around the prompt: how the requirements get written down, which dec

The prompt is the smallest part of building a website with a coding agent. What decides whether you get a demo or a working site is the workflow wrapped around the prompt: how the requirements get written down, which decisions get locked before generation starts, and how the result gets checked. Below is the workflow I use, structured the way the Web Builder skill structures it — a skill that installs into Claude Code, Cursor, or Codex and takes a site from brief to verified handover. The steps transfer even if you never install it; the skill just makes them hard to skip.

Step 1: Write a brief your future self can argue with

A prompt like "build a website for my repair company" leaves every real decision to improvisation. A brief writes them down. Web Builder takes the brief as a JSON file with fields like brand, business, locale, region, websiteType, adminRequired, and modules — and each field earns its place. region and locale drive concrete recommendations later: which SMS providers make sense given the merchant's country and where recipients are, which shipping APIs fit the warehouse origin and destinations. adminRequired forces a decision most people postpone until it is expensive.

The conversational version of the same brief, from the skill's own documentation:

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.

Note what is in there: audience and market, the workflows (bookings, inquiries — not "pages"), the admin decision, and the delivery target (a local project first). That is the level of specificity that survives contact with generation.

Step 2: Lock the scope as a composition, and preview it

Web Builder defines scope as a website type plus functional modules. There are 11 types — a repair company is business; a shop is commerce; a listing site is directory — and 26 modules, from inquiries, bookings, and content to payments, shipping, subscriptions, and entitlements. Before anything is generated, a composition resolver checks the combination: dependencies pulled in, exclusions honored, the admin decision applied, and a plan previewed for your review.

This preview step is where scope misunderstandings die cheaply. The type definitions are deliberately blunt about boundaries: a listing directory does not automatically include multi-seller transactions, and a course presentation site does not automatically include a full learning platform. Finding that out in a plan costs a minute. Finding it out after generation costs a rebuild.

Step 3: Choose the designs — frontend first, admin second, access checked

With scope locked, the agent searches the Skillux template catalog by role and industry, and you choose a frontend design from real options, then an admin design if the project has an admin area. Two details of this step matter more than they sound. First, entitlement is checked before a template downloads — no building half a site on a design you cannot use. Second, covers and previews are labeled as what they are: a cover is a showcase image, and only an actual preview shows you the design you are committing to. If the project is admin-free, this step is shorter by design: no admin template, and the generator omits the admin pages, APIs, data models, and credentials entirely.

Step 4: Generate the foundation, then implement — and know which is which

Generation scaffolds the application foundation. Web Builder ships two executable foundations today: standard (Next.js, TypeScript, Prisma, SQLite, site settings, optional admin) and commerce (example products, SKUs, stock, cart, orders, access keys, simulated payments). Everything else in the module catalog is implemented by the agent following the skill's instructions, guided and checked, but written for your project.

Keeping those two verbs separate — generated versus implemented — is the difference between a workflow and a magic trick. The skill's project record, .web-builder/project.json, tracks the distinction per item: pending means work is still required, scaffolded means a foundation exists, and a workflow counts as complete only when its checks pass. One practical gotcha lives here too: choosing the commerce type does not by itself select the commerce foundation — the brief must explicitly include the orders module and a three-letter currency, and generation takes a --foundation commerce flag. Simulated payments, it should go without saying but apparently must, do not charge anyone.

Step 5: Run the acceptance pass like a skeptic

A green build is the start of verification, not the end of it. The generated project's own checks come first:

npm run typecheck
npm test
npm run build

Then test the workflows the way a user will break them:

  • Submit every form with real and with bad input. The inquiry form should save a record you can find, and reject invalid input with an error state a person can act on — not a silent failure, not a stack trace.
  • Look at the empty states. A bookings list with no bookings, a shop with no products, search with no results. These are the screens your first visitors will actually meet, and the ones generation most often skips.
  • Check both sides of the login. Sign in as an administrator and as a customer. Admin-only actions should be unreachable for the customer account, not just hidden from its menu.
  • Exercise the loading and failure paths. Slow the network down. Disconnect a provider. A site where an unconfigured payment or SMS service fails loudly at handover is a site you can finish; one where it fails silently in production is not.
  • Check the unglamorous pages. Pagination with more items than one page holds, the site on a phone-width viewport, text contrast on the template's lighter sections.

Run automated HTTP checks only against an isolated local copy of the project, and point external services at sandboxes or local sinks while testing. The deliverable at the end is a local project plus a status record that says, item by item, what passed and what still needs attention — including the external services still waiting on real credentials. That list is part of the handover, not an embarrassment to hide.

Step 6: Make the next session start from the record, not from memory

Websites are rarely finished in one sitting, and the second session is where agent-built projects usually unravel — the agent re-asks settled questions or quietly makes different choices. The fix is boring and effective: the project record persists. When you return, the agent reads .web-builder/project.json and the existing code first, and reuses the recorded language, template, module, and provider decisions. Your job in session two is to describe the change, not to re-litigate the brief.

The workflow in one paragraph

Brief in writing, with the market and the admin decision in it. Scope as an explicit composition, previewed before generation. Designs chosen in order, access verified before download. Generation and implementation tracked as different states. Acceptance done at the level of user actions — submit, log in, fail, empty — not just a passing build. And a project record that lets the next session continue instead of restart. None of these steps require Web Builder specifically; they require refusing to let a single prompt carry decisions it cannot hold. The skill exists so the refusal is automatic.

If you want to see the whole flow laid out as a product, the Web Builder overview on Skillux covers the brief-to-handover path step by step, and the Web Builder skill on Skillux is free to install into your agent.

I work on Skillux, a catalog and marketplace of AI design skills for Claude Code, Cursor, and Codex. Skills like Web Builder are how we package workflows like this one — brief, build, verify — so an agent can repeat them instead of reinventing them per project.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.