In This Article

Build with a Coding Agent

Go from a single prompt to a deployed Wix-managed Astro project. You describe what you want to build, and a coding agent on your computer creates the business, scaffolds the Astro project, and publishes the site. You continue from the project folder with the Wix CLI.

This is the Astro path, with the Wix CLI.

What you can build

With a single prompt, your agent can build and deploy a complete, working site backed by Wix business solutions: a store, a booking system, a blog, and more.

Describe what you want in plain language:

Build a storefront for handmade ceramics with a product catalog and checkout. (Wix Stores)
Build a booking site for a yoga studio with class schedules and online payments. (Wix Bookings)
Build an events page that sells tickets. (Wix Events)
Build a portfolio site for an architecture firm, with projects managed in a CMS. (Wix CMS)
Build a membership site for a fitness coach with gated, members-only content. (Wix Members)

The agent reads your prompt, picks the solutions your site needs, and installs them for you. This is a starting point, not a limit: because the skill reads Wix's live documentation, your agent can discover and wire up any Wix business solution, not just the common ones. If you need something specific, name it in your prompt, or paste a link to the relevant Wix documentation for the agent to read. Learn more about featured business solutions for Wix Headless.

Tip: The more detail you give, such as the desired pages, data, and design, the more complete the result. For ready to adapt examples, see the prompt recipes.

Before you begin

Make sure you have:

A Wix account. If you don't have one, sign up.
A coding agent such as Claude Code, Cursor, Codex, or GitHub Copilot in VS Code.
Node.js (v24.22.1 or higher), to continue with the Wix CLI. The agent installs it when it can.

Step 1 | Build with a single prompt

The Wix Headless skill tells your coding agent how to create the business, scaffold an Astro project, and publish it on Wix.

Caution: This path always provisions a new business and site. If you already have a project, from the self-managed quick start or a dashboard-created headless client, this flow can't attach to it. If you paste an existing siteId or clientId into your prompt, the agent won't use it, and you'll end up with 2 separate, unrelated Wix projects. To use a project you already have, leave the skill URL out of your prompt. Call the JavaScript SDK or the REST API with that project's site ID and client ID.

In your coding agent, describe what you want to build and include the skill URL. For example:

Copy

The agent provisions the business and site, scaffolds the Astro project in a folder on your computer, and publishes the frontend. For more detailed, ready-to-adapt prompts, see Prompt recipes. To understand what happens between your prompt and the deployed site, see How it works.

You can tell the skill is working when the agent asks you to log in to Wix, reports that it provisioned a site, and names the business solutions it installed.

Step 2 | Find your project

Your project appears in your Wix dashboard alongside your sites. Open your dashboard to view the live URL, manage the site, or connect a custom domain.

The agent saves the Astro project in a folder on your computer. Ask it where it saved the project. You continue from that folder with the Wix CLI. Edit Frontend doesn't open these Astro sites in another tool.

Step 3 (Recommended) | Install the Wix plugin for ongoing work

The single-prompt skill is enough to scaffold and deploy. For ongoing development, install the Wix plugin in your AI client. It adds Wix Skills and the Wix MCP together, giving your agent persistent Wix context so it can search Wix docs, scaffold code, and call Wix APIs directly from your chat.

Step 4 | Keep building

Keep prompting the agent in the project folder to add features and functionality. Define your data model, add authentication, build UI, and redeploy.

To preview and publish from that folder, run npx wix preview, then npx wix release.

You don't need to stay in the same chat to keep working. Start a new chat in the project folder and tell the agent what you want to change. Site Settings in the dashboard has Publish and Unpublish. After you release from the project folder, publish further updates with npx wix release.

How it works

A lot happens between your prompt and the deployed result. You don't run any of it yourself, but knowing the sequence helps you follow along, tell when something has gone wrong, and steer the agent toward the site you want.

From your prompt to a deployed site

You describe what you want. Your prompt, plus the skill URL, is the whole input. The more detail you give about pages, data, and design, the more complete the result.
The agent gets set up. It checks your environment and installs the skill. If necessary, the agent logs you in to Wix. Logging in happens once in your browser: the agent shows you a link and a code to confirm, then continues on its own.
The agent works out what to build. In this discovery phase, it reads your prompt and infers the business solutions you need, a brand and tone for the content, and how much example content to create. This is where it might ask you to make a choice.
The agent provisions and builds. It creates the Wix business and site, installs the business solutions your project needs, seeds realistic example content, and builds the frontend so that every page connects to your live Wix backend instead of to mock data.
The agent deploys. It publishes the site to Wix hosting and gives you a live URL. It saves the Astro project as a folder on your computer, and you continue from that folder with the Wix CLI.

Questions the agent might ask

The skill runs with little back-and-forth, but the agent pauses when a choice is genuinely yours to make. Common examples:

Imagery. Choose whether the agent generates AI images for your content and pages or uses styled placeholder graphics instead. Generated images look richer but cost roughly 1 Wix AI credit each. Placeholders are free and easy to replace with your own photos later.
An ambiguous request. If your prompt could point to several business solutions or your intent isn't clear, the agent asks you to clarify rather than guess.

Answer in plain language. If the agent doesn't ask about something you care about, such as a specific business solution, a data schema, or a design direction, say so in your prompt up front instead of waiting for the agent to ask.

Best practices

For the best result, follow these best practices:

Structure your prompt. Group your requirements into functionality, pages, and design so the agent can work through them methodically.
Name your data and its schema. Specify required collection names and fields with their types. For example, a 'projects' collection with Project Name (text), Main Image (image), and Location (text).
Ask to seed example content. Request realistic sample data so the site looks complete out of the box and is easy to review.
Specify Wix business solutions. If you know you need Wix Stores, Bookings, Blog, or the CMS, say so to point the agent at the right APIs.
Mention authentication early. If members need to log in, say so up front so the agent sets it up from the start.
Describe behavior, not structure. Tell the agent what site visitors should be able to do, and let it choose the implementation.
Call out responsiveness and accessibility. Ask for a mobile-friendly layout, good color contrast, and alt text so the result is production-ready.
Iterate. Build the smallest working version first, then keep prompting to extend it.

Troubleshooting

Because the agent infers a lot from a short prompt, the first result doesn't always match what you pictured. These are some common gaps and how to close them:

You got a site that isn't connected to Wix. The skill URL was probably missing from your prompt, so the agent built a generic mockup or a bare scaffold instead. Check your Wix dashboard: if no new site appears, start again with the skill URL included.
You got the wrong business solution. The agent inferred a different solution than you intended, such as a static schedule instead of real bookings. To fix this, follow up in the agent chat and tell it explicitly which solution to use, such as asking it to power the class schedule with Wix Bookings rather than a static list. Naming the solution removes the guesswork.
You want to add another solution. You don't have to start over. Ask the agent to add it, such as a blog or a contact form. It installs the solution, seeds content, and builds the new pages on the existing site. Make that request in the project folder.
You're not sure what the agent did. Ask it. It can tell you which business solutions it installed, what content it seeded, and where it saved the project folder. You can confirm the site from your Wix dashboard.
Something else went wrong, or you're stuck. Ask your agent to help. It has your project context, so it can inspect the code, explain what it did, and often diagnose and fix the problem itself.

Prompt recipes

A short prompt gets you started, but a detailed one gets you a finished site. The recipes below show how to structure a thorough prompt: group your requirements into functionality, pages, and design, name your data up front, and ask the agent to seed realistic example content.

Portfolio site with a CMS

Copy

Online store with Wix Stores

Copy