Generated banner for Wix Headless Replatform
Generated logo for Wix Headless Replatform

Wix Headless Replatform

WixOfficialPublished by Wix

  • Skill
  • Workflow
  • Software development
  • MIT
  • Low risk
  • Has scripts

From the author

Clone, rebuild, migrate, or reverse-engineer a public website home page into a Wix Headless frontend while preserving source identity, SEO, interactions, and visual fidelity.
— the description by Wix

AutoGineer summary

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

This skill acts as a supervisor for cloning or migrating a public website's home page into a Wix Headless frontend. It manages the end-to-end process, including browser-based extraction, build planning, implementation, and quality assurance. The workflow ensures visual fidelity, SEO preservation, and structural integrity by utilizing a staged approach that moves from context resolution to final verification. It supports both standalone cloning and integration into existing migration projects via handoff files.

What it does

  • Clones or migrates a public home page to a Wix Headless frontend.
  • Performs browser-backed extraction to capture visual and structural evidence.
  • Generates a build plan based on a frozen extraction manifest.
  • Implements the frontend using Wix CLI Headless, Astro, TypeScript, and Tailwind.
  • Conducts automated visual review and gap-loop cycles to ensure quality.
  • Supports one-click continuation for automated migration workflows.

When to use it

  • When you need to clone a public website's home page into a new Wix Headless project.
  • When migrating an existing site to Wix Headless as part of a larger project.
  • When you require a high-fidelity frontend implementation that preserves source SEO and interactions.
  • When you need to automate the transition from a source website to a Wix-managed environment.

Advantages

  • Ensures visual and functional fidelity through strict extraction and review contracts.
  • Automates complex migration steps to reduce manual effort.
  • Maintains SEO and branding consistency during the transition.
  • Provides a structured, repeatable process for frontend reconstruction.
  • Supports iterative gap recovery to handle implementation challenges.

Usage examples

“Clone the website at example.com into a new Wix Headless project.”
The agent initiates the standalone cloning workflow, resolves the home page, and begins the extraction and build process.
“Continue the migration for the site at example.com using the handoff file at path/to/handoff.json.”
The agent enters migration mode, loads the specified handoff, and resumes the implementation or verification stage.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/wix/wix-headless-replatform/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip wix-headless-replatform.zip -d .agents/skills

Documentation by Wix

wix-headless-replatform

Role

Drive a close-enough, visually polished Wix Headless frontend from a source website. The implemented scope is one resolved home page and the default output is projects/<project-name>, derived from the hostname. Use Wix CLI Headless, Astro, TypeScript, and Tailwind; use React only for complex interactive islands. Reject additional-page and explicit-URL scope with an actionable explanation until a later approved workflow defines page resolution and shared evidence across routes.

This entry skill is the supervisor. It decides the next workflow stage and loads only the resource for that stage. Do not preload every resource or reference: stage-specific rules are deliberately demand-loaded.

Two modes exist:

  • Standalone clone: source URL to a new, real Wix CLI Headless project.

  • Migration phase: --handoff <migration-project>/website/handoff.json continues on the migration-owned destination. Never omit --handoff for an integrated migration: the standalone command creates a second site.

Non-negotiable invariants

  • Treat the requested public branded homepage as authorized; apply the boundaries in references/safety.md without asking a separate routine authorization question.

  • Browser-backed extraction is mandatory. Do not substitute HTML-only extraction.

  • Resolve the home page before capture. Build only from a validated frozen extraction manifest; raw observations are never builder inputs.

  • A standalone output must be a successful Wix CLI scaffold with valid Wix identity and runnable dev and build scripts. Never hand-create a Wix-shaped substitute.

  • In migration mode, reuse the handoff's site/project and route/data-binding intent; do not create or retarget a second destination.

  • Preserve source structure, first-viewport evidence, chrome hierarchy, source assets, fonts, core interactions, SEO, internal URL behavior, and branded fallback behavior.

  • A build is not completion. Completion requires the accepted post-build visual-review and gap-loop evidence described by rp-qa-gap-loop, plus optional facelift acceptance only when the user explicitly selected facelift mode.

Supervisor protocol

On every new or resumed run:

  1. Resolve the source URL, output directory, and mode. In migration mode read website/handoff.json and docs/site-clone/frontend-automation-state.json first.

  2. Select the first incomplete stage from the table below and read only that resource's SKILL.md plus the references it explicitly needs.

  3. Execute that stage until it writes its required durable artifact, or records a specific genuine blocker with evidence and an exact unblock action.

  4. Re-select the stage after every boundary. Do not say that a required next step “needs to happen” and end the run; load its resource and perform it.

