<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: aidy029</title>
    <description>The latest articles on DEV Community by aidy029 (@aidy029).</description>
    <link>https://dev.to/aidy029</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4252722%2F6584c6f0-dbe9-4f2a-bc6a-7af0bfb8f5ff.png</url>
      <title>DEV Community: aidy029</title>
      <link>https://dev.to/aidy029</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aidy029"/>
    <language>en</language>
    <item>
      <title>From Prompt to a Full Website: A Practical Workflow for AI Coding Agents</title>
      <dc:creator>aidy029</dc:creator>
      <pubDate>Thu, 19 Nov 2026 00:54:35 +0000</pubDate>
      <link>https://dev.to/aidy029/from-prompt-to-a-full-website-a-practical-workflow-for-ai-coding-agents-1npk</link>
      <guid>https://dev.to/aidy029/from-prompt-to-a-full-website-a-practical-workflow-for-ai-coding-agents-1npk</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Write a brief your future self can argue with
&lt;/h2&gt;

&lt;p&gt;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 &lt;code&gt;brand&lt;/code&gt;, &lt;code&gt;business&lt;/code&gt;, &lt;code&gt;locale&lt;/code&gt;, &lt;code&gt;region&lt;/code&gt;, &lt;code&gt;websiteType&lt;/code&gt;, &lt;code&gt;adminRequired&lt;/code&gt;, and &lt;code&gt;modules&lt;/code&gt; — and each field earns its place. &lt;code&gt;region&lt;/code&gt; and &lt;code&gt;locale&lt;/code&gt; 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. &lt;code&gt;adminRequired&lt;/code&gt; forces a decision most people postpone until it is expensive.&lt;/p&gt;

&lt;p&gt;The conversational version of the same brief, from the skill's own documentation:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;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.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Lock the scope as a composition, and preview it
&lt;/h2&gt;

&lt;p&gt;Web Builder defines scope as a website type plus functional modules. There are 11 types — a repair company is &lt;code&gt;business&lt;/code&gt;; a shop is &lt;code&gt;commerce&lt;/code&gt;; a listing site is &lt;code&gt;directory&lt;/code&gt; — and 26 modules, from &lt;code&gt;inquiries&lt;/code&gt;, &lt;code&gt;bookings&lt;/code&gt;, and &lt;code&gt;content&lt;/code&gt; to &lt;code&gt;payments&lt;/code&gt;, &lt;code&gt;shipping&lt;/code&gt;, &lt;code&gt;subscriptions&lt;/code&gt;, and &lt;code&gt;entitlements&lt;/code&gt;. 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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Choose the designs — frontend first, admin second, access checked
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Generate the foundation, then implement — and know which is which
&lt;/h2&gt;

