mp-design-ui-3

Generate multiple UI component variants in distinct design styles for Svelte, React, Vue, and HTML projects.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-design-ui-3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mp-design-ui-3
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/skills/mp-design-ui-3
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-design-ui-3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the slow, subjective process of exploring design directions by quickly producing multiple UI styles for the same component or page.

Core Features & Use Cases

  • Multi-style UI variant generation: Creates N variants across selected design styles (e.g., brutalism, cafe, cosmic) for side-by-side comparison.
  • Framework-aware targeting: Detects your project framework from dependencies and infers the correct file extension and scope (component vs page).
  • Winner finalization with tokens: Moves the chosen variant to the target path and generates a design-tokens.md file extracted from the winning style.

Quick Start

Run the Skill to generate five design variants for your LoginForm component in Svelte by calling: /mp-design-ui-3 LoginForm --count 5 --styles brutalism,cafe,cosmic,luxury,editorial

Frequently Asked Questions about mp-design-ui-3

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

FAQPage Schema
How do I generate multiple UI variants for a component to compare design styles?

Generating UI variants involves spawning parallel subagents to create multiple styled versions of a component in your source directory. This produces a comparison view of distinct visual directions to accelerate design decisions.

Can I generate UI variants for both Svelte and React projects?

Yes, UI variant generation is framework-aware and supports Svelte, React/Next, Vue/Nuxt, and HTML projects. It detects your project dependencies to infer the correct file extension and component scope automatically.

What is a design tokens file and how is it created from a chosen variant?

A design tokens file is a markdown document extracting the core style attributes from a selected UI variant. It is generated when you finalize your winning variant, extracting its visual properties into a reusable style system definition.

How do I finalize a winning design variant from a comparison view?

To finalize a winning design variant, you select your preferred style from the generated comparison page. The system copies the chosen variant to your target path, writes the design-tokens.md file, and cleans up the temporary variant directories.

What design styles can I use for generating component variants?

You can specify multiple design styles for component variant generation, such as brutalism, cafe, cosmic, luxury, and editorial. The system reads a style catalog to apply these distinct visual themes across your generated variants.

Do I need to manually clean up temporary UI variant files after selecting a design?

No, you do not need to manually clean up temporary UI variant files. The system automatically removes the temporary variant directories from your project after copying the winning variant to the target path and generating the design tokens file.