migrate-code-page-visual
/migrate-code-page-visual
Ensures a migrated page visually matches the original Kentico Xperience 13 page. Uses Playwright to compare both pages and iteratively fixes styling, layout, and content differences. Use when a page migration results in visual discrepancies that need to be corrected.
- Author
- kentico ↗
- Repository
- xperience-by-kentico-kenticopilot ↗
- Licence
- MIT
- Last repository change
- 14.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 14.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Ensures a migrated page visually matches the original Kentico Xperience 13 page. Uses Playwright to compare both pages and iteratively fixes styling, layout, and content differences. Use when a page migration results in visual discrepancies that need to be corrected.
Arguments
/migrate-code-page-visual [page-name] [legacy-page-url] [new-page-url]
Original author description
Ensures a migrated page visually matches the original Kentico Xperience 13 page. Uses Playwright to compare both pages and iteratively fixes styling, layout, and content differences. Use when a page migration results in visual discrepancies that need to be corrected.
How it works
- Input Parameters
- Structure of the projects
- Context
- Important Principles
- Visual Matching Steps
- Output format
SKILL.md preview
--- name: "migrate-code-page-visual" description: "Ensures a migrated page visually matches the original Kentico Xperience 13 page. Uses Playwright to compare both pages and iteratively fixes styling, layout, and content differences. Use when a page migration results in visual discrepancies that need to be corrected." argument-hint: "[page-name] [legacy-page-url] [new-page-url]" compatibility: "Requires Playwright MCP" --- You are tasked with ensuring that the migrated page visually matches the original legacy page. ## Input Parameters - **Page Name** - The name/path of the page being matched (e.g., 'home', 'doctors'). - **Legacy Page URL** - The URL of the page in the KX13 project (e.g., <https://localhost:5001/en-us/home>). - **New Page URL** - The URL of the page in the XbyK project (e.g., <http://localhost:60444/en-us/home>). ## Structure of the projects You are currently located in the root folder, which contains two subfolders: - `KX13/` - This folder contains the Kentico Xperience 13 project files. This is the legacy/source project. - `XbyK/` - This folder contains the Xperience by Kentico project files. This is the new project. ## Context The page migration from KX13 to XbyK has been completed in the previous step. The result is a functional page, but it does not visually match the original. Your task is to make the new page look completely identical to the old one. ## Important Principles 1. **Dynamic content** - When migrating a page, ensure that everything that was fetched dynamically from the database will still be dynamically fetched from the database. Nothing can be statically hardcoded in the new project if it was dynamic in the legacy project. 2. **Pixel-perfect matching** - The goal is to make the pages visually identical, including layout, spacing, colors, fonts, and responsive behavior. 3. **Preserve functionality** - While fixing visual issues, ensure all functionality remains intact. ## Visual Matching Steps 1. **Ensure XbyK is running** - Start the application if not already running. 2. **Capture both pages** - Use Playwright MCP to navigate to both pages: - Navigate to the legacy page URL - Take a snapshot or screenshot for reference - Navigate to the new page URL - Take a snapshot or screenshot for comparison 3. **Identify visual differences** - Compare the two pages and note all differences: - Layout and structure - Colors and backgrounds - Typography (fonts, sizes, weights) - Spacing and margins - Images and media - Interactive elements (buttons, links, forms) 4. **Fix each difference** - For each visual discrepancy: - Identify the source of the difference (CSS, HTML structure, missing content) - Make the necessary changes in the XbyK project - Prefer fixing via CSS/styling over changing HTML structure - Implement retrieval of missing content dynamically from the database - Nothing can be hardcoded if it was dynamic in the legacy project 5. **Rebuild and restart** - After making changes: - Verify the project builds without errors - Restart the XbyK application 6. **Verify the fix** - Use Playwright MCP to check if the difference is resolved 7. **Iterate** - Repeat steps 3-6 until both pages are visually identical ## Output format When done, provide the user with this exact output (without any additional text): ```markdown # Migration Complete Page visual match adjustment has been successfully completed. **Next steps:** - Review the changes to ensure everything looks as expected. - Continue migrating other pages by repeatedly running migrate-code-page-widgets and migrate-code-page. ```
Versions
The database has no other skills named migrate-code-page-visual.
Database snapshot: 13.11.2026 · package version 7feb03585e5b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100migrate-code-page
Migrates a page from a Kentico Xperience 13 project to Xperience by Kentico. Converts controllers, views, layouts, content retrieval, and all dependencies for the specified page. Use when migrating the business and presentation logic of a specific page after its Page Builder… - 100migrate-code-page-widgets
Migrates Page Builder widgets and sections from a Kentico Xperience 13 page to Xperience by Kentico. Identifies and converts all widget and section components used by the specified page. Use when migrating Page Builder features for a specific page before migrating the page logic itself. - 100update-xperience
Update Xperience by Kentico to a newer version - regenerate the DancingGoat example from the new project template, keeping this repository's changes, bump its Kentico packages, and optionally raise the libraries' minimum Xperience version (Kentico NuGet and npm packages). Use… - 100playwright
Capture a screenshot of a URL or local page and load it into context for a visual check. Use when asked to check visually, use playwright, screenshot a page, see or look at the design yourself, or verify a layout on desktop and mobile widths. - 90figma-to-page
Implement a frontend page or component from a Figma URL or node using Figma MCP and Playwright QA. Use when exact visual, copy, and structural fidelity to Figma is the top priority. - 100playwright-testing
Use when writing Playwright E2E tests — browser automation, visual regression testing, Page Objects, fixtures, and reliable test patterns.