migrate-shared-component
OfficialMigrate shared layout components across projects
Software Engineering#migration#dynamic content#playwright verification#dependency migration#xperience by kentico#kentico xperience 13#shared component
AuthorKentico
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Migrating a shared header/footer/navigation-style component from a legacy Kentico Xperience 13 codebase to Xperience by Kentico is hard because you must preserve both behavior and dependencies without breaking dynamic data retrieval.
Core Features & Use Cases
- Dependency-aware migration: Locates the shared component in the source project and migrates it along with relevant dependent components/pages/services.
- Behavior parity for dynamic content: Ensures anything that was dynamically fetched in the legacy project remains dynamically fetched in the new project to avoid incorrect hardcoding.
- Verification with build + visual checks: Builds the target project and uses Playwright MCP to confirm the migrated UI matches the legacy rendering (styling, content, and text).
Quick Start
Run the migrate-shared-component skill and provide the shared component name and the legacy page URL where that component appears.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: migrate-shared-component Download link: https://github.com/Kentico/xperience-by-kentico-kenticopilot/archive/main.zip#migrate-shared-component Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.