ui-design

Align UI design artifacts into a master Design System, Visual Specs, Interaction Spec, and Vaadin Mapping.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/js-rom/Luis --skill ui-design-js-rom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-design
Source: https://github.com/js-rom/Luis/tree/main/.agents/skills/ui-design
Command: npx skills add https://github.com/js-rom/Luis --skill ui-design-js-rom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns UI design artifacts into a cohesive master Design System, per-state Visual Specs, an Interaction Spec, and a Vaadin Mapping, to ensure consistent implementation across teams.

Core Features & Use Cases

  • Master Design System: project-level tokens, typography, spacing, and accessibility constraints that drive all views.
  • State Visual Specs: per-use-case visuals for significant UI states with assets and token usage.
  • Interaction Spec: YAML-driven description of transitions, validations, and traceability to SSDs and operation contracts.
  • Vaadin Mapping: mapping document that aligns design-system decisions with Vaadin 25 Flow implementation.
  • Pair-programming workflow: ensures cross-disciplinary collaboration between design and frontend teams.

This skill integrates design-system governance with concrete state and behavior specs to streamline handoffs and reduce iteration cycles.

Quick Start

Begin by drafting the Design System and the State Visual Specs for the target use case, then create the Interaction Spec and Vaadin Mapping for review.

Frequently Asked Questions about ui-design

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

FAQPage Schema
How do I align UI design artifacts into a cohesive design system for Vaadin?

To align UI design artifacts for Vaadin, you consolidate project-level tokens, typography, and spacing into a master Design System, then generate per-state visual specs and an interaction spec to ensure consistent implementation across teams.

What is a state visual spec and when do I need it for UI design?

A state visual spec defines per-use-case visuals for significant UI states, including assets and token usage. You need it during the elaboration phase when a use case involves multiple UI states to ensure traceability from visuals to behavior.

How do I create an interaction spec that traces UI transitions to operation contracts?

You create an interaction spec using YAML to describe transitions, validations, and traceability to SSDs and operation contracts. This aligns state visual specs with behavior to enable deterministic handoffs to frontend teams.

Does this UI design workflow support pair-programming with frontend developers?

Yes, the workflow supports pair-programming by ensuring cross-disciplinary collaboration between design and frontend teams. It integrates design-system governance with concrete state and behavior specs to streamline handoffs.

Can I use this to map a design system directly to Vaadin 25 Flow components?

Yes, you can map design-system decisions to Vaadin 25 Flow implementation. The skill generates a Vaadin mapping document that aligns the master design system, state visual specs, and interaction spec with Vaadin 25 components.

What format do I need for the master design system to start generating visual specs?

You need the master design system formatted as YAML. This file defines project-level tokens, typography, spacing, and accessibility constraints that drive all views and subsequent state visual specs.