Skip to content

feat(sp-wix): Wix × Stripe Projects business-integration skill#374

Open
ozsay wants to merge 3 commits into
mainfrom
headless-stripe
Open

feat(sp-wix): Wix × Stripe Projects business-integration skill#374
ozsay wants to merge 3 commits into
mainfrom
headless-stripe

Conversation

@ozsay

@ozsay ozsay commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

What

A new standalone skill, sp-wix, that connects Wix business services (Stores, Blog, CMS, Forms) to an app managed by Stripe Projects — invoked after stripe projects add wix/* has provisioned a Wix metasite and synced its credentials to .env.

The host agent keeps the frontend, build, and hosting; this skill owns only the Wix backend work and returns an integration guide.

Flow

  1. Discovery — infer the Wix capability set + brand + per-capability intent from the user's words (no interview/gate).
  2. Setup — install the apps those capabilities need on the metasite.
  3. Seed — create starter backend content (products, posts, collections+items, forms).
  4. Handoff — return an SDK-integration guide: packages, the public clientId from .env, seeded IDs, and links to the live Wix SDK docs (rather than inline snippets that drift).
  5. Register origin — after deploy, add the live site URL to the OAuth app's allowed domains (the step init does for hosted sites; here we don't own hosting, so it's done post-deploy).

Design notes

  • Standalone — the only upstream is wix-manage (API recipes loaded via Skill); no reference to the wix-headless skill. API request shapes live in wix-manage (found by capability phrase), frontend shapes in the SDK docs.
  • No @wix/cli — pure curl against wixapis.com, token minted from .env client-credentials (POST /oauth2/token).
  • Descriptive, not restrictive — imperative about its own actions, imposes nothing on the host's flow.

Validation (POC)

Exercised end-to-end across runs against a real Stripe project: discovery → setup → seed → handoff → frontend build → deploy → register-origin. The SDK was wired correctly (server-side SSR listPosts), the skill read the real wix-manage recipes (not guessed shapes), read live SDK docs (no sibling-project copying), and registered the deployed origin.

Known gap: the Stripe-provisioned OAuth app currently lacks SCOPE.HEADLESS.MEGA (and OAuth-app-manage), so the admin Setup/Seed/origin calls 403 — a provider-side scope fix, tracked separately. Manually installing the Blog app confirmed the frontend renders posts once the backend exists.

🤖 Generated with Claude Code

ozsay and others added 3 commits June 8, 2026 12:19
Standalone skill that connects Wix business services (Stores, Blog, CMS,
Forms) to a Stripe Projects app after `stripe projects add wix/*` has
provisioned a metasite + synced credentials to .env.

The skill owns only the Wix backend work; the host keeps the frontend,
build, and hosting. Flow: Discovery (infer capabilities/brand/intent) ->
Setup (install apps) -> Seed (create content) -> Handoff (SDK integration
guide) -> Register origin (post-deploy OAuth-app allowed-domain update,
the step init normally does for hosted sites).

- Standalone: only upstream is wix-manage (recipes loaded via Skill)
- Pure curl against wixapis.com; token minted from .env client-credentials
  (no @wix/cli, no wix login, no wix.config.json)
- Handoff links to live Wix SDK docs rather than inlining snippets
- Descriptive, not restrictive: imperative on its own actions, imposes
  nothing on the host flow

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant