replatform

Orchestrates source-to-Wix migrations by inspecting project artifacts and routing to the next workflow step.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill replatform-divinaarmuela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: replatform
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/replatform
Command: npx skills add https://github.com/divinaarmuela/Content --skill replatform-divinaarmuela

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Migrating a business from platforms like Shopify, WordPress, or WooCommerce into Wix involves many fragile steps—discovery, mapping, setup, code generation, and import—where losing track of state or skipping approvals can cause data loss or duplicate writes. This Skill acts as the traffic controller for the entire migration, inspecting durable project artifacts to determine exactly what to do next. ## Core Features & Use Cases - Resumable orchestration pipeline: Resolves the active migration project, loads orchestration artifacts, and routes through discovery, mapping, setup, codegen, and import with durable JSON checkpoints. - Safety gates and review checkpoints: Enforces a mapping review checkpoint, safe-mode/dry-run code safety review, and a mandatory execution-plan approval before any writes to the user's Wix site. - Deterministic state management: Ships scripts and libraries for execution manifests, crosswalk state, artifact freshness validation, recovery logging, and completion reporting. - Use Case: A user asks to continue a Shopify-to-Wix migration that stopped mid-run. The Skill inspects migrations/<project>/ artifacts, finds the mapping plan is approved but setup verification is missing, and routes to the setup-discovery step without redoing completed work. ## Quick Start Ask the agent to start or continue a RePlatform migration for your store and let it inspect the migration project to determine the next step.

Frequently Asked Questions about replatform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a Shopify or WordPress site to Wix?

Start a migration run and provide the source site URL; the workflow infers the platform, asks for the acquisition mode and credentials, then runs discovery, mapping, setup, and import into a Wix managed headless site. All writes wait behind an explicit execution-plan approval.

How do I resume an interrupted migration run?

Re-invoke the migration and it resolves the active project under the migrations directory, then reads orchestration JSON artifacts to find the next incomplete step. Completed stages are skipped because each artifact is treated as a checkpoint only when well-formed.

Can I run a Wix migration in dry-run mode first?

Yes, setting DRY_RUN=true in config/wix.env runs the same generated setup and import code while skipping Wix calls at the shared boundary. Leaving dry-run for live writes requires explicit user approval, except for the initial new-site scaffold.

Does the migration build a customer-facing website by default?

No, the default delivery mode is management-only, which migrates data into a Wix managed headless backend without building a frontend. A storefront website is built only when the user explicitly opts into website mode.

What happens if the import partially fails?

Failed, deferred, or missing records are tracked in a local crosswalk and attempt journal, so recovery runs can target only missing, failed, or deferred records. Completion reporting reconciles extracted versus imported counts and flags mismatches.