StageLoad only whenResourceDurable outcome
Contextmode, scope, project, or browser environment is unresolvedresources/rp-project-context/SKILL.mdvalid context, approval record, runnable project/plan state, or blocker
Evidencefrozen home-page extraction is absent or staleresources/rp-source-evidence/SKILL.mdvalidated extraction/latest.json and frozen manifest, or global blocker
Implementationfrozen build plan exists and home UI is incompleteresources/rp-ui-implementation/SKILL.mdmanifest-hash-aware runnable home implementation
Verify and improvebuild, QA, comparison, review, fix, report, release, or receipt is incompleteresources/rp-qa-gap-loop/SKILL.mdaccepted result, done_with_gaps, or global blocker
Optional faceliftnormal clone accepted and automation state says facelift is requestedresources/rp-facelift/SKILL.mdaccepted facelift review, or blocker

When frontendPhase.allowedNow is plan, complete only the plan-eligible context and evidence work and leave a resumable plan-state record. When it is build, continue through implementation and verification against the migration-owned project.

One-click continuation

A migration handoff declaring automationMode: "one_click" authorizes routine scope and frontend checkpoints. Record those approvals in docs/site-clone/frontend-automation-state.json; do not pause to ask whether to proceed with a required stage, screenshot review, or authorized gap-fix pass. An explicit facelift request may be carried from 1-click intake, but it remains gated until normal clone acceptance; 1-click never implies facelift by itself.

In a one-click build run, keep selecting and executing stages until one of these durable outcomes exists:

  • website/completion.json is valid and the latest visual review is complete with no open critical/high identity finding; or

  • five visual gap cycles have been completed and website/completion.json records the truthful terminal status done_with_gaps with the final reviewed evidence; or

  • a genuine blocker is recorded with owner, evidence, attempted recovery, and exact next authority/action needed.

An owned local extraction gap is not a genuine blocker. Continue unrelated work, use no more than two distinct targeted recovery attempts, then build the affected dependency closure provisionally and surface post-assembly choices in final-report.json and .md.

Before classifying a shell, browser, or network failure as a blocker, use the repo-local Wix/Yarn toolchain PATH ordering and follow the recovery order in resources/rp-project-context/SKILL.md: aligned-shell retry, then the required browser/network escalation and retry, then blocker only if it still fails or approval is pending. After every gap iteration, immediately return to the stage table; never treat a first build, a reported plan, or backend import as frontend completion.

Commands

Run node scripts/site-clone.mjs <source-url> for standalone mode, or node scripts/site-clone.mjs <source-url> --handoff <path> for migration mode. The active resource gives the exact commands and inputs for its stage.

References

Resources load their own references. The shared contracts are kept under references/: safety.md, workflow.md, extraction-schema.md, output-contract.md, qa-checklist.md, and the interaction/layout/control/normalization/gap contracts.

Files

references/workflow.md

Home-page reconstruction workflow

Modes and scope

The skill runs as a standalone clone or a migration phase selected explicitly by --handoff <website/handoff.json>. Migration mode reuses the migration-owned Wix site/project and binding intent. Standalone mode provisions one real Wix CLI Headless Astro project.

The implemented extraction/build scope is one home page. --scope must be home and --urls is not accepted. A later approved workflow must define resolution, evidence conflicts, and shared ownership for additional pages.

When a migration handoff allows only plan, complete project context plus frozen extraction/build planning and stop resumably. When it allows build, continue through implementation and verification on the migration-owned project.

Browser preflight

Before browser capture run:

node scripts/browser-extraction-preflight.mjs --project-root <project-root>

Use --fix for supported remediation. In this repository, align to the documented NVM/Yarn toolchain first. For a sandboxed browser/network failure, request the required escalation and retry before it becomes a global blocker.

Stage order

  1. Provision or verify the Wix project boundary when build mode requires it.

  2. Resolve the requested URL to one public home page and destination / route.

  3. Capture browser observations at desktop/tablet/mobile with normalization audit and persist typed, sanitized, hash-bound replay packets.

  4. Run the independent semantic, structural, behavior, and visual detector ensemble; segment visible regions and assign ownership.

  5. Plan recursive jobs and extract foundation, metadata, shared chrome, sections, and arbitrarily nested components deepest-first.

  6. Classify and recover gaps within the bounded local budget.

  7. Enforce the rendered-content boundary, then validate/harden hashes and freeze accepted or provisional specs. Content extraction must use browser-rendered text and exclude script, style, noscript, and template descendants. Preserve visible pre/code content with explicit provenance. If source-code contamination is still detected, omit only the affected strings, create an owned local gap, and continue unrelated units.

  8. Derive the build plan and component-selection evidence from the manifest. If an approved registry item is selected, expose only its resolved binding and contractRef to the builder.

  9. Build foundation, metadata, chrome, recursive children, then ordered sections.

  10. Build and run unit/page browser QA; revise only affected owners.

  11. Produce the final gap report and, when applicable, the migration receipt.

Resolution/extraction may create observations and specs, but never destination UI. Building consumes only frozen specs, generated selection evidence, and any selected component's compact agent contract. It may not browse the source, scan the registry, read candidate/review material, or read raw observations. A missing builder fact returns through an owned extraction-gap request.

Page resolution

Normalize the input, remove fragments/query discovery noise, follow redirects with a read-only request, preserve an applicable locale home prefix, inspect canonical URL, and record requested/candidate/resolved/canonical URLs. Ambiguous home identity is a global blocker with an exact user action; do not guess a route or build the supplied non-home page as home.

Capture and safe probing

Capture the clean page after stable settling, controlled scrolling, lazy-content discovery, and consent/obstruction normalization. Retain raw and normalized evidence plus every normalization action.

Probe only public unauthenticated presentation state. Allow scroll, hover, focus, keyboard navigation, resize, bounded wait, tabs, disclosures, menus, and confirmed carousel controls. Block navigation, mutating requests, forms, auth, cart/checkout, purchase/booking, uploads, account/admin state, destructive actions, and unclassified clicks. Reset state between branches and retain an audit of blocked requests/actions.

Freeze and anti-stuck behavior

Every visible concern has one owner, explicit ignore, or owned gap. High-confidence detector results that meet calibrated precision may freeze automatically. Medium results become typed decisions for the orchestrating agent. Low/invalid/abstained results become gaps.

Local gaps never block unrelated work. Try at most two distinct targeted tactics. If the fact remains unavailable, freeze/build the reliable contract provisionally and propagate provisional status only through declared dependencies. The agent may make a conservative evidence-backed layout/semantic choice, but cannot invent copy, assets, links, business actions, or behavior.

Only unresolved home identity, page-wide unusable capture, corrupt artifact integrity, unisolatable safety failure, or inability to assemble/build/serve any viable shell stops the run globally.

Replay a retained immutable capture without reopening the source with:

node scripts/replay-extraction.mjs --out <project> [--capture <capture-id>]

Replay first verifies spec, dependency, manifest, and observation-packet hashes. A changed detector/projection or typed patch creates a new capture and report; the source capture remains untouched.

Build order and registry

Verify extraction/latest.json and its manifest before creating UI. The build ledger is keyed to manifest/spec hashes; a changed hash invalidates the affected downstream entries.

Install the foundation once, apply metadata, then build shared chrome, recursive child components, and top-level sections in dependency/source order. Use Astro for static UI and React only for useful islands. Preserve exact content/assets, layers, geometry, responsive behavior, accessibility, and observed end states.

Filter the local shadcn-format registry by contract, its approved hash-pinned capability manifest, framework/runtime, license, accessibility, responsive, SSR, RTL, reduced-motion, dependency, and human-approval requirements. Resolve only declared axes, slots, states, and compositions, and record selection/rejection evidence. An eligible selection is copied from its pinned local source only after its exact source hash is verified; exact dependency versions, required Astro integration configuration, and build/registry-installation.json record the installation. The builder consumes the resolved selection and only the selected item's hash-pinned contract.md; registry internals and candidate material are not agent context. Use a bounded custom builder when no item qualifies and emit a source-neutral qa/registry-opportunities.json; never fetch a floating live-registry component.

Verification and completion

Verify each unit at its required viewports against frozen acceptance fields, then verify the assembled home page. qa/visual-qa.json contains unitAcceptance results for every frozen required criterion and pageAcceptance results for page checks; pending browser evidence is reported as pending, never silently passed. Findings return to their smallest owner. Do not use unrelated global CSS or another section to hide a gap.

Generate final-report.json and .md. For every unresolved/user-accepted gap state what could not be imported reliably and why, evidence/confidence/attempts, provisional output, assumptions/omissions, affected checks/dependencies, and choices to accept, retry/fix, provide material, replace, omit, or leave unresolved.

Record a post-assembly decision with:

node scripts/record-gap-decision.mjs --out <project> --gap <gap-id> --decision <choice>

No remaining gap plus complete browser verification may become done. Remaining local gaps become done_with_gaps; only a global blocker is blocked. In one-click mode do not pause before assembly for local gaps.

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

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

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-headless-replatform · 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 wix-headless-replatform.zip