Go from a single prompt to a deployed Wix-managed headless project. You describe what you want to build, and your AI agent scaffolds the project, provisions the business and site, and deploys it for you. Then you keep prompting to extend it.
This is the fastest way to start. There's nothing to install to try it.
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)
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.
Make sure you have:
- Node.js (v20.11.0 or higher).
- A Wix account. If you don't have one, sign up.
- An AI client such as Claude Code, Cursor, Codex, or GitHub Copilot in VS Code.
The Wix Headless skill instructs your AI agent on how to scaffold and deploy a Wix-managed headless project using the Wix CLI. You don't need to install anything to use it.
In your AI client, describe what you want to build and include the skill URL. For example:
The agent provisions the business and site for you and scaffolds the local codebase in one step. For more detailed, ready-to-adapt prompts, see Prompt recipes. To understand what happens between your prompt and the deployed site, see How AI Agent Site Creation Works.
Your project lives in two places:
- On Wix: It appears in your Wix dashboard alongside your sites. Open your dashboard to view the live URL, manage the site, or connect a custom domain.
- On your computer: The project's code is saved as a folder. Your agent chooses where to put it, so if you're not sure, ask it where it saved the project and note the location. You'll need it to keep editing later.
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.
Keep prompting your agent to add features and functionality. Define your data model, add authentication, build UI, and redeploy. You can also continue developing manually with the Wix CLI at any time.
You don't need to stay in the same chat to keep working. To pick your project back up later, start a new chat with your agent in the project folder from Step 2 and tell it what you want to change. As long as the agent is working in that folder, it has your code and can keep building.
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.
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. In the same project folder, 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, connecting them to the existing site.
- You're not sure what the agent did. Ask it. The agent can tell you which business solutions it installed, what content it seeded, and where it saved your project folder. You can also confirm everything 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.
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.