claude-design-parity

Port Claude Design prototypes into codebases with two-pass ports and Playwright visual diffs.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/jeffmichaeljohnson-tech/claude-design-parity --skill claude-design-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-design-parity
Source: https://github.com/jeffmichaeljohnson-tech/claude-design-parity/tree/main
Command: npx skills add https://github.com/jeffmichaeljohnson-tech/claude-design-parity --skill claude-design-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, pixelmatch, pngjs, and includes scripts (resource) components.

What problem does it solve?

Port Claude Design prototypes into real codebases without losing wiring, state stores, or project conventions, enabling reliable parity checks against design outputs.

Core Features & Use Cases

  • Two-pass port discipline: literal port for visual fidelity, then re-wire for functional fidelity.
  • Automated visual parity verification via Playwright and pixel-diff reports for multiple routes and viewports.
  • Stack-agnostic design discovery: reads CLAUDE.md and repository layout to infer state idioms, bridges, and conventions.
  • Generates parity reports (design vs impl) to guide incremental porting and validation.

Quick Start

Invoke /claude-design-parity in a Claude Code session to begin a parity run against your project.

Frequently Asked Questions about claude-design-parity

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

FAQPage Schema
How do I port design prototypes into an existing codebase without losing state stores or project conventions?

Port design prototypes into a real codebase using a two-pass discipline: a literal port for visual fidelity, then a re-wire pass for functional fidelity. The tool reads CLAUDE.md and repository layout to infer state idioms and bridges, preserving invariants during the port.

How do I verify visual parity between a design prototype and its code implementation?

Verify visual parity using Playwright and pixel-diff reports. The tool runs automated visual parity verification across multiple routes and viewports, generating design vs implementation reports to guide incremental validation.

Can I use Playwright and pixelmatch to automate visual diff testing for UI porting?

Yes, Playwright and pixelmatch are used as core dependencies to automate visual diff testing. The tool captures screenshots across routes and viewports, then generates parity reports comparing design outputs against the implementation.

What's the best way to maintain design fidelity when converting prototypes to production code?

Maintain design fidelity by following a two-pass port discipline: first perform a literal port to match visuals exactly, then re-wire the code to integrate functional fidelity with existing state stores and bridges, validated by automated pixel-diff reports.

Does this design-to-code porting tool work with different tech stacks and state management patterns?

Yes, the tool is stack-agnostic. It reads CLAUDE.md and the repository layout to discover invariants, state idioms, and project conventions, allowing it to operate across both generic and specialized stacks during the porting process.

Why does my design prototype lose wiring and state connections when I port it to my codebase?

Wiring and state connections are lost when ports skip functional re-wiring. The tool solves this by reading CLAUDE.md and repository structure to discover existing state stores and bridges, then performing a second pass to re-wire the ported code for functional fidelity.