Skip to main content
skill CX Codex

wix-headless-templates — Claude Code skill: install and what it does

wix-headless-templates is a Claude Code skill with ready Wix Headless code for business solutions: data layers, pages, and seeds. It supports agent-built sites based on templates.

MIT 301 installs ★ 40 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add wix/skills --skill wix-headless-templates -a claude-code
Open on GitHub

What wix-headless-templates does

Each Wix business solution gets its own folder: storefront, bookings, rentals, blog, cms, forms, members, events, restaurants, donations, pricing-plans, portfolio, faq. A folder carries a typed data layer and stores built on @wix/sdk, React hooks, reference components, Astro pages whose SEO fields the site owner can edit, a plain-fetch REST version for sites without a bundler, a seed script, and read-site.mjs, which reports what a site already contains. INSTRUCTIONS.md spells out the hook and DTO contracts.

Shared code sets the design and content floors, covers server-side work that needs elevated calls, site search and media upload, and holds the seed helpers. blank/ is the untouched CLI scaffold; compose.mjs rebuilds a solution's project/ from it and writes the package-lock.json.

The skill does not run a build. wix-headless-kit pulls the folder through install/templates.mjs, then copies, deploys and seeds from that copy. read-site.mjs only works with a logged-in Wix CLI, so an anonymous session reads nothing. A project rebuilt by compose.mjs reinstalls its dependencies, so run npm ci there before a typecheck.

What it helps with

  • Stand up a storefront on @wix/sdk from a working template
  • Check what a live site already holds before a seed writes anything
  • Serve the same data layer to a site with no bundler through the REST twin
  • Fill a site from a plan with an idempotent seed script
  • Read the hook and DTO contracts in INSTRUCTIONS.md

Example prompts for the agent

  • Open the bookings template and walk me through the hook and store contracts in INSTRUCTIONS.md
  • Run node bookings/seed/read-site.mjs --site <siteId> and tell me what the site already has
  • Rebuild storefront's project/ with node compose.mjs storefront and list what changed

How to install wix-headless-templates

1Skills CLI (Vercel)

npx skills add wix/skills --skill wix-headless-templates -a claude-code

2Manually: put the files in place

~/.claude/skills/wix-headless-templates/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/wix-headless-templates/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about wix-headless-templates

How do I install wix-headless-templates in Claude Code?

Run npx skills add wix/skills --skill wix-headless-templates -a claude-code; the skill then sits at ~/.claude/skills/wix-headless-templates/SKILL.md.

What does wix-headless-templates do?

It holds the shipped code for Wix Headless sites, one folder per business solution, with the data layer, Astro pages, seeds and contract playbook for each.

How is it different from wix-headless-kit?

This one is only the material and has no flow of its own. wix-headless-kit fetches the folder, then copies, deploys and seeds from its own copy.

Source text

SKILL.md · MIT
---
name: wix-headless-templates
description: "The shipped, verified code behind Wix Headless sites, one folder per Wix Business Solution: an online store, bookings, rentals, a blog, CMS collections, forms, members, events, restaurants, donations, pricing plans, a portfolio, an FAQ. Each ships a typed framework-agnostic data layer and stores over @wix/sdk, React hooks and reference components, Astro pages with owner-editable SEO, a REST twin for sites without a bundler, a seed script that fills the site from a plan, a reader that reports what a site already holds, and a playbook (INSTRUCTIONS.md) with the contracts. Shared across them: design and content floors, the capabilities (site search, media upload), the seed helpers, and a composed, lock-pinned project per solution that a create copies whole. Used by wix-headless-kit, which fetches, deploys and seeds from this folder; readable on its own to see what a solution's code does and how it is seeded."
---

# Wix Headless Templates

The code a Wix Headless site is built from, one folder per Wix Business Solution. `wix-headless-kit`
is the skill that runs a build: its `install/templates.mjs` fetches this folder once into the kit's
own `templates/` (a sparse clone of `skills/wix-headless-templates/`, or the checkout when the kit
runs from one) and the kit copies, deploys and seeds from there. This skill holds no flow of its
own; it is the material, kept as a skill so it is published, mirrored and readable like one.

## Layout

