Skills

Skill 16 of 67

Wix Headless Templates

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…

2 minutes · 349 words · 3 sections

Install

$ npx skills add wix/skills --skill wix-headless-templates

$ npx skills add wix/skills

» /plugin marketplace add wix/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/wix/skills, branch main, last pushed 8 November 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

67 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 5 distinct layouts observed: skills/*/SKILL.md, skills/wix-headless-replatform/resources/*/SKILL.md, skills/wix-replatform/resources/*/SKILL.md, */SKILL.md, wix-replatform/resources/*/SKILL.md.

Duplicates collapsed

5 mirror copies folded into their canonical skill — republished for Alternate. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from a curated brand profile — hue 261°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Wix Headless Templates”, a leading h1 that duplicated the skill title.

Spec compliance

1 editorial note across 1 of 67 skills. They are printed in the margin of each skill rather than as errors here.

Wix Headless Kit — 1 note

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Wix, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /wix/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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.

Wix Headless Templates

Layout

Reading it on its own

Changing it

About this skill

Trigger

Colophon

Wix Headless Templates

Layout

Reading it on its own

Changing it

Appendix 16.1–16.828

AssetsJSON · 14 files

Also bundled827 files

About this skill

Trigger

Colophon

Appendix 16.1–16.828

AssetsJSON · 14 files

Also bundled827 files