rp-mapper

Maps discovered source entities and fields to Wix targets with deterministic resolution and lossiness documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Migrating a site to Wix requires deciding what every source entity and field becomes on the Wix side, and hand-authoring those mappings is slow, inconsistent, and prone to silently dropping data. This Skill produces machine-readable mapping artifacts and human review summaries so every column is either mapped or explicitly skipped. ## Core Features & Use Cases - Deterministic mapping resolution: Runs scripts/resolve-mapping.js to join discovered CSV headers, vendor overlays, and the Wix target spec, producing mapping-resolution.json and an explicit residue queue of unmapped columns, unsupported targets, and unfilled required fields. - Faithfulness ledger: Records lossy transformations, skipped entities, hierarchical-to-flat taxonomy drops, and unverified Wix targets in mapping-gaps.json before execution, so users are warned before consent. - Review workflow: Generates mapping-plan.md and mapping-summary.md, then pauses at a mapping review checkpoint before downstream setup and code generation. - Use Case: After discovering a Shopify CSV export, run the resolver to auto-map known columns, then decide only the residue entries and produce a reviewable plan mapping products, categories, and orders to Wix Stores and eCommerce entities. ## Quick Start Ask the assistant to run the rp-mapper skill on the discovered source schema in migrations/<project> to produce the mapping plan and review summary.

Frequently Asked Questions about rp-mapper

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

FAQPage Schema
How do I map a source data export to Wix entities?

Run the deterministic resolver with the discovery fileset to join observed headers against the vendor overlay and Wix target spec. It writes mapping-resolution.json and a residue queue; you then decide only the unmapped columns and produce the mapping plan and review summary.

What does the resolve-mapping script output?

It writes mapping-resolution.json with field mappings, coverage stats, and derived entities, plus mapping-residue.json listing unmapped columns, unsupported targets, unfilled required fields, and overlay drift. Exit code 2 means a required Wix input is unfilled or the overlay references an unknown canonical field.

How are unmapped source columns handled in a Wix migration?

Every unmapped column in the residue must be explicitly mapped to a canonical field or recorded as intentionally skipped with a reason. Leaving entries undecided risks silently dropping data when a vendor overlay profile is stale.

Does the mapper handle hierarchical source taxonomies?

Yes. When a source entity is hierarchical but the Wix target is flat, such as Blog categories, the mapper requires a faithfulness-ledger entry recording that the parent/child hierarchy is dropped, or notes a CMS collection with a parent reference as the alternative.

What happens if a Wix field or enum cannot be verified?

Unverified Wix field, enum, or app names are marked as unverified in the mapping plan and surfaced before execution rather than guessed. The mapper consults the rp-target-wix domain knowledge and verified contracts first.