frontend-design

Translate UI design goals into token-driven frontend design systems.

2.7k|627|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/jjyaoao/HelloAgents --skill frontend-design-jjyaoao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-design
Source: https://github.com/jjyaoao/HelloAgents/tree/main/skills/frontend-design
Command: npx skills add https://github.com/jjyaoao/HelloAgents --skill frontend-design-jjyaoao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Front-end teams often struggle to translate vague design requests into consistent, accessible, and maintainable UI code across projects.

Core Features & Use Cases

  • Tokens-first design drives visuals from semantic tokens, ensuring consistent typography, spacing, color, and elevation.
  • Production-ready code samples including tokens.css, components.css, utilities.css, and TypeScript implementations to accelerate delivery.
  • Comprehensive component coverage with stateful, accessible primitives (default, hover, focus, active, disabled, loading, empty, error) suitable for dashboards, landing pages, admin panels, and design systems.
  • Real-world scenarios: build reusable UI libraries, design systems, and UI components for React, Vue, Svelte, and Next.js projects.

Quick Start

Provide a starting point by generating design tokens, components, and templates to bootstrap a production-ready frontend design system.

Frequently Asked Questions about frontend-design

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

FAQPage Schema
How do I build a production-ready frontend design system from vague UI ideas?

A tokens-first design system drives visuals from semantic tokens, ensuring consistent typography, spacing, color, and elevation across your project. It provides TypeScript implementations and comprehensive component coverage for maintainable architecture.

How do I generate accessible UI components with full state coverage for a dashboard?

You can generate accessible UI components for dashboards by using primitives that cover default, hover, focus, active, disabled, loading, empty, and error states. This ensures comprehensive stateful behavior for admin panels and component libraries.

Does this tokens-first design approach work with TypeScript and Tailwind-ready templates?

Yes, this approach provides TypeScript typings and Tailwind-ready templates alongside tokens.css, components.css, and utilities.css outputs. It supports React, Vue, Svelte, and Next.js projects for building reusable UI libraries.

What is the best way to structure design tokens for a scalable component library?

The best way to structure design tokens for a scalable component library is using a tokens-first approach that defines semantic token layers. This satisfies design-token definitions and enables token-driven styling across all UI components.

Can I use this frontend design system for React, Vue, Svelte, and Next.js projects?

Yes, you can use this frontend design system for React, Vue, Svelte, and Next.js projects. It provides TypeScript implementations and comprehensive component coverage suitable for building reusable UI libraries and design systems across these frameworks.

Why do frontend teams struggle to translate vague design requests into consistent UI code?

Frontend teams struggle with vague design requests when lacking a tokens-first design system. Without semantic tokens driving typography, spacing, color, and elevation, maintaining consistent and accessible UI code across projects becomes difficult.