All skills
wix avatar

/wix-headless

@8f7fa5d official
by Wix.comwix/skills33 stars
33

Connect Wix business services (Stores, Bookings, 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, build or host a Wix site, connect/implement this design with Wix.

Use this Skill: https://skilld.dev/gh/wix/skills/wix-headless

This session only. Nothing lands on disk.

referencesCONTENT.md

≈965 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Content — default copy quality bar for the built frontend (managed create)

Applies when this skill writes frontend page copy from scratch (managed create, CREATE.md §4) — hero/section headlines, subtitles, kickers, CTA labels, and any image captions the pages include. Same scope as DESIGN.md: not connect/iterate (the copy already exists there).

Same precedence rule as DESIGN.md: fallback, not override. If the user supplied their own copy, brand voice, or tone direction, use theirs — don't overwrite it to match the conventions below. The one exception is §1 — a comprehension floor, not a style preference: whatever the voice, a first-time visitor must still be able to tell what the business is from the hero.

1 · Say what the business is — explicitly, above the fold

  • A first-time visitor must know what the site is and what they can do, straight from the hero — never left to infer from mood or voice alone.
  • The business category (e.g. "yoga studio", "restaurant", "construction services") must appear literally in at least one of: the H1, a kicker above the H1, or the first clause of the subtitle. A witty H1 alone is not enough.
  • The subtitle leads with the offer, in plain language, before any flavor — put the verb the visitor actually cares about early ("Book…", "Order…", "Learn…", "Hire…").
  • Voice-driven, evocative H1s are welcome — but only when the category sits explicitly right beside them (kicker or subtitle). When in doubt, name the category in the kicker.

2 · Kickers (micro-copy above titles)

  • Cut a kicker that only restates the title (e.g. "The Courses" above a Courses heading) — it adds nothing.
  • Keep a kicker that carries real information: category + location ("Yoga Studio · Downtown"), a feature's proper name, event details, dates, price framing.
  • A kicker is the right place to satisfy §1 when the H1 itself is voice-led rather than literal.

3 · Titles, subtitles, paragraphs, CTAs

  • Titles and subtitles end without a period. Paragraphs (full running sentences) keep theirs.
  • No fluff — every line should move the visitor's understanding forward, the H1 and subtitle most of all.
  • CTA labels are short and avoid all-caps unless a specific reason demands it (readability). Word them to the actual action (ties to DESIGN.md §2's "one primary CTA, worded to the action" rule) — not generic verbs.

4 · Images — the real subject comes first

  • At least one image on the page must show the real story of the business — the actual thing, not just abstract graphics, dashboards, or decorative art. A climbing outfitter shows mountains and climbers; a clinic shows the room; a workshop shows the tools and hands at work.
  • Decorative/supporting visuals (illustrations, icons, patterns, textures) layer in addition to the real subject, never instead of it. They earn their place by reinforcing the story and mood once the business is genuinely shown — not by standing in for it.
  • Imagery (real or decorative) matches the tone, voice, and era of the business.
  • When the user must supply their own real photos (the business has a specific, particular space/product/person that generated imagery can't stand in for), use a fillable image slot with a descriptive placeholder naming exactly what belongs there — not a generic stock image presented as final.

5 · Image captions

  • A caption describes what is actually seen in its image. Tone can vary (serious, playful, informative) but must stay aligned with the image's real content.
  • No meaningless captions, and no caption that ignores the image. A slogan or pull-quote overlaid on a photo is not a caption — if a true caption is wanted, write one that describes the scene once the real image is in place.

Source: SKILL.md on GitHub

1 warning1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The wix-headless skill is a robust tool for integrating Wix services into headless frontends. It incorporates secure practices for credential management, ensuring tokens remain outside the AI context. While the skill performs remote code execution and has data ingestion surfaces, these actions are carried out through official vendor channels and structured workflows.

  • Socket1d

    1 alert: gptAnomaly

  • Snyk1d

    Risk: LOW · No issues

Signed by skilld at 8f7fa5d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
What it can do
Runs commands Reads files Edits files
All 16 allowed tools
Bash(curl *)Bash(npx @wix/cli@latest *)Bash(npx @wix/cli *)Bash(npm create @wix/new@latest *)Bash(npm install *)Bash(npm run *)Bash(node *)Bash(cd *)Bash(ls *)Bash(mkdir *)Bash(cp *)Bash(mv *)Bash(uuidgen)ReadWriteEdit
  • wix
  • headless
  • ecommerce
  • astro
  • vite
  • jsx
  • hosting
  • cms
  • bookings

README badge

README badge for wix/skills/wix-headless

Scaffolds a new Wix Headless site from scratch or connects an existing HTML/JSX/Vite project to Wix Headless for hosting and business features (ecommerce, bookings, forms, CMS). Handles discovery, design, feature wiring via the Wix SDK, and deployment; routes on operation type (create vs. connect) and frontend framework (Astro by default, or your own build).

Generated from the current SKILL.md.

Does this skill create a new site or connect an existing one?
Both. Path A creates a new site from scratch based on your description (e.g. 'build me an online store'). Path B connects an existing project (HTML/JSX/Vite app, Claude Design output, etc.) to Wix Headless for hosting and feature wiring.
What happens when I connect an existing project to Wix Headless?
The skill analyzes your project, installs the necessary Wix Business Solutions apps, and wires the Wix SDK directly into your existing source files so each installed app powers its corresponding feature.
What frameworks does this skill support?
For new sites, it defaults to Astro but supports any framework you explicitly name (React, Vue, Svelte, Vite, etc.). For existing projects, it works with HTML, JSX, TSX, Vue, and other web frontends.
Does this skill handle ecommerce, bookings, and content sites?
Yes. It routes to different vertical packs depending on your needs: stores and ecommerce, bookings and appointments, CMS and blogs, forms, and gift cards. All verticals include CMS by default.
How does the skill authenticate with Wix?
It uses the Wix CLI (`npx @wix/cli@latest token`) to generate bearer tokens for API calls. The login flow is safe for non-interactive agents and includes a recovery ladder if needed.

Generated from the current SKILL.md. These answers refresh after source changes.