القائمة
Apply an explicitly requested, identity-preserving UI/UX refinement after clone acceptance.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/wix/skills --skill rp-faceliftيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى 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-facelift |
| description | Apply an explicitly requested, identity-preserving UI/UX refinement after clone acceptance. |
Load this resource only when docs/site-clone/frontend-automation-state.json records
checkpoints.facelift.requested: true and the migration website receipt is complete or
done_with_gaps. A done_with_gaps receipt must reference a finalized visual review and
the configured cycle cap. Never load it as part of ordinary cloning.
Invoke the installed ui-ux-pro-max skill for this pass. If it is unavailable, record a
specific facelift blocker with the required install/enable action; do not silently replace
it with an unconstrained redesign or claim the selected deliverable is complete.
Before changes, treat extracted brand colors/fonts/logos/assets, route plan, visible copy, section order, core interaction contract, SEO, and dynamic data bindings as identity locks. Preserve them. UI/UX Pro Max may improve hierarchy, spacing, responsive layout, accessibility, component/control states, and restrained purpose-driven motion/interactions. It must not change the brand, information architecture, page content, URLs, source assets, or required core behavior.
Build and browser-test the changed site. Write docs/site-clone/facelift-review.json with
the request, changed routes/components, evidence that all identity locks were retained,
accessibility/interaction checks, before/after screenshot references, and an accepted or
blocked decision. For done_with_gaps, include the completion receipt and residual-gap
context; do not claim normal clone acceptance, visual parity, or resolution of those gaps.
Update frontend-automation-state.json facelift checkpoint to
accepted only after that review passes. Then return to the root supervisor so it can write
the completion receipt. In one-click mode the stored request authorizes this stage after the
gate; it does not waive the review.
