skills.rest
peppone-choi
peppone-choiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify-frontend-parity

Verify frontend parity against legacy PHP screens and the SPA plan.

Updated May 29, 2026
Search Tags:#frontend#UI#verification#legacy#SPA#parity
One-click install
npx skills add https://github.com/peppone-choi/opensamguk --skill verify-frontend-parity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-frontend-parity
Source: https://github.com/peppone-choi/opensamguk/tree/main/.claude/skills/verify-frontend-parity
Command: npx skills add https://github.com/peppone-choi/opensamguk --skill verify-frontend-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that the new frontend implementation accurately reflects the functionality, data display, and UI components of the legacy PHP system, preventing feature gaps and inconsistencies.

Core Features & Use Cases

  • Parity Verification: Compares frontend routes, displayed data, UI elements, and permission-based access against legacy screens and the SPA plan.
  • Use Case: After developing new features in the frontend, run this Skill to confirm that all legacy screens have corresponding frontend implementations, display the same information, and use comparable UI components.

Quick Start

Run the verify-frontend-parity skill to check the parity between the legacy PHP screens and the current frontend implementation.

Frequently Asked Questions about verify-frontend-parity

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

FAQPage Schema
How do I verify my new SPA frontend matches legacy PHP screens?▼

Verify SPA frontend parity against legacy PHP screens by comparing frontend routes, data display, and UI components with legacy code references to prevent feature gaps and inconsistencies.

What is frontend parity verification for legacy system migration?▼

Frontend parity verification checks that new implementations accurately reflect the functionality, data display, and UI components of the legacy PHP system, ensuring no features are lost during migration.

How do I check if all legacy screens have corresponding frontend implementations?▼

Check legacy screen coverage by utilizing file system checks and command-line tools to compare frontend routes and component structures against legacy PHP code references and the SPA plan.

Can I verify role-based access control parity between my new frontend and legacy system?▼

Yes, you can verify role-based access control parity by assessing permission-based access in the new frontend implementation against the legacy PHP screens and SPA plan requirements.

Does frontend parity verification assess real-time updates and page count?▼

Yes, frontend parity verification assesses page count, data display, UI component presence, role-based access control, and real-time updates to ensure complete functional matching with the legacy system.

What's the best way to confirm UI component presence in a frontend migration?▼

The best way to confirm UI component presence is running a verification skill that compares frontend component structures against legacy PHP screens and the SPA plan using command-line tools.

Related Skills

Explore More Software Engineering Skills→
skyasu2skyasu2
2

validation-analysis

Analyze post-commit validation results to generate a prioritized remediation plan.

Community
Intermediate
kimjuyoung1127kimjuyoung1127

page-register-upgrade

Upgrade the /register route UI, data flow, and behavior for feature parity.

Community
Intermediate
findinfinitelabsfindinfinitelabs

react-typescript-frontend

Build a type-safe Chuukese React frontend with Mantine UI v8 and Vite.

Community
Intermediate
nmdranmdra
26

skill-creator

Develop, evaluate, and optimize AI skill units with automated testing and benchmarking.

Community
Advanced