implement-design

Integrate Claude Design prototypes into React, Vite, and Tailwind CSS codebases.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/evanharmon1/harmon-devkit --skill implement-design-evanharmon1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-design
Source: https://github.com/evanharmon1/harmon-devkit/tree/main/ai/skills/frontend/implement-design
Command: npx skills add https://github.com/evanharmon1/harmon-devkit --skill implement-design-evanharmon1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill bridges the gap between visual design prototypes and production-ready code, preventing the common pitfalls of manual handoff, inconsistent styling, and accessibility regressions.

Core Features & Use Cases

  • Defensive Ingestion: Safely parses Claude Design handoff bundles regardless of format variations.
  • Token Reconciliation: Maps design tokens to a canonical Tailwind v4/shadcn/ui system, ensuring runtime consistency.
  • Automated Verification: Enforces WCAG AA contrast standards and responsive layout integrity across browsers.
  • Use Case: When you have a finished design in Claude Design, use this skill to bootstrap a new design system or implement a feature while ensuring all brand assets, accessibility gates, and responsive states are perfectly aligned with your existing codebase.

Quick Start

Use the implement-design skill to ingest the handoff bundle located in the specs directory and begin the reconciliation process.

Frequently Asked Questions about implement-design

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

FAQPage Schema
How do I turn design handoffs into React and Tailwind CSS code?

To turn design handoffs into React and Tailwind CSS code, you parse visual prototypes and reconcile design tokens into a canonical Tailwind v4 and shadcn/ui system. This process ingests handoff bundles and maps them directly to your existing component architecture.

What is design token reconciliation in a Vite and Tailwind v4 codebase?

Design token reconciliation in a Vite and Tailwind v4 codebase is the process of mapping visual design tokens to a canonical shadcn/ui system. It ensures runtime consistency across multiple themes and viewports during component implementation.

How do I automate WCAG AA contrast checks when implementing frontend designs?

You automate WCAG AA contrast checks during frontend design implementation by using built-in automated verification gates. These gates enforce accessibility standards and responsive layout integrity across browsers before code reaches production.

Does this design implementation process work with existing React and Vite setups?

Yes, the design implementation process works with existing React and Vite setups by safely ingesting handoff bundles and integrating them into your current codebase. It ensures production-grade quality through cross-browser testing and strict adherence to your semantic design system.

How do I implement a new feature from a design handoff while keeping brand assets aligned?

To implement a new feature from a design handoff while keeping brand assets aligned, you ingest the handoff bundle and let the tool reconcile assets with your existing codebase. This ensures all responsive states and accessibility gates are perfectly matched to your production environment.

Do I need Playwright to verify cross-browser layout integrity for design prototypes?

Yes, you need Playwright to verify cross-browser layout integrity for design prototypes. The automated verification process uses Playwright to test responsive layouts across multiple viewports and enforce strict contrast gates during the component implementation phase.