phia-design-system

Document PhiaUI design-system tokens for typography, color, spacing, and theming.

31|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/charlenopires/PhiaUI --skill phia-design-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phia-design-system
Source: https://github.com/charlenopires/PhiaUI/tree/main
Command: npx skills add https://github.com/charlenopires/PhiaUI --skill phia-design-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams need a single source of truth for visual language to maintain consistency across PhiaUI's 829 components and multiple themes, reducing drift and onboarding friction.

Core Features & Use Cases

  • Typography tokens, color tokens, spacing scales, radii, shadows, icons, layout, animation, and accessibility guidelines form a cohesive system.
  • Accessibility and dark mode baked-in, with responsive tokens for dashboards, docs, and marketing pages.
  • Use cases include branding a SaaS admin panel, marketing landing pages, and developer UI components that ship as a design system.

Quick Start

Review the design system assets and apply the tokens to a new PhiaUI component following the guidelines described in this skill.

Frequently Asked Questions about phia-design-system

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

FAQPage Schema
How do I define design tokens for a UI component library with dark mode and accessibility?

Define semantic-token-based theming rules for typography, color, spacing, and shadows to ensure accessibility and dark mode. This approach provides a single source of truth for visual language, maintaining consistency across hundreds of components without external libraries.

What is a semantic token-based theming approach for software engineering?

Semantic token-based theming uses named tokens for UI elements like typography, color, and spacing instead of hard-coded values. This system ensures responsive behavior, dark mode support, and accessibility guidelines are baked-in, reducing visual drift across multiple themes.

How do I create a Tailwind v4 design system for SaaS dashboards and marketing pages?

Apply documented design tokens for layout, animation, and spacing to build SaaS dashboards and marketing pages using Tailwind v4. This method enforces modularity constraints and zero external libraries, providing a cohesive visual system for admin panels and developer components.

Can I use this design system scope for admin panels without external dependencies?

Yes, you can brand a SaaS admin panel using this design system because it enforces zero external libraries. It specifies modularity constraints and semantic tokens for icons and layout, guiding future component design while maintaining accessibility and responsive behavior.

What's the best way to maintain design consistency across hundreds of UI components?

Establish a single source of truth using design tokens for typography, color, radii, and shadows to maintain consistency across multiple themes. This reduces onboarding friction and visual drift by enforcing strict accessibility and dark mode guidelines across all components.

When do I need a formal design system with predefined spacing and shadow tokens?

You need a formal design system with predefined tokens when scaling a UI library to hundreds of components. It ensures cohesive accessibility, dark mode, and responsive behavior across varied use cases like marketing pages and admin panels, preventing visual drift.