ux-ui-designer-full

Generate design-system scaffolds with tokens, components, and documentation for engineering handoff.

2|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/adnanmueller/am-dev-plugins --skill ux-ui-designer-full
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-ui-designer-full
Source: https://github.com/adnanmueller/am-dev-plugins/tree/main/plugins/development-pipeline/agents/02a-ux-ui-full
Command: npx skills add https://github.com/adnanmueller/am-dev-plugins --skill ux-ui-designer-full

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams often struggle with maintaining a single source of truth for UI standards, leading to inconsistent experiences across features and products.

Core Features & Use Cases

  • Create a production-grade design system with tokens, components, patterns, and documentation that scales with product growth.
  • Generate feature-specific design artifacts and handoffs to design and frontend teams.
  • Maintain accessibility guidelines and a consistent visual language across all interfaces.

Quick Start

Start by generating a complete design-system scaffold with tokens, components, and feature documentation for engineering handoff.

Frequently Asked Questions about ux-ui-designer-full

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

FAQPage Schema
How do I create a production-grade design system for engineering handoff?▼

Create a production-grade design system by generating a complete scaffold of design tokens, components, and patterns. This establishes a single source of truth for UI standards and outputs feature-specific artifacts ready for frontend engineering handoff.

Why do we need a single source of truth for design tokens and components?▼

A single source of truth for design tokens and components prevents inconsistent UI experiences across product features. Design-system automation unifies the UI language and enforces accessibility guidelines across all interfaces for cross-functional teams.

Can I generate feature-specific design artifacts for frontend engineers?▼

Yes, you can generate feature-specific design artifacts and handoffs directly from the design system. This provides frontend engineers with end-to-end specifications, design tokens, and component patterns needed for implementation.

What is the best way to document UI patterns and accessibility guidelines at scale?▼

Documenting UI patterns and accessibility guidelines at scale requires automated design documentation that enforces an end-to-end specification. This maintains a consistent visual language across large-scale projects and cross-functional collaboration.

Does design-system automation work for large-scale projects requiring cross-functional collaboration?▼

Yes, design-system automation is specifically applicable to large-scale projects requiring scalable design documentation. It facilitates cross-functional collaboration between designers and frontend engineers by unifying the UI language across products.

How do I start building a design system scaffold with tokens and components?▼

Start building a design system scaffold by generating the foundational structure of design tokens, components, and feature documentation. This quick start approach creates the baseline needed for engineering handoff and scalable product growth.