AutoGineer
Generated banner for Wix Headless
Generated logo for Wix Headless

Wix Headless

WixOfficialPublished by Wix

  • Skill
  • Tool integration
  • Software development
  • MIT
  • Low risk
  • Has scripts
Download ZIP

From the author

Connect Wix business services (Stores, Bookings, Donations, CMS, Blog, Events, Forms, and more) to a Wix Headless frontend — infer the needed capabilities, install the apps, seed backend content, and produce an SDK-integration guide. For managed (Wix-hosted) projects it can also build the frontend: scaffold a new site (create) or wire an existing/brought-in design (connect), then build and release. Works across managed, self-managed, and stripe project types. Triggers: set up a Wix Headless backend, add Wix business features to my app, accept donations, build or host a Wix site, connect/implement this design with Wix.
— the description by Wix

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The wix-headless skill acts as an orchestrator for integrating Wix business services (such as Stores, Bookings, and CMS) into a headless frontend architecture. It handles the end-to-end configuration of the Wix backend, including app installation, content seeding, and the generation of a tailored SDK integration guide. Depending on the project type (managed, self-managed, or stripe), the skill can either provide a comprehensive integration guide for the user to implement or, in managed scenarios, actively scaffold, wire, and deploy the frontend project.

What it does

  • Infers required Wix capabilities based on user intent and project context.
  • Installs necessary Wix apps and seeds backend content automatically.
  • Generates a custom SDK integration guide for calling Wix services from the frontend.
  • Scaffolds or connects existing frontend projects to Wix for managed hosting.
  • Handles project-type-specific authentication and deployment workflows.
  • Provides a mechanism to relay feedback to Wix regarding the headless experience.

When to use it

  • When you need to integrate Wix business services into a custom-built headless frontend.
  • When you want to automate the setup and content seeding of a Wix backend.
  • When you are building a new site on Wix infrastructure and need a scaffolded frontend.
  • When you have an existing frontend design and need to wire it to Wix business capabilities.
  • When working with Stripe Projects and requiring a Wix backend configuration.

Advantages

  • Reduces manual configuration by automating app installation and content seeding.
  • Provides a clear, actionable SDK integration guide tailored to your specific capabilities.
  • Supports multiple project architectures including managed, self-managed, and Stripe-based setups.
  • Ensures consistent backend setup by following verified inline recipes.
  • Simplifies the transition from design to a functional, Wix-powered headless site.

Usage examples

“Set up a Wix Headless backend for a store with products and a blog.”
The skill will install the Stores and Blog apps, seed sample products and posts, and provide an SDK guide for fetching this data in your frontend.
“I have an existing design; connect it to Wix and host it on their managed infrastructure.”
The skill will initialize the project, wire the existing UI to the necessary Wix business services, and prepare it for release on Wix.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/wix/wix-headless/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip wix-headless.zip -d .agents/skills

Documentation by Wix

Wix Headless

This skill connects Wix business services to a Wix Headless frontend. Its core job is to configure the Wix backend: infer the needed capabilities, install the Wix apps, seed the backend content, and produce an SDK-integration guide describing how to call Wix from the frontend.

What happens with the frontend depends on the project type and operation:

  • Backend-only (self-managed, stripe, or a managed "just set up the backend" run) — the skill emits the SDK guide as its final output; the host owns the frontend, build, and hosting.

  • Managed create / connect — the skill also owns the frontend: it scaffolds a new project (create) or attaches Wix to an existing one (connect), wires it to the backend using that same guide, builds, and releases to Wix. (There is no Designer or template library — the frontend is built ad-hoc to intent.)

On a backend-only run the skill does not own the project scaffolding. When the work needs a frontend, scaffold it according to user intent — framework and structure follow the prompt; the skill's job is the Wix backend plus the emitted SDK guide describing how to call Wix from whatever frontend exists, not choosing or generating the app. This is the norm for a stripe run: the project is provisioned via Stripe Projects (credentials land in .env — see stripe/AUTHENTICATION.md), the skill configures the backend and emits the guide, and the live site is finalized per stripe/DEPLOYMENT.md — while the frontend is scaffolded and wired to intent, by the host.

Project types

The skill behaves identically across project types except for authentication and deployment, which are isolated in a per-type folder under references/:

Project typeHostingAuthentication & deployment live in
managedWix infrastructure (maintained by Wix)references/managed/
self-managedthe user's own host (TBD)references/self-managed/
stripethe user's own host, provisioned via Stripe Projectsreferences/stripe/