| path | what it is |
|---|---|
| `<solution>/INSTRUCTIONS.md` | the solution's playbook: what ships, the contracts of every hook, store and DTO, the pages, the dashboard links |
| `<solution>/app/` | the framework-agnostic core: `wix/<solution>/*-core.ts` (pure logic), the SDK transport, `*-store.ts` state machines, `types.ts`; `hooks/` (React bindings) and `components/` (reference implementations, correct and plain) |
| `<solution>/app-astro/` | Astro pages and layouts with owner-editable SEO pre-wired |
| `<solution>/rest/` | the data layer a second time over plain `fetch`, same exports, for a site with no bundler |
| `<solution>/seed/` | `SEED.md` (the plan shape and the traps), `seed-<solution>.mjs` (fills the site from a plan, idempotent), `read-site.mjs` (reports what the site already holds) |
| `<solution>/project/` | the composed project: the CLI's blank scaffold with the solution deployed and a `package-lock.json`, copied whole at create or attach so `npm ci` installs without resolving |
| `shared/` | `DESIGN.md` and `CONTENT.md` (the floors every site meets), `CUSTOM_OPERATIONS.md` (server-side work that needs elevated calls), `app/` and `rest/` (the client, media and config seams), `capabilities/` (site search, media upload), `seed/` (the CLI resolver, token, image resolver and site context every seed uses) |
| `blank/` | the pristine CLI scaffold the composed projects start from |
| `compose.mjs` | repository tooling: rebuilds a solution's `project/` from `blank/` plus a deploy, and its lock |

The solutions: `storefront`, `bookings`, `rentals`, `blog`, `cms`, `forms`, `members`, `events`,
`restaurants`, `donations`, `pricing-plans`, `portfolio`, `faq`.

## Reading it on its own

- What a solution does and how its pieces fit: `<solution>/INSTRUCTIONS.md`, then `app/wix/<solution>/types.ts`.
- How a site is filled and what the seed refuses: `<solution>/seed/SEED.md`.
- What an existing site holds before anything is written: `node <solution>/seed/read-site.mjs --site <siteId>` (a logged-in Wix CLI).
- A seed by hand, from a project folder with a `wix.config.json`: `node <solution>/seed/seed-<solution>.mjs plan.json`.

## Changing it

Code under `app/`, `app-astro/`, `rest/` and `seed/` is the source; `project/` is generated from it
with `node compose.mjs <solution>` from a checkout of the repository (it reinstalls the project's
dependencies, so run `npm ci` in the project before a typecheck). A composed project is checked
with `tsc` on its own `tsconfig.json`. Locks are resolved locally, never on a sandbox mirror.

© wix · MIT · wix/skills

Similar skills

All skills for Frontend and UI →

From the same set9

wix-docs wix-docs verifies exact Wix API endpoints and schemas via curl or MCP tools. Keeps agents from inventing parameters from memory. CX Codex +1 841installs wix-manage wix-manage — a skill for Claude Code and five other platforms that handles Wix site configuration and business tools through REST API. Runs administration, SEO tasks, app setups, and analytics queries. CX Codex +1 803installs wix-headless-kit wix-headless-kit — a skill for Claude Code, Codex, and Cursor that builds Wix Headless sites and deploys web projects online. Connects pre-built store, booking, or blog backends to your frontend code. CX Codex +1 482installs wix-vibe-headless wix-vibe-headless connects an existing frontend to a live Wix site using client-side REST and a public client ID. Runs straight from the browser without an SDK or custom backend. CX Codex +1 422installs wix-headless wix-headless wires Wix services into a headless frontend: installs the apps, seeds backend content, and returns an SDK integration guide. Managed projects also get the frontend built and released. CX Codex +1 338installs wix-app Assists in building Wix CLI app extensions, dashboard pages, widgets, and backend APIs. Prepares applications for Wix App Market review. CX Codex +1 261installs wix-design-system Inspects @wix/design-system components, props, code examples, and testkit drivers directly inside your project. CX Codex +1 218installs wix Agent skills and an MCP server to build Wix app extensions, wire headless frontends, and manage Wix Studio 2 sites. ★ 40repo stars

Project sponsors

Companies that keep this analytics open