harness-design-web

Generate token-bound web components for React, Vue, or Svelte projects.

18|11|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-design-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-design-web
Source: https://github.com/Intense-Visions/harness-engineering/tree/main/agents/skills/claude-code/harness-design-web
Command: npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-design-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates design tokens and design intent into token-bound web components, ensuring consistent UI while eliminating hard-coded values.

Core Features & Use Cases

  • Scaffold token-bound web components from design-system tokens for React, Vue, and Svelte projects
  • Detect framework and CSS strategy automatically to generate framework-consistent code
  • Enforce design constraints and anti-patterns from DESIGN.md during generation

Quick Start

Run this skill against your project to scaffold token-bound web components from your design tokens.

Frequently Asked Questions about harness-design-web

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

FAQPage Schema
How do I generate web components from design tokens for React, Vue, or Svelte?

To generate web components from design tokens, this Skill translates your design-system/tokens.json into framework-specific scaffolding, automatically detecting whether you are using React, Vue, or Svelte to ensure UI consistency.

Can I enforce design constraints and prevent anti-patterns when generating UI components?

Yes, you can enforce design constraints by placing your design intent and rules inside a design-system/DESIGN.md file, which the generator reads to prevent hard-coded values and UI anti-patterns during token-bound component scaffolding.

Do I need a specific CSS strategy to scaffold token-bound web components?

A defined CSS strategy is required to scaffold token-bound web components effectively, as the generation process applies your design tokens to color, typography, and spacing based on the detected CSS approach.

What files do I need before scaffolding token-bound web components?

Before scaffolding token-bound web components, you need design tokens located at design-system/tokens.json and your design intent documented at design-system/DESIGN.md to guide the framework-specific code generation.

Why use design tokens to generate web components instead of hard-coded values?

Using design tokens to generate web components eliminates hard-coded values for color, typography, and spacing, ensuring consistent UI across your React, Vue, or Svelte projects while strictly enforcing your design system constraints.