&lt;p&gt;Generation scaffolds the application foundation. Web Builder ships two executable foundations today: &lt;code&gt;standard&lt;/code&gt; (Next.js, TypeScript, Prisma, SQLite, site settings, optional admin) and &lt;code&gt;commerce&lt;/code&gt; (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.&lt;/p&gt;

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

&lt;h2&gt;
  
  
  Step 5: Run the acceptance pass like a skeptic
&lt;/h2&gt;

&lt;p&gt;A green build is the start of verification, not the end of it. The generated project's own checks come first:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm run typecheck
npm &lt;span class="nb"&gt;test&lt;/span&gt;
npm run build
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then test the workflows the way a user will break them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Submit every form with real and with bad input.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Look at the empty states.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check both sides of the login.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exercise the loading and failure paths.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check the unglamorous pages.&lt;/strong&gt; Pagination with more items than one page holds, the site on a phone-width viewport, text contrast on the template's lighter sections.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Make the next session start from the record, not from memory
&lt;/h2&gt;

&lt;p&gt;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 &lt;code&gt;.web-builder/project.json&lt;/code&gt; 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.&lt;/p&gt;

&lt;h2&gt;
  
  
  The workflow in one paragraph
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;If you want to see the whole flow laid out as a product, the &lt;a href="https://skillux.dev/web-builder" rel="noopener noreferrer"&gt;Web Builder overview on Skillux&lt;/a&gt; covers the brief-to-handover path step by step, and &lt;a href="https://skillux.dev/skills/web-builder" rel="noopener noreferrer"&gt;the Web Builder skill on Skillux&lt;/a&gt; is free to install into your agent.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I work on &lt;a href="https://skillux.dev" rel="noopener noreferrer"&gt;Skillux&lt;/a&gt;, 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.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>claudecode</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Build a Complete Website with Claude Code Using a Web Builder Skill</title>
      <dc:creator>aidy029</dc:creator>
      <pubDate>Thu, 19 Nov 2026 00:16:59 +0000</pubDate>
      <link>https://dev.to/aidy029/how-to-build-a-complete-website-with-claude-code-using-a-web-builder-skill-1ccg</link>
      <guid>https://dev.to/aidy029/how-to-build-a-complete-website-with-claude-code-using-a-web-builder-skill-1ccg</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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 &lt;a href="https://github.com/skillux-hub/web-builder" rel="noopener noreferrer"&gt;Web Builder&lt;/a&gt;, 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.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a skill actually is
&lt;/h2&gt;

&lt;p&gt;A skill is a directory your coding agent loads as working instructions. Web Builder's repository has &lt;code&gt;SKILL.md&lt;/code&gt; at the root as the entry point, plus &lt;code&gt;references/&lt;/code&gt; (type and module definitions, implementation and verification guidance), &lt;code&gt;config/&lt;/code&gt; (the catalog of types, modules, and dependencies), &lt;code&gt;scripts/&lt;/code&gt; (the executable tooling), &lt;code&gt;assets/&lt;/code&gt; (foundation layers), and &lt;code&gt;tests/&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Scope is defined as &lt;strong&gt;website types × functional modules&lt;/strong&gt;. There are 11 types — &lt;code&gt;landing&lt;/code&gt;, &lt;code&gt;business&lt;/code&gt;, &lt;code&gt;commerce&lt;/code&gt;, &lt;code&gt;content&lt;/code&gt;, &lt;code&gt;booking&lt;/code&gt;, &lt;code&gt;education&lt;/code&gt;, &lt;code&gt;directory&lt;/code&gt;, &lt;code&gt;dashboard&lt;/code&gt;, &lt;code&gt;tool&lt;/code&gt;, &lt;code&gt;community&lt;/code&gt;, &lt;code&gt;marketplace&lt;/code&gt; — and 26 modules grouped by concern: &lt;code&gt;admin&lt;/code&gt;, &lt;code&gt;authentication&lt;/code&gt;, &lt;code&gt;tenancy&lt;/code&gt;; &lt;code&gt;content&lt;/code&gt;, &lt;code&gt;taxonomy&lt;/code&gt;, &lt;code&gt;search&lt;/code&gt;, &lt;code&gt;seo&lt;/code&gt;; &lt;code&gt;commerce&lt;/code&gt;, &lt;code&gt;payments&lt;/code&gt;, &lt;code&gt;shipping&lt;/code&gt;, &lt;code&gt;after-sales&lt;/code&gt;; &lt;code&gt;inquiries&lt;/code&gt;, &lt;code&gt;bookings&lt;/code&gt;, &lt;code&gt;learning&lt;/code&gt;; &lt;code&gt;subscriptions&lt;/code&gt;, &lt;code&gt;entitlements&lt;/code&gt;; &lt;code&gt;notifications&lt;/code&gt;, &lt;code&gt;sms&lt;/code&gt;; and a few platform ones (&lt;code&gt;directory&lt;/code&gt;, &lt;code&gt;execution&lt;/code&gt;, &lt;code&gt;community&lt;/code&gt;, &lt;code&gt;marketplace&lt;/code&gt;, &lt;code&gt;analytics&lt;/code&gt;). You compose the modules your site needs instead of bolting commerce or membership onto every project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Install
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx skills add https://github.com/skillux-hub/web-builder --skill web-builder
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Pick your agent and install scope when prompted. Cloning the repo and installing the directory manually also works — just preserve the relative structure of &lt;code&gt;SKILL.md&lt;/code&gt;, &lt;code&gt;references&lt;/code&gt;, &lt;code&gt;config&lt;/code&gt;, &lt;code&gt;scripts&lt;/code&gt;, and &lt;code&gt;assets&lt;/code&gt;, because the scripts resolve paths against it.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Log in and write a brief, not a prompt
&lt;/h2&gt;

&lt;p&gt;Web Builder verifies a Skillux session before anything else, because template downloads later in the flow are entitlement-checked:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python scripts/skillux.py login
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then write the brief as a JSON file, saved outside the repository (for example &lt;code&gt;../brief.json&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"brand"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Example Services"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"business"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Service presentation, case studies, and customer inquiries"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"locale"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"en-GB"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"region"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"United Kingdom"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"websiteType"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"business"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"adminRequired"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"adminRequirementSource"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"user"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"modules"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"services"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"cases"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"inquiries"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"categories"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two fields deserve attention. &lt;code&gt;adminRequired&lt;/code&gt; 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 &lt;code&gt;region&lt;/code&gt;/&lt;code&gt;locale&lt;/code&gt; 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.&lt;/p&gt;

&lt;p&gt;Inside the agent, the equivalent conversational request looks like this (this is the skill's own documented example):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;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.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Step 2: Preview the composition before generating anything
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python scripts/composition.py --brief ../brief.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;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 &lt;code&gt;directory&lt;/code&gt; and assuming multi-seller transactions come with it. They don't; that's &lt;code&gt;marketplace&lt;/code&gt;, with seller onboarding, commissions, and settlement, and the type definitions are explicit about the boundary.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Choose templates, with the entitlement check in the open
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python scripts/skillux.py catalog --role frontend --industry services
python scripts/skillux.py catalog --role admin
python scripts/skillux.py check &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;template-slug&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
python scripts/skillux.py fetch &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;template-slug&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; --role frontend --project ../example-site
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You pick the frontend design first, then the admin design, from the Skillux catalog with previews where available. &lt;code&gt;check&lt;/code&gt; verifies your account actually has access to a template before &lt;code&gt;fetch&lt;/code&gt; 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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Generate the foundation and run it
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python scripts/create_project.py ../example-site --brief ../brief.json

&lt;span class="nb"&gt;cd&lt;/span&gt; ../example-site
npm install
npm run setup
npm run dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;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 &lt;code&gt;standard&lt;/code&gt; foundation today is Next.js, TypeScript, Prisma, and SQLite, with site settings and optional admin scaffolding. If you enabled admin, it lives at &lt;code&gt;/admin&lt;/code&gt;, and the generated credentials are in the project's &lt;code&gt;LOCAL_ACCESS.md&lt;/code&gt;. Keep that file and &lt;code&gt;.env&lt;/code&gt; private; they are the keys to the local site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Verify workflows, not just the build
&lt;/h2&gt;

&lt;p&gt;The skill records everything in &lt;code&gt;.web-builder/project.json&lt;/code&gt;: the original brief, the composition plan, the actual template versions used, implementation status, and checks. Statuses are kept honest on purpose — &lt;code&gt;pending&lt;/code&gt; means implementation is still required, &lt;code&gt;scaffolded&lt;/code&gt; means a foundation exists, and a business workflow can only be marked complete after its checks pass.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# inside the generated project&lt;/span&gt;
npm run typecheck
npm &lt;span class="nb"&gt;test&lt;/span&gt;
npm run build
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four traps that cost people an afternoon
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Selecting a module does not implement it.&lt;/strong&gt; A module in the brief is a plan plus instructions loaded at implementation time. Only the &lt;code&gt;standard&lt;/code&gt; and &lt;code&gt;commerce&lt;/code&gt; foundations are executable scaffolds today; the rest is guided implementation, and the project record tracks which state each piece is in.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;websiteType: "commerce"&lt;/code&gt; does not switch the foundation.&lt;/strong&gt; For the commerce foundation (example products, SKUs, stock, cart, orders, access keys, simulated payments), the brief must explicitly include &lt;code&gt;orders&lt;/code&gt; and a three-letter &lt;code&gt;currency&lt;/code&gt;, and you add &lt;code&gt;--foundation commerce&lt;/code&gt; to the preview and generation commands.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Simulated payments do not charge money.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Single-page sites need an explicit admin decision.&lt;/strong&gt; For &lt;code&gt;landing&lt;/code&gt;, set &lt;code&gt;adminRequired&lt;/code&gt; deliberately — &lt;code&gt;false&lt;/code&gt; gives you a genuinely admin-free project instead of a site with a forgotten &lt;code&gt;/admin&lt;/code&gt; route.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What you end up with
&lt;/h2&gt;

&lt;p&gt;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 &lt;code&gt;project.json&lt;/code&gt; 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 &lt;code&gt;.web-builder/project.json&lt;/code&gt; first and reuses the recorded language, template, module, and provider decisions instead of interviewing you again.&lt;/p&gt;

&lt;p&gt;If you want the guided version of this flow, the &lt;a href="https://skillux.dev/web-builder" rel="noopener noreferrer"&gt;Web Builder overview on Skillux&lt;/a&gt; lays out the same brief-to-verified-handover path, and you can get &lt;a href="https://skillux.dev/skills/web-builder" rel="noopener noreferrer"&gt;the Web Builder skill on Skillux&lt;/a&gt; itself — it is listed there free — or install it straight from GitHub as shown above.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I work on &lt;a href="https://skillux.dev" rel="noopener noreferrer"&gt;Skillux&lt;/a&gt;, 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.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>claudecode</category>
      <category>ai</category>
      <category>webdev</category>
      <category>nextjs</category>
    </item>
  </channel>
</rss>
