migrate-page-visual

Compare legacy and migrated Kentico Xperience 13 pages with Playwright screenshots and apply iterative UI fixes.

14|7|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill migrate-page-visual
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-page-visual
Source: https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kx13-codebase-migration/skills/migrate-page-visual
Command: npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill migrate-page-visual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It fixes visual mismatches after migrating a Kentico Xperience 13 page so the new Xperience by Kentico page renders identically.

Core Features & Use Cases

  • Playwright-based visual comparison: Screenshots and diffs legacy vs migrated pages to locate layout, typography, spacing, and media discrepancies.
  • Iterative page correction: Applies targeted fixes in the XbyK project (prefer CSS/styling) while preserving the page’s existing behavior.
  • No hardcoding of dynamic data: Ensures migrated output continues to fetch the same data dynamically rather than freezing it as static content.

Use Case: When a content team reports that a migrated page looks “almost right” (off by spacing, fonts, or alignment), use this skill to drive iterative, verifiable visual corrections until the page is visually identical.

Quick Start

Ask the agent to run migrate-page-visual with the page name, the KX13 legacy page URL, and the XbyK new page URL for Playwright to compare and iterate until the visuals match.

Frequently Asked Questions about migrate-page-visual

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

FAQPage Schema
How do I fix visual mismatches when migrating Kentico Xperience 13 pages to Xperience by Kentico?

To fix visual mismatches during Kentico Xperience 13 page migration, compare legacy and new pages using Playwright screenshots, apply targeted CSS styling adjustments, and iterate through verify-build-restart cycles until the pages are pixel-perfect.

How does Playwright visual regression testing work for migrated Kentico pages?

Playwright visual regression testing captures screenshots of both legacy and migrated Kentico pages, generates visual diffs to locate layout and typography discrepancies, and drives iterative UI corrections until the rendering matches perfectly.

Can I hardcode dynamic content during page migration to make styling alignment easier?

You must not hardcode dynamic content during page migration. The process requires strict preservation of dynamic data sourcing so the migrated Xperience by Kentico page continues fetching data dynamically rather than freezing it as static output.

What's the best way to handle responsive layout and CSS fixes after a Kentico migration?

The best way to handle responsive layout and CSS fixes after a Kentico migration is applying targeted styling adjustments within the new project while preserving existing behavior, then verifying the results through repeated Playwright screenshot comparisons.

Why does my migrated Kentico page look almost right but still has spacing and alignment issues?

Migrated Kentico pages often retain spacing and alignment issues due to divergent styling between projects. Iterative visual comparison using Playwright identifies these exact discrepancies, allowing for targeted CSS corrections until the page is visually identical.

Do I need Playwright to verify pixel-perfect page migrations in Xperience by Kentico?

Playwright is required to verify pixel-perfect page migrations in Xperience by Kentico. It performs the legacy vs new page screenshot comparisons and visual diffs needed to locate rendering discrepancies and drive iterative UI fixes.