Everything else — Discovery, Setup, Seed, the SDK handoff — is project-type-agnostic and refers to "the provided authentication mechanism" rather than any specific method.

Resolving the project type

Resolve the type before Discovery, in this order — stop at the first that decides:

  1. Caller-provided. If the host/caller passed a project type (managed | self-managed | stripe), use it. An explicit value always wins.

  2. Detect from project signals (on disk). Check the working directory (read-only):

    • stripe — .env carries WIX_WIX_CLIENT_ID / WIX_WIX_CLIENT_SECRET / WIX_WIX_METASITE_ID (or the plain WIX_* fallback). This is the Stripe-Projects fingerprint.

    • managed — a Wix CLI project: wix.config.json present, or a .wix/ directory, or @wix/cli / @wix/astro in package.json.

    • self-managed — a frontend project on disk (e.g. package.json with a bundler/framework) with neither the Stripe .env fingerprint nor the Wix-CLI markers above.

  3. Detect from user intent. If disk is inconclusive, read the prompt:

    • managed — "managed", "host on Wix", "Wix-hosted", "deploy to Wix", "wix release".

    • stripe — "stripe projects", "I added Wix via Stripe", a Stripe-Projects context.

    • self-managed — "self-hosted", "my own host", names a non-Wix host, "I'll deploy it myself".

  4. Ask. If signals are absent or conflict, ask the user which type applies — don't guess.

Hold the resolved type in scratch; it selects <TYPE_DIR> (see Path resolution). Note self-managed is TBD — once resolved to it, the auth step will stop with a clear "not wired yet" error.

Resolving the operation (managed only)

create/connect/iterate are managed-only. For managed, resolve the operation by intent first, directory second — never let an empty directory override what the user is asking for. Check iterate first (it's decided by an unambiguous on-disk signal):

  • iterate → references/managed/CONNECT.md. The project is already connected to Wix — a wix.config.json (or .wix/) is already present — and the owner wants to add or change capabilities. Same flow as connect, but §1 skips init and reuses the existing wix.config.json; never re-init an already-connected project.

  • connect → references/managed/CONNECT.md. The user brings a design not yet connected to Wix and wants it wired: a frontend project on disk without a wix.config.json, or a brought-in/fetched design (a .zip/folder/file you unzip or read, a design-file URL, a Claude-Design/v0/Lovable export), or language like "connect this / implement this design (… connecting to Wix) / host this on Wix / deploy this to Wix / add Wix Headless to this project". A brought-in or fetched design is connect even when the current directory is empty — the design arrives from elsewhere (zip/fetch/URL), so emptiness at trigger time is not a create signal. (CONNECT.md step 1 places the brought design into CWD, then inits it.)

  • create → references/managed/CREATE.md. The user wants a new site built from a prompt with nothing brought in — "build me a site / store / blog…", no design file, no project on disk.

  • backend-only — the user only wants the backend configured (no frontend work). → the shared spine + emit the SDK handoff.

For self-managed and stripe, the operation is always backend-only (the host owns the frontend). Only when there is genuinely no brought-in design and no connect language does directory emptiness decide: empty → create; an existing frontend on disk → connect.

Preconditions (the host provides these — we read, never create)

  1. The project type — managed | self-managed | stripe — provided by the caller, else detected from project signals / user intent (see Project types § "Resolving the project type"), else asked. It selects <TYPE_DIR> (see Path resolution).

  2. A Wix metasite + a headless OAuth app exist, and credentials are available — obtained via the project type's AUTHENTICATION.md. The skill needs a bearer token authorized for the metasite and the metasite id.

  3. The user intent — free text describing what Wix should power ("add a store", "blog + contact form", "persist my app's data").

  4. (Optional) the project on disk — read-only, to sharpen brand/capability inference.

If the credentials are absent, the Wix backend isn't reachable — stop with a clear error.

What this skill does

Always open DISCOVERY.md first (it's agnostic — capability/brand/intent inference + the imagery gate, no auth). Then route by project type + operation:

Backend-only (self-managed, stripe, or managed backend-only) — the lean spine:

  1. Discovery (references/DISCOVERY.md) — infer capabilities + brand + intent + imagery.

  2. Setup (references/SETUP.md) — install the Wix apps those capabilities need.

  3. Seed (references/SEED.md) — create the backend content (+ entity images if imagery is on).

  4. Handoff (references/SDK_HANDOFF.md) — after Setup and Seed, emit the integration guide: SDK bootstrap, per-capability call shapes, the seeded IDs, and the @wix/* package list.

  5. Finalize deployment (<TYPE_DIR>/DEPLOYMENT.md) — run the project-type's finalize steps.

Throughout any run — if the user asks to send feedback to Wix, complains/gets frustrated, or the run hits any real friction (a confusing error, a doc gap, a tooling dead end, a workaround you had to invent — it doesn't need to repeat), offer to relay it to Wix per references/FEEDBACK.md. Default to offering rather than waiting to be asked. Every flow's finalize step (<TYPE_DIR>/DEPLOYMENT.md / managed/CREATE.md / managed/CONNECT.md) ends with the same checkpoint — treat it as a required self-check, not optional. Send only after an explicit yes — never automatically.

Managed create / connect / iterate — after Discovery, hand the whole run to the managed flow:

  • create → references/managed/CREATE.md (scaffold → Setup → Seed → build the frontend → release).

  • connect → references/managed/CONNECT.md (init → Setup → Seed → wire the existing UI → release).

  • iterate → references/managed/CONNECT.md — the project is already connected, so it reuses the existing wix.config.json (no init). Setup / Seed / wiring are incremental: it may already be set up and seeded from a prior run, so the agent checks current state first (installed apps, already-seeded content, existing wiring) and applies only the delta the new intent needs — never blindly re-installing or re-seeding. Re-release only if the frontend build output changed. These reuse the same SETUP.md/SEED.md/SDK_HANDOFF.md, but apply the SDK guide to build/wire the frontend themselves rather than emitting it, and release via managed/DEPLOYMENT.md.

Each Wix call uses the universal call shape (SETUP.md §1) with $TOKEN/$SITE_ID obtained per <TYPE_DIR>/AUTHENTICATION.md. The skill runs non-interactively except for the one imagery question (and asking the project type if it can't be resolved).

Don't smoke-test the frontend locally unless the user asks to verify. The deliverable is the built-and-released site (managed) or the SDK guide (backend-only) — not a local test report. By default do not start a dev server (wix dev / astro dev / npm run dev) to curl pages, drive the cart / booking / login flow, or launch a headless browser: correctness comes from following the recipes, real errors surface at wix build / wix release, and a headless run can't complete an interactive login or a real payment anyway — so these loops routinely burn minutes of wall for little signal (this is distinct from, and in addition to, the "release once at the very end" rule — that one only bans extra build+release cycles, not dev-server testing). Only spin up a dev server and smoke-test when the user's prompt explicitly asks to verify / test / confirm it works — and then keep it to a single lightweight pass (pages compile and render), not a full purchase/booking/login drive. The one post-release check in <TYPE_DIR>/DEPLOYMENT.md is the sanctioned verification.

Donations exception to the smoke-test policy above: for a build that accepts donations, follow the bounded anonymous API handoff check in references/inline-recipes/how-to-code-donations.md before claiming it works. It does not authorize a payment or campaign mutation, and does not require a dev-server testing loop. That recipe also defines the separate hosted-checkout and payment checks.

Path resolution

Compute <SKILL_ROOT> from this file (<SKILL_ROOT>/SKILL.md — strip /SKILL.md); hold the absolute path in scratch. Then resolve the project type to its folder and hold it too:

<TYPE_DIR> = <SKILL_ROOT>/references/<projectType>/ — one of managed/, self-managed/, stripe/.

WhatPath
Vertical index (intent matching + per-vertical site spec)<SKILL_ROOT>/references/CAPABILITIES.md
Discovery (infer capabilities + brand + intent; existing site → the Dynamic Context call in §1)<SKILL_ROOT>/references/DISCOVERY.md
Setup (install apps)<SKILL_ROOT>/references/SETUP.md
Seed (create backend content)<SKILL_ROOT>/references/SEED.md
SDK-integration handoff (emitted, or applied by create/connect)<SKILL_ROOT>/references/SDK_HANDOFF.md
Image generation (opt-in; agnostic)<SKILL_ROOT>/references/IMAGE_GENERATION.md
Design — fallback visual quality bar for the built frontend, when the user gave no design direction of their own (managed create only)<SKILL_ROOT>/references/DESIGN.md
Content — fallback copy quality bar for the built frontend, when the user gave no copy/voice direction of their own (managed create only)<SKILL_ROOT>/references/CONTENT.md
Experience overlays — a vertical's own design + copy bar on top of DESIGN/CONTENT (optional per vertical; read when that vertical is loaded)<SKILL_ROOT>/references/inline-recipes/experience-<vertical>.md (today: experience-store.md, experience-donations.md)
AI features — text/chat + embeddings (opt-in; agnostic)<SKILL_ROOT>/references/AI_FEATURES.md
Feedback — relay the user's headless-experience feedback to Wix (opt-in; user-approved)<SKILL_ROOT>/references/FEEDBACK.md
Authentication — obtain $TOKEN/$SITE_ID/clientId (project-type-specific)<TYPE_DIR>/AUTHENTICATION.md
Deployment — finalize the live site (project-type-specific)<TYPE_DIR>/DEPLOYMENT.md
Managed create flow (scaffold a new project)<SKILL_ROOT>/references/managed/CREATE.md
Managed connect flow (wire an existing project)<SKILL_ROOT>/references/managed/CONNECT.md
Frontend-axis references (how a frontend wires to Wix)<SKILL_ROOT>/references/astro.md, non-astro.md

Start a run by opening DISCOVERY.md. The flow files (CAPABILITIES, DISCOVERY, SETUP, SEED, SDK_HANDOFF, IMAGE_GENERATION, AI_FEATURES) are project-type-agnostic; the per-type specifics live under <TYPE_DIR>/ (AUTHENTICATION.md, DEPLOYMENT.md, and — managed only — CREATE.md/CONNECT.md).

Where the how comes from

This skill has no skill upstream — the how is read from the live Wix docs at dev.wix.com/docs. Read-priority: a page this skill links is read by curl-ing its .md twin directly (first priority — don't re-discover a curated link with search); the Wix MCP doc/search tools are second priority, for finding pages the skill doesn't link or as a fallback if a fetch fails. (Append .md to any docs URL for raw markdown; menu pages list child links, content pages carry the schema.)

Doc discovery is the shared fallback for both tracks — never the first move. Each track's primary source is its pinned material (below); when that doesn't cover what you need, fall back to references/DOC_DISCOVERY.md — a semantic doc-search + schema lookup that works with or without the Wix MCP.

  • Seed reads each capability's create flow from its inline recipe — a self-contained local inline-recipes/setup-*.md (mapped per capability in SEED.md § "What to seed per capability") that inlines the calls and supersedes the REST doc pages, so read it and seed from it alone. Only a capability with no inline recipe (e.g. coupons) falls back to doc discovery (DOC_DISCOVERY.md).

  • Handoff links the SDK docs for each capability's API shape, and supplies the runtime package set from the inlined map in SDK_HANDOFF.md (the SDK .md pages don't expose @wix/* import strings to navigation, so packages are mapped, not navigated).

Setup carries its app-install call (and the appDefId constants) inline in SETUP.md; CAPABILITIES.md is the vertical index that lets Discovery match intent and declares, per built vertical, the Required site features + Implementation checklist that Seed enables (backend-backed features) and the Handoff carries into the guide (so the host builds a complete site, not a bare data dump). This skill carries the what (which capabilities, how much content, what a finished site includes) and reads the how off the docs.

Files

references/inline-recipes/how-to-code-members-astro.md

name: "How to Code Members (Astro)" description: "The frontend contract for member sign-up / log-in / log-out and member-gated surfaces on a Wix-managed Astro frontend — the built-in /api/auth/login + /api/auth/logout routes that @wix/astro ships, the returnToUrl param, gating a page by resolving the member in SSR / a backend route, reading the current member with @wix/members getCurrentMember, and the two rules that keep this path from breaking: no OAuthStrategy/no client (that 500s under auto-auth) and no auth.elevate for a member reading their own data. Specifies the how for the Astro axis only — read how-to-code-members-non-astro.md for any non-Astro frontend."

RECIPE: How to Code Member Auth on a Wix-managed Astro Frontend (built-in /api/auth/*, @wix/members)

A concise contract for wiring login / sign-up / logout and member-gated surfaces into an Astro frontend. This is the how (which routes, which module, which failure modes), not the what — which pages are gated, what the account page shows, and the design come from the request you're fulfilling.

⚠️ AXIS GUARD — this recipe is for Astro only. On managed-Astro authentication is ambient and login ships as built-in routes. If the frontend is not Astro (Vite/React/Vue SPA, static HTML, self-managed), stop and read how-to-code-members-non-astro.md — that path builds a manual OAuthStrategy handshake, which is the opposite of what this recipe says. Cross-contaminating them is a real failure: building an OAuthStrategy client on Astro 500s at SSR (astro.md — "no client" is the whole point of the integration).

One mechanism, not three. Sign-up, log-in and log-out are the same flow. The Wix login page logs in an existing member or registers a new one in the same step; you never build a separate "sign up" call. Log-out is the inverse of the same flow.

Login surface — this recipe is the Wix-hosted login page (the default). If the brief explicitly asks for a custom/branded in-app login form or custom sign-up fields (full name / username / address / arbitrary fields), that's the custom login page surface — read how-to-code-members-custom-login.md. Note custom login is a client-driven OAuthStrategy flow with no client under Astro auto-auth, so on Astro it means instantiating an explicit OAuthStrategy client in a backend route or a client island (never in SSR frontmatter) — take it on only on real intent; otherwise the built-in routes below are the default. The choice is intent, not project type.

Pinned docs (read before wiring — curl the .md directly):

Identity vs. profile — two layers, don't conflate them (read this first)

The docs draw a hard line, and so must the code:

  • Identity / auth — "is this caller a logged-in member?", log in, log out. Native to the headless OAuth app. No app install needed. Everything in "Log in / sign up / log out" and "Gate a surface" below runs on this layer alone.

  • Member profile / Members Area — reading the member's name / photo / roles / badges, an editable my-account page. Served by the Wix Members Area app, which must be installed on the site (see SETUP.md). @wix/members getCurrentMember() returns member data only once that app is present.

So a paywall that only needs "logged-in vs not" runs on identity alone; anything that displays or edits member data needs the Members Area app installed. If getCurrentMember() returns empty/errors on a site where login clearly worked, suspect the Members Area app isn't installed — not a code bug.

Log in / sign up / log out — built-in routes, zero wiring

@wix/astro ships the endpoints; you only render links/actions. Do not build a login page or an OAuth handshake — that's the non-Astro path.

<!-- log in OR sign up — same route, redirects to the Wix login page -->
<a href="/api/auth/login">Log in / Sign up</a>

<!-- land the member somewhere specific afterward -->
<a href="/api/auth/login?returnToUrl=/account">Log in</a>

Logout is a POST to /api/auth/logout (optionally with ?returnToUrl=):

<form method="POST" action="/api/auth/logout"><button>Log out</button></form>

  • The param is returnToUrl — not returnUrl. The routes validate their query with a strict schema that silently DROPS unknown params, so a misspelled param doesn't error — the member just lands on /. The value must be a relative path (the callback refuses absolute URLs).

  • After login the member identity rides on every subsequent SDK call automatically — no client, no token handling. That's auto-auth (astro.md).

Gate a surface — resolve identity in SSR or a backend route

Gating is just "do I have a member session?", decided server-side (SSR frontmatter or a src/pages/api/*.ts route), then bounce anonymous visitors to the built-in login route. This is the exact shape already used for blog comments (SDK_HANDOFF.md §5).

---
// src/pages/account.astro — gate the page in SSR frontmatter
import { members } from '@wix/members';
let me = null;
try {
  const res = await members.getCurrentMember({ fieldsets: ['FULL'] });
  me = res.member ?? null;
} catch { /* not a member / not installed — treat as anonymous */ }

if (!me) return Astro.redirect('/api/auth/login?returnToUrl=/account');
---
<h1>Welcome, {me.profile?.nickname ?? me.loginEmail}</h1>

  • Guard the SSR call in try/catch — an unguarded throw truncates the response mid-stream (white screen; astro.md A3). An anonymous visitor is a normal state, not an error: catch → treat as logged-out → redirect to login.

  • Don't render account/gated UI as a client island that checks auth in the browser. Resolve identity server-side and gate the route; render only what a member should see. (Same reasoning as the blog-comment API-endpoint path — avoid the browser-auth detour.)

  • For an action that only some callers may take (post a comment, place a member order), don't gate the whole page: render the control always, and on submit POST to a src/pages/api/*.ts endpoint that resolves the session and, if the caller isn't a member, redirects to /api/auth/login?returnToUrl=….

Read the current member — @wix/members, not the dev-preview package

import { members } from '@wix/members';
const { member } = await members.getCurrentMember({ fieldsets: ['FULL'] });
// member.profile?.nickname, member.profile?.photo, member.loginEmail, member.contactId, member.roles

  • ⚠️ The SDK export is getCurrentMember, NOT getMyMember. The REST method is named Get My Member and the SDK docs page may show GetMyMember, but @wix/members exports it as members.getCurrentMember — calling members.getMyMember(...) throws is not a function at runtime. This bites because a logged-out smoke test never reaches the call; it only fails once a real member loads the page.

  • ⚠️ Use @wix/members (members.getCurrentMember / getMember / updateMember). It needs only visitor/member auth and is production-ready. Do NOT reach for @wix/site-members (wixSiteMembers, frontend "Current Member" getMember/getRoles/makeProfilePublic) — it's in Developer Preview ("not intended for production"). Use it only if a profile-privacy toggle is specifically requested.

  • The member's photo field is a wix:image:// identifier — resolve it with media.getScaledToFillImageUrl like any other Wix image (astro.md A6); never hand-build the CDN URL.

  • Reading another member by id returns only their PUBLIC fieldset, and a private profile returns nothing to a visitor/member identity. This is why the blog-comment author lookup (SDK_HANDOFF.md §5) quietly assumes the author's profile is public — the same caveat applies to any "look up a member by id" here.

⚠️ Do NOT auth.elevate() for member features (the most likely wrong turn)

Member login and elevation are different axes:

  • Login moves you along the identity axis: anonymous visitor → a specific member.

  • auth.elevate() moves you along the permission axis: caller → app/admin scope.

A logged-in member reading their own data — own orders, own bookings, own subscriptions, plan-gated content, their profile — is authorized for it under the member token, with no elevation. Reaching for auth.elevate() to "make member data work" is the classic mistake: it's the wrong axis, and it doesn't grant a member access to their own data (they already have it).

auth.elevate() is only for site-wide/admin reads (everyone's orders, listing all members). On Astro that goes in a backend route (src/pages/api/*.ts wrapping auth.elevate(), astro.md §2) — never inline in a page. If you're gating content by the member's own plan, that's a member-token read; listing all plans/orders as admin is the elevate read. Keep them separate.

pricing-plans is a HARD dependency on members

If the site has pricing-plans (membership / subscription / paid tiers), login is required, not optional. Ordering a plan (orders.createOnlineOrder(planId)) orders it for a logged-in member; if none is logged in the Wix flow forces sign-up. orders.memberListOrders() and "my subscription" reads return nothing for an anonymous visitor.

So: browsing the plans grid is public, but the subscribe button and the my-subscription surface both need the login mechanism above. A logged-in member calling orders.createOnlineOrder needs no onBehalf — the order is created on their behalf from the member session. (Everywhere else — stores "my orders", bookings "my bookings", events "my registrations" — member login is a soft add-on: the purchase/RSVP/book action itself runs fine as an anonymous visitor; only the account view of it needs a member.)

Conclusion

Correct member auth on an Astro frontend:

  • uses the built-in /api/auth/login (login and sign-up) and POST /api/auth/logout routes with an allow-listed returnToUrl — the login handshake never builds an OAuthStrategy client, and one must never be built in SSR frontmatter (the public-env clientId is undefined at server render → 500). (The one exception is the custom-login surface — how-to-code-members-custom-login.md — which builds an explicit client in a backend route or client island, never in SSR frontmatter.)

  • gates surfaces server-side (SSR frontmatter or a src/pages/api/*.ts route), guarded in try/catch, bouncing anonymous visitors to /api/auth/login?returnToUrl=…;

  • reads the current member via @wix/members getCurrentMember (not the dev-preview @wix/site-members), resolving the photo wix:image:// URI and expecting only PUBLIC fields for other members;

  • does no auth.elevate for a member reading their own data (elevation is a different, admin-only axis that lives in a backend route);

  • treats login as required whenever pricing-plans is present (subscribe + my-subscription), and as a soft add-on for the "my …" surfaces of the other verticals;

  • needs the Wix Members Area app installed only for profile data (name/photo/roles) — pure "logged-in vs not" gating runs on the identity layer with no install.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Wix
Publisher
Wix (Official)
Source
wix/skills · skills/wix-headless · commit d168bc2
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Wix or Wix.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download wix-headless.zip