AutoGineer
Generated banner for Rp Website Continuation
Generated logo for Rp Website Continuation

Rp Website Continuation

WixOfficialPublished by Wix

  • Skill
  • Workflow
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Continues a website-mode migration from the validated backend handoff through frontend build, post-build gap analysis/fixing, release, and a durable frontend completion receipt.
— the description by Wix

AutoGineer summary

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

This skill manages the frontend-specific phase of a website migration. It ensures that the migration process correctly handles site destinations, avoids duplicate site creation, and executes the build, gap analysis, and release cycle. It relies on handoff data to perform site cloning and concludes by generating a durable completion receipt.

What it does

  • Coordinates frontend site migration from a validated backend handoff.
  • Prevents duplicate site creation by enforcing strict destination and scaffolding rules.
  • Executes the build and post-build gap analysis loop.
  • Performs optional UI/UX facelift and acceptance reviews if requested.
  • Handles missing or stale handoff data by regenerating the necessary files.
  • Generates a final completion receipt in JSON format upon successful release.

When to use it

  • When the orchestration router specifies this resource for a website-mode migration.
  • When you need to complete the frontend portion of a replatforming project.
  • When you need to resolve missing or stale website handoff data.
  • When you need to finalize a migration with a formal completion receipt.

Advantages

  • Ensures architectural consistency by preventing orphaned site creation.
  • Automates the gap analysis and fix loop for frontend migrations.
  • Provides a standardized completion receipt for audit and tracking purposes.
  • Integrates seamlessly with existing backend handoff workflows.

Usage examples

“Continue the website migration for the current project.”
The agent will check for a valid handoff, perform the frontend build, run gap analysis, and generate the completion receipt.
“The website handoff is missing, please fix it.”
The agent will trigger the handoff generation script before proceeding with the migration workflow.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/wix/rp-website-continuation/download

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

    mkdir -p .agents/skills && unzip rp-website-continuation.zip -d .agents/skills

Documentation by Wix

rp-website-continuation

Use this resource only when the orchestration router returns nextResource: resources/rp-website-continuation/.

Contract

For deliveryMode=website, this is a frontend-only run — but it still needs a destination, and that destination is still rp-destination's job, not this skill's or wix-headless-replatform's. Do not let wix-headless-replatform scaffold its own site here: its only safeguard against a duplicate is "does a local folder already have a package.json," which is not the same account-confirmation gate, WIX_SITE_ID persistence, and dashboard-URL report that every other delivery mode gets.

  1. Resolve the destination via rp-destination first, scaffolding into <projectDir>/frontend with --site-template blank (there is no backend catalog to provision for, and this matches wix-headless-replatform's own default template choice for the home-scope clone this invocation performs). Persist WIX_SITE_ID in config/wix.env and report the dashboard URL, same as any other mode.

  2. Then invoke wix-headless-replatform with the source URL and --out <projectDir>/frontend; do not run backend discovery, mapping, setup, or import. Because <projectDir>/frontend already contains a valid scaffold from step 1, wix-headless-replatform's own standalone reuse check finds it and continues from there instead of scaffolding a second site.

Finish its build and gap loop. Only when the user explicitly requested facelift at intake, run the separate post-clone UI/UX Pro Max facelift and acceptance review; otherwise do not load that stage. Then release and write website/completion.json with finalize-migration-website.mjs --project-dir <projectDir> --out <projectDir>/frontend --release-url <public-url>.

execution/completion-report.json means backend import accounting. It is not the terminal result of a deliveryMode=management_and_website migration.

When the route reason is missing_website_handoff or stale_website_handoff, first run node skills/wix-replatform/scripts/website-handoff-generate.js <projectDir> and route again. Otherwise load the current website/handoff.json, then invoke wix-headless-replatform in migration mode via its --handoff flag:

node scripts/site-clone.mjs <source-url> --handoff <projectDir>/website/handoff.json

--handoff is required here, not optional. It is the only thing that puts wix-headless-replatform into migration-phase mode; without it the skill falls back to standalone mode and unconditionally scaffolds and executes a new @wix/new headless call — a second, orphaned site, which is exactly the failure "never create a second destination site" (see rp-destination) exists to prevent. Continue its actual build, post-build gap analysis, bounded fix loop, and release sequence. Do not stop after implementation or a successful build.

The frontend skill must atomically write website/completion.json before this resource can finish. A successful receipt has the current handoffFingerprint, completed screenshot review, zero unresolved critical/high gaps, and a released (or explicitly not-applicable) release state.

If a genuine blocker remains after required 1-click recovery/escalation retries, persist a status: "blocked" receipt with the blocker code, evidence, attempted recovery, owner, and exact unblock action. Then route again. Do not describe a pending storefront as a completed migration.

After the gap loop has passed and the storefront is released, write the receipt with:

node skills/wix-headless-replatform/scripts/finalize-migration-website.mjs \
  --handoff <projectDir>/website/handoff.json --release-url <public-url>

Files

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

No issues found by our static scan· No issues found

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 · wix-replatform/resources/rp-website-continuation · 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 rp-website-continuation.zip