Rp Project Intake
WixOfficialPublished by Wix
- Skill
- Workflow
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The rp-project-intake skill manages the initial decision-making process for migration projects. It guides the user through selecting project scope, delivery modes, destination site types, and notification settings. By standardizing how these decisions are captured and recorded in the project's orchestration state, it ensures that subsequent migration stages have the necessary configuration to proceed. It supports both standard step-by-step interaction and an accelerated one-click mode for experienced users.
What it does
- Resolves project precedence and initializes missing project documentation.
- Determines delivery modes including management, website, or combined configurations.
- Collects destination site type and business type for new Wix sites.
- Manages notification mute decisions for existing site migrations.
- Records configuration choices like management import mode and optional UI facelift requests.
- Supports a one-click automation mode to collect all missing intake decisions at once.
When to use it
- When a migration router reports missing project, delivery mode, or destination strategy.
- At the start of a new migration project to establish core configuration.
- When an existing destination site requires a decision on notification muting.
- When a user explicitly requests a one-click intake process to expedite setup.
Advantages
- Ensures consistent project configuration across different migration runs.
- Prevents invalid or incomplete destination site type selections.
- Provides a clear path for handling sensitive notification settings on existing sites.
- Reduces manual overhead by grouping intake questions in one-click mode.
Usage examples
- “I want to migrate my backend and my storefront to a new Harmony site.”
- The agent identifies the delivery mode as management_and_website, prompts for the Harmony business type, and records these in the orchestration state.
- “Run the intake in one-click mode for this project.”
- The agent sets automationMode to one_click and prompts for all missing intake decisions simultaneously to finalize setup.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/wix/rp-project-intake-zo6c/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip rp-project-intake.zip -d .agents/skills
Documentation by Wix
rp-project-intake
Use when the router reports unresolved project, delivery mode, destination strategy, or source mode.
Resolve project precedence: explicit user project, current project context, the sole project under the migrations root, otherwise ask the user to choose. Never infer from a sibling project.
Project initialization also creates EXPECTATIONS.md at the project root when it is
missing. Mention it as an optional place to record expectations; do not make it an intake
question or replace a user's existing file.
Resolve delivery mode before destination creation: default to management; choose
website for frontend only; choose management_and_website when the user wants both a
backend migration and a customer-facing storefront. Accept both as an input alias for
management_and_website, then record the canonical value in orchestration/decisions.json.
For a new destination site, the site type is an explicit operator choice with no
default: Headless (a website developed in code), Wix Studio, or Wix Harmony. It decides
where the imported data lives and cannot be changed later as a setting. A generic "Editor"
answer is incomplete until Studio or Harmony is named; the classic Wix Editor is not offered.
Ask it together with Harmony's business type as one combined question — store,
bookings/services, another business, or "not sure, start blank" — never as two questions.
Record it with orchestration-state.js decide --key targetSiteType --value <type> [--business-type store|bookings|other]; a Harmony answer that names no business type records
unknown. A choice the operator already gave counts; do not ask again. rp-destination raises
the durable request when it is still missing. Existing-site adoption needs no type.
For an existing destination site, ask whether to mute its notifications before the first
write. The router returns the exact question and choices
(missing_notification_mute_decision, question); show them in those plain words and do not
pick for the operator. Mute: Wix stops all site notifications, including customers' emails,
until someone unmutes, and the live business may miss real customer notifications during the
import. Don't mute: customers and the owner may get emails for imported records (orders,
bookings, forms, RSVPs, and so on). Record the answer with orchestration-state.js decide --key notificationMute --value on|off (it also writes WIX_MUTE_NOTIFICATIONS). A new site is
always muted and is never asked. A supervised replatform run raises this question itself as
a durable request; answer it with replatform answer. Once setup has written to the site the
answer cannot change.
For delivery modes that include management, also record managementImportMode. Default to
standard; accept an explicit user choice of quick at intake even before the source URL is
probed. The later source-inputs/probe result validates whether a matching quick adapter exists;
never promise quick support merely from the user's choice.
Record faceliftMode=requested only when the user explicitly asks for a post-clone UI/UX
facelift. It is optional, defaults to off, and is not a substitute for normal clone fidelity.
In explicit user-requested 1-click mode include this choice in the initial grouped intake so the later, separate
facelift stage is authorized without another routine approval.
In normal mode ask only the current missing decision. In explicit user-requested 1-click mode
record automationMode=one_click with source=user, collect every still missing intake value
together (including the existing-site mute question), record the answers, and continue. Never infer one-click from an uploaded file or
execution surface. Delegate all destination,
source-file, and credential procedures to their dedicated modules.
Output
The resolved project, plus orchestration/decisions.json entries for whichever of
deliveryMode, managementImportMode, targetSiteType (with targetSiteBusinessType for
Harmony), notificationMute (existing sites), faceliftMode, and automationMode this run resolved. This is what a dispatched run must produce.
Files
- ATTRIBUTION.mdAdded by AutoGineer846 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md4.2 KiB
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.
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 · skills/wix-replatform/resources/rp-project-intake · 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.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download rp-project-intake.zip