by skillux-hub
A modular website-building skill for AI coding agents, covering 11 website types and 26 functional modules, with Skillux template selection, frontend and admin integration, workflow validation, and country-aware SMS and shipping SDK/API recommendations.
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
# Add to your Claude Code skills
git clone https://github.com/skillux-hub/web-builderGuides for using ai agents skills like web-builder.
Turn a business brief into a working local website with selected Skillux designs and connected workflows. Communicate in the user's language; website language and market follow their own requirements. A static template, generated foundation, or menu is not an implemented business system.
For an actual website-building run, complete the Skillux startup login gate before requirements intake, template recommendations, generation or implementation. Run python "<skill>/scripts/skillux.py" login: it verifies the current session, opens official browser authorization if needed, waits for approval and rechecks the server. Do not merely tell the user to log in or continue while approval is pending. Reuse a verified session without asking for authorization again. Network/unknown-access failures remain blockers, not proof that login or purchase is required.
Check the existing app and .web-builder/project.json first. Reuse choices, downloaded versions, and check results; do not reinitialize or overwrite work. Follow Business requirements for the brief and defaults. Ask only questions whose missing answers change the current work.
Classify by primary customer workflow using Website types:
| Type | Read when |
|---|---|
| Landing | Single-page campaigns and simple presentations |
| Business | Company, services, cases and multi-page portfolios |
| Commerce | Actual online selling/ordering |
| Content | Publishing, articles, magazines, portfolios |
| Booking | Appointments, reservations, event registration |
| Education | Courses, enrollment, learning delivery |
| Directory | Searchable listings and publisher submissions |
| Dashboard | Data consoles, SaaS workspaces, internal tools |
| Tool | Calculators, AI tools, conversion and execution workflows |
| Community | Forums, questions/answers and member-generated discussions |
| Marketplace | Independent sellers/providers transacting through a platform |
Read one primary type; add a secondary type only for a requested hybrid workflow. Industry and template appearance do not determine type. Record websiteType and optional additionalWebsiteTypes in the brief without changing existing module IDs. Unlisted domains can compose the nearest applicable workflows.
Determine admin need before admin selection: ask for single-page sites unless already answered; otherwise include admin by default unless explicitly declined. Record adminRequired and its source. Preserve an existing decision.
When the selected scope includes categories/classification (taxonomy), implement the classification module as a working management workflow with persisted business associations. Include a dedicated admin entry when admin is enabled. Hierarchical categories require a clear, polished interactive tree with expand/collapse, contextual add-child actions and named ancestor paths in pickers; a category text field, flat list hiding parent relationships, or menu placeholder does not complete this module.
Use Functional modules to select and load only relevant rules. Each module owns its data, actions, states, dependencies, and acceptance:
For SMS selection, use Country-based SDK recommendations to suggest two or three providers from the user's/merchant's known country and actual recipient destinations, preserving existing provider choices.
For shipping selection, use Country-and-route SDK/API recommendations. Start from the user's/merchant's known country, then qualify warehouse origin -> destination and required fulfillment capabilities. Distinguish official SDKs from official REST adapters and preserve established provider choices.
Use Executable composition and scripts/composition.py --brief <brief.json> to preview resolved scope. config/catalog.json owns presets, dependencies, exclusions, and asset layers. Record selection sources; planned modules are not implemented features. Ecommerce requires Payments without asking again whether payments are needed. Establish payment need for other businesses. Shipping follows actual origin/destination and fulfillment needs. Template widgets do not authorize either module. Admin-only login does not require customer accounts.
Read Skillux discovery and downloads. Recommend 3–5 suitable frontend packs with real covers/previews, style/fit, and purchase status. A cover is product artwork; disclose missing previews. Offer another selection when requested. The user chooses appearance unless they authorize agent selection.
After frontend selection, recommend an industry-neutral admin design if admin is needed and explain selected management modules. If the requested dashboard already is the management interface, avoid selecting a duplicate workbench for the same purpose. Check every selected slug with check; owned lists licenses, not a catalog pass. Follow the selected-template entitlement gate: when the server confirms purchase is required, proactively open the real detail page, explain buying the template or an applicable membership, and wait until a new server check grants access. Do not advance to generation/download/implementation for that selection while it remains denied. The user completes any purchase; do not buy automatically or assume every membership covers every template.
python "<skill>/scripts/skillux.py" catalog --role frontend --industry fashion
python "<skill>/scripts/skillux.py" catalog --role admin
python "<skill>/scripts/skillux.py" check <slug>
Read Implementation and continuation. Save nonsensitive requirements JSON, generate only for new projects, and download selected templates privately. Default to Next.js, TypeScript, Prisma, and SQLite; retain compatible existing architecture. standard is industry-neutral; choose commerce only for explicit selling/ordering with orders and a confirmed currency.
python "<skill>/scripts/create_project.py" "<new-project>" --brief "<brief.json>"
python "<skill>/scripts/skillux.py" fetch <frontend-slug> --role frontend --project "<project>"
python "<skill>/scripts/skillux.py" fetch <admin-slug> --role admin --project "<project>"
Skip admin downloads when not needed. Set adminRequired: false before generation to omit admin assets, routes, models, and credentials. Single-page generation requires an explicit admin decision. Existing projects are not automatically migrated. Read template instructions/generators and migrate real pages/assets; an iframe or brand replacement is insufficient. Protect shared backend code, credentials, and existing work.
For each selected module, connect frontend -> server validation -> persisted data -> admin/operational workflow when applicable. Keep /, /admin, and /admin/login layouts and customer/admin sessions independent. Load the module rules while implementing its surfaces: real pagination for lists, shared image uploads/pickers with proper request limits, rich text with safe rendering, derived page SEO, and working admin governance. Do not create unrequested commerce features in other types.
The generator supplies foundations, not selected business modules or template integration. Keep businessImplementation and templateIntegration pending until their actual checks pass. Remove fake handlers from connected features; disclose missing payment, shipping, identity, email, and storage configuration.
When admin is enabled, complete the authenticated admin acceptance gate before delivery. Opening the login screen is insufficient: enter the signed-in workbench, wait for real data on each implemented management page, exercise key saves and refresh persistence, and verify server authorization. Record unexecuted checks explicitly; do not report the backend as working from build or login-entry checks alone.
Read Verification, applying shared checks plus only selected module/type checks. Exercise key actions in isolated local data or sandboxes and verify visible feedback, server results, persistence, authorization, failure cases, and relevant concurrency. Build/typechecks/screenshots alone do not prove working behavior. Inspect actual desktop/mobile pages and text/background contrast after design migration.
Record checks and cleanup in continuation state, distinguishing verified interaction, compile/visual-only, unexecuted, and blocked work. Deliver the complete local project with absolute path, startup/access instructions, template versions, results, and remaining configuration. Deployment and purchases are not default delivery actions.
Do not bundle the remote template library or alter purchase records. If the catalog is unavailable, preserve requirements/selections and report the blocker. Use legitimate local templates when specified by the user.
English | 简体中文
A business website-building skill for AI coding agents. Define the scope through website types × functional modules, choose Skillux design templates, generate an application foundation, connect business workflows, and verify the result.
Web Builder is listed free on Skillux: https://skillux.dev/skills/web-builder — install steps, files, and the free price are on the product page. Overview: https://skillux.dev/web-builder
Use it to create template-based websites or continue projects built with this skill. Start with SKILL.md; executable presets and dependencies live in config/catalog.json.
Skillux login → Business requirements → Website type → Functional modules → Frontend/admin templates → Implementation → Verification and delivery
Install through the Skills CLI and choose your agent and installation scope as prompted:
npx skills add https://github.com/skillux-hub/web-builder --skill web-builder
Alternatively, clone the repository and install the complete directory using your agent's skill installation method. Preserve the relative structure of SKILL.md, references, config, scripts, and assets.
Example request:
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.
For an existing project, describe the change you need. The agent first reads .web-builder/project.json and the application code, reusing recorded language, template, module, and provider decisions.
| Type ID | Workflow |
|---|---|
landing |
Single-page presentations, campaigns, and product launches |
business |
Company sites, services, case studies, and multi-page portfolios |
commerce |
Product sales and fulfillment for a single operator |
content |
Blogs, publications, knowledge content, and portfolios |
booking |
Appointment slots, date-range reservations, and event capacity |
education |
Course presentation, enrollment, and online learning |
directory |
Categorized listings, discovery, and contact |
dashboard |
Data consoles, operations, and workspaces |
tool |
Calculators, AI tools, file conversion, and execution results |
community |
Forums, Q&A, member content, and moderation |
marketplace |
Seller onboarding, transactions, commissions, and settlement |
See the website type index for scope, module mappings, and acceptance scenarios. A listing directory does not automatically include multi-seller transactions; a course presentation site does not automatically include a full learning platform.
| Capability group | Module IDs |
|---|---|
| Administration and identity | admin, authentication, tenancy |
| Content and organization | content, taxonomy, search, seo |
| Lists and resources | lists, media, files |
| Transactions and fulfillment | commerce, payments, shipping, after-sales |
| Customers and learning | inquiries, bookings, learning |
| Periods and access | subscriptions, entitlements |
| Notifications and channels | notifications, sms |
| Platforms and execution | directory, execution, community, marketplace, analytics |
The module index defines selection criteria, dependencies, and acceptance rules. Categories and tags use taxonomy; payments manage transactions, subscriptions manage periods, and entitlements control access to features, content, and usage allowances.
Provider guides: SMS SDK recommendations · Shipping SDK/API recommendations. A recommendation does not establish an active account, route coverage, or a completed integration.
| Component | Current scope |
|---|---|
| Composition resolver | Website types, explicit modules, dependencies, exclusions, aliases, and admin decisions; supports plan previews |
standard foundation |
Next.js, TypeScript, Prisma, SQLite, site settings, and optional admin scaffolding |
commerce foundation |
Example products, SKUs, stock, cart, orders, access keys, simulated payments, and optional admin scaffolding |
| Skillux tools | Catalog discovery, entitlement checks, selected template downloads, and version recording |
| Other business modules | Instructions loaded as needed for implementation and verification, rather than completed installable plugins |
Selecting a module does not implement it, and generating a foundation does not complete a website. Selected templates still require real migration. Payments, SMS, email, shipping, and other external services require valid configuration and verification. Simulated payments do not charge money. The generator does not automatically supply seller isolation, settlements, or booking engines.
The generation tools require Python 3.10+. Generated applications require Node.js 22.12+, npm, and an environment that supports SQLite native dependencies. Additional SDKs may have higher runtime requirements; check the chosen version before integration.
git clone https://github.com/skillux-hub/web-builder.git
cd web-builder
Save a brief outside the repository, for example as ../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"]
}
From the repository root, pass the login gate, preview the composition, and generate into an empty directory outside the repository. When using selected templates, their access checks must pass before generation:
python scripts/skillux.py login
python scripts/composition.py --brief ../brief.json
python scripts/create_project.py ../example-site --brief ../brief.json
cd ../example-site
npm install
npm run setup
npm run dev
Open the local URL shown in the terminal. If admin is enabled, visit /admin; generated credentials are in the project's LOCAL_ACCESS.md. Keep that file and .env private.
For the commerce foundation, explicitly include orders and a three-letter currency code in the brief, and add --foundation commerce to the preview/generation commands. Setting websiteType: "commerce" alone does not switch the executable foundation. Single-page sites require an explicit adminRequired decision; set it to false for an admin-free project.
The generator refuses to overwrite nonempty directories and does not automatically migrate existing applications. See composition configuration and implementation guidance for full input and continuation rules.
Web Builder verifies the Skillux session before starting. Missing or expired login opens official browser authorization and waits for approval. Once a template is selected, confirmed missing entitlement opens its detail page so the user can buy the template or an applicable membership/pass. The workflow continues only after server-side access is granted. The underlying public catalog endpoint remains anonymous:
python scripts/skillux.py login
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
Skip admin templates when no admin area is needed. The Skillux CLI manages login credentials; do not put them in briefs or project records. Downloads remain in the project's private template directory. This repository does not bundle the remote template library or purchase templates automatically. See Skillux discovery and entitlement.
.web-builder/project.json records the original brief, composition plan, actual template versions, implementation status, and checks. pending means implementation is still required; scaffolded means a foundation exists. Business implementation and template integration can be marked complete only after their corresponding checks pass.
Run Python checks from the skill repository:
python -B -m unittest discover -s tests -v
Run application checks inside a generated project:
npm run typecheck
npm test
npm run build
Key workflows also need verification of user actions, server results, persistence, permissions, and failures. A successful build does not prove every business workflow works. Use HTTP checks only against isolated local test projects, and prefer provider sandboxes or local sinks for external services. See verification guidance. Local project de
web-builder is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by skillux-hub. A modular website-building skill for AI coding agents, covering 11 website types and 26 functional modules, with Skillux template selection, frontend and admin integration, workflow validation, and country-aware SMS and shipping SDK/API recommendations. It has 0 GitHub stars.
web-builder's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/skillux-hub/web-builder" and add it to your Claude Code skills directory (see the Installation section above). web-builder ships a SKILL.md manifest, so compatible agents can discover and load it automatically.
web-builder is primarily written in TypeScript. It is open-source under skillux-hub on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh web-builder against similar tools.
No comments yet. Be the first to share your thoughts!