skills.rest
divinaarmuela
divinaarmuelaCOMMUNITY
Explore all skills by this author →
GitHub

rp-import-codegen

Generates migration readers, transforms, and Wix write specs from schema and mapping artifacts.

Updated Apr 19, 2026
Search Tags:#code generation#migration#etl#data import#ndjson#wix#replatforming
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill rp-import-codegen-divinaarmuela
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rp-import-codegen
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/replatform/resources/rp-import-codegen
Command: npx skills add https://github.com/divinaarmuela/Content --skill rp-import-codegen-divinaarmuela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning approved migration schemas and mapping plans into runnable import code is error-prone: hand-written Wix request shapes, slug sanitizing, bulk batching, and dedupe logic repeatedly ship bugs that only surface at execution time. This Skill generates the project-specific code layer from machine-readable artifacts so the migration runs through verified shared runtime primitives instead of ad-hoc code. ## Core Features & Use Cases - Source reader generation: Produces platform-agnostic extraction entrypoints that vendor the matching source adapter's transport (HTTP or CSV file readers) and write durable NDJSON extract files to disk. - Transform and write-spec generation: Emits thin transforms over the shared Wix build layer and per-entity write specs that call the verified rp-target-wix runtime, including Catalog V3 product shapes, bulk batching by endpoint limits, and crosswalk-based idempotent dedupe. - Execution artifacts and safety gates: Generates runnable setup/extract/import entrypoints, execution manifests, dry-run support, notification-mute preflight, and a mandatory code-safety review artifact when SAFE_MODE or DRY_RUN is enabled. - Use Case: After approving a mapping plan for a WordPress-to-Wix store migration, run this Skill to produce the reader, transforms, and import runner that rp-execute-import will execute, complete with a sample-preview gate before any live write. ## Quick Start Generate the migration import code for the active project from its source-schema.json, mapping-plan.json, and setup-plan.json artifacts.

Frequently Asked Questions about rp-import-codegen

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

FAQPage Schema
How do I generate migration import code from a mapping plan?▼

Provide the project's source-schema.json, mapping-plan.json, and setup-plan.json artifacts, then run the codegen workflow. It emits execution manifests, a source reader, transforms, write specs, and runnable setup, extract, and import entrypoints under the migration project.

How does the generated importer write products to Wix?▼

Generated importers use the Wix Stores Catalog V3 bulk create endpoint through the shared rp-target-wix runtime, batching by all endpoint limits at once such as 100 products and 1000 variants per request. Per-record creates are only used when no bulk equivalent exists.

Does the codegen support CSV file sources?▼

Yes, when source-schema.json has platform set to csv, it generates a file reader instead of an HTTP reader. The reader vendors a shared CSV parser, replays grouping layouts like blank-key continuation and sectioned rows, and materializes column-values entities depth-ascending.

How does the generated importer avoid duplicate records on re-run?▼

It dedupes by source ID before building each batch and records a durable sourceId-to-targetId crosswalk in NDJSON. Existing target entities found by name or slug safety nets are adopted into the crosswalk with their id and revision rather than silently skipped.

What happens when SAFE_MODE or DRY_RUN is enabled?▼

Codegen must produce a code-safety-review.md artifact verifying every write path passes safeModeOptions through the shared sanitizer and that dry-run uses the same code path with Wix calls skipped only at the shared send boundary. Execution approval stays pending until the review passes.

Why must generated code avoid hand-written Wix request shapes?▼

Hand-emitted endpoints repeatedly shipped wrong shapes such as lowercase Ricos enums and incorrect tag bodies that only failed at execution. The skill vendors verified request builders from rp-target-wix and treats its VERIFIED shapes as the source of truth over documentation examples.

Related Skills

Explore More Software Engineering Skills→
lync-cyberlync-cyber
133

platform-audit

Detect outdated AI IDE capability mappings and produce update plans for CataForge platform profiles.

Community
Advanced
nmrtnnmrtn
42

pm-interview

Generate a user interview guide and plan from a product assumption.

Community
Advanced
MRiabovMRiabov

engineer-plan-reviewer

Validate engineering plan artifacts against stage manifests and motion-trajectory contracts.

Community
Advanced
Hashzin-0Hashzin-0

veracidade-confiabilidade

Prevent AI hallucination by enforcing verification and explicit admission of uncertainty.

Community
Intermediate