用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/wix/skills --skill rp-project-context命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Build on and manage the connected Wix site from a Base44 app: discover and call any Wix API (endpoints, request/response shapes, fields), gather site context, route each call to the right identity, and follow curated recipes for admin tasks.
REST recipes to configure and manage a Wix site's business solutions — stores, bookings, payments, CMS, and more. Open the matching recipe for the exact endpoint, method, and payload before calling — never guess a Wix API. Routes to: stores, bookings, get-paid, CMS, contacts, forms, media, app-installation, pricing-plans, restaurants, ricos rich-content, sites, blog, calendar, domains, events, site-properties, ecommerce, marketing, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.
Build a Wix Headless site fast by wiring SHIPPED, verified @wix/sdk code instead of authoring the integration from recipes. Each Wix business vertical ships a typed, framework-agnostic React core (data layer returning plain DTOs, hooks, headless components) plus an Astro overlay (SSR pages with owner-editable SEO pre-wired) and a build-time REST seed script — the agent scaffolds via the Wix CLI, deploys the shipped code, seeds the backend, designs the presentation layer itself on the shipped hooks (product card/grid, PDP, home, theme), and releases to Wix hosting. Works on Wix-managed Astro (ambient auth, the default) and on any React-based project (Vite, non-Astro) over the public OAuth client id. Verticals: stores/storefront (products, categories, variants, cart, hosted checkout), bookings (services, appointment/class time slots, staff, booking form, checkout-or-place), blog (posts, categories/tags, rich content), cms (structured content collections), events (listing, RSVP, ticket sales), members (login, ga
正在显示 SKILL.md
| name | rp-project-context |
| description | Resolve headless mode, scope, Wix project validity, and browser execution readiness. |
Load this resource only when the run's mode, source/scope, output project, approval state, or browser environment is unresolved. It owns setup decisions, not extraction or UI work.
Read references/safety.md and the applicable mode/scope and preflight sections of
references/workflow.md. Read references/output-contract.md only when validating the
project or automation-state artifact.
home scope with no --urls.--handoff. Read its route families, public URL intent, Wix
bindings, slug policy, websiteScope, automationMode, and
frontendPhase.allowedNow. The handoff is authoritative.plan phase, write/refresh plan-eligible context and evidence only; do not require a
runnable frontend or attempt build/release. In build, validate the existing
migration-owned project before proceeding.For standalone home cloning, provision or verify the exact final output directory before
artifact generation or UI writes. It must be a real successful Wix CLI scaffold, not a
manual fallback, and contain a valid Wix configuration plus package.json dev and
build scripts. Create its empty yarn.lock project boundary up front. If the scaffold
uses @wix/astro-wix-hosting-adapter, remove a direct standalone
@astrojs/cloudflare dependency before install/build normalization.
For migration mode, reuse the handoff-owned project/site only. If project identity or its runnable contract fails, record the precise failure and recover it; never create a sibling scaffold.
Use clear-wix-starter.mjs after a valid template creates demo files, before clone UI
work starts.
Before browser extraction run:
node scripts/browser-extraction-preflight.mjs --project-root <project-root>
If needed, first attempt --fix. The host must have normal node_modules resolution,
required browser/design dependencies, and Chromium; Yarn Plug'n'Play is not sufficient.
For this repository, run path-sensitive Wix/Yarn commands in interactive zsh with the
repo-local NVM toolchain. In a one-click run, retry a shell/PATH mismatch once under that
aligned shell. If browser launch or network access is sandbox-blocked, request the required
escalation and retry. Only then record a blocker; a pending runtime approval is a real
wait, not a reason to ask unrelated routine confirmations.
Write/update frontend-automation-state.json whenever the mode, phase, effective scope,
scope checkpoint, or auto-progress policy changes. Return to the root supervisor once the
context is durable.