wix-vibe-headless

Connects existing front ends to live Wix sites via client-only REST scaffolds.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill wix-vibe-headless-divinaarmuela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-vibe-headless
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/wix-vibe-headless
Command: npx skills add https://github.com/divinaarmuela/Content --skill wix-vibe-headless-divinaarmuela

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It lets an already-built front end (a vibe-coded app, HTML/JSX/Vite project, or design-tool export) display and transact with live content from an existing Wix site directly from the browser, without the Wix SDK, a backend, or a build step. ## Core Features & Use Cases - Nine business-solution verticals: copy-as-is REST helpers for Stores (products, cart, checkout), Bookings, Blog, Events & Tickets, Portfolio, Restaurants (menu, ordering, reservations), CMS/Wix Data, Pricing Plans, and Members (custom login with email, Google/Facebook, or SSO). - Shared transport layer: a single wix-client.js that mints and refreshes anonymous visitor tokens from the public WIX_CLIENT_ID, persisting identity across reloads so carts and sessions survive. - Read-only over owner content: renders live Wix data or an honest empty state, never mocks or provisions data; purchases always complete through Wix-hosted checkout redirect sessions. - Use Case: A user hands over their WIX_CLIENT_ID and asks to connect their Vite/React storefront to their Wix store — the skill supplies the catalog and cart helpers plus wiring instructions so products, cart, and checkout work against live Wix data. ## Quick Start Give the assistant your Wix client ID and ask it to connect your existing front end to your Wix store, blog, bookings, or other business solution using this skill.

Frequently Asked Questions about wix-vibe-headless

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect my existing front end to my Wix site?

Provide your site's public WIX_CLIENT_ID, pick the vertical matching your business solution (store, bookings, blog, etc.), copy the shared wix-client.js plus that vertical's helper into your project, and wire your UI to the exported functions. No SDK, backend, or build step is required.

What Wix business solutions does this skill support?

It covers nine verticals: Stores/eCommerce, Bookings, Blog, Events & Tickets, Portfolio, Restaurants (menu, ordering, reservations), CMS/Wix Data, Pricing Plans, and Members with custom login. Each ships its own REST helper and an INSTRUCTIONS.md playbook.

Is the WIX_CLIENT_ID safe to hardcode in frontend code?

Yes. The WIX_CLIENT_ID is a buyer/visitor-facing credential that only mints anonymous visitor tokens, so committing it is fine. It cannot perform admin operations; elevated management tasks require a separate connector token or API key.

When should I use wix-headless instead of wix-vibe-headless?

Use wix-headless when building a new Wix site end-to-end, when the project should use the @wix/sdk or Wix CLI, or when hosting on Wix. wix-vibe-headless is strictly the client-only, REST-only path for wiring an existing front end to an existing site.

Why does my cart empty on every page reload?

The visitor refresh token is the cart's identity and must persist in localStorage via the shipped wix-client.js. Re-minting an anonymous token per load creates a new visitor each time, which silently empties the cart.

Can I build a custom checkout page instead of Wix-hosted checkout?

No. All purchases must complete through the Wix redirect-session flow — the helpers return a hosted checkout URL you redirect to. Hand-building checkout or purchase URLs is explicitly prohibited.