multi-brand-design-system

Design shared design systems with layered tokens and brand overrides for multi-product UI reskinning.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/tlennon-ie/product-building-agents --skill multi-brand-design-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-brand-design-system
Source: https://github.com/tlennon-ie/product-building-agents/tree/main/.claude/skills/multi-brand-design-system
Command: npx skills add https://github.com/tlennon-ie/product-building-agents --skill multi-brand-design-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of building and maintaining separate design systems for sibling products that must share infrastructure while still feeling distinct in brand identity.

Core Features & Use Cases

  • One system, brand-skinnable: Re-skin the entire UI by switching a single root attribute so components never contain brand conditionals.
  • Token layering architecture: Use primitive (shared), brand (per-product overrides), and semantic (component contract) tokens to keep customization controlled and scalable.
  • Glassmorphic, accessible styling: Standardize dark glass patterns with consistent focus states, contrast expectations, reduced-motion behavior, and fallbacks for performance.

Quick Start

Configure primitive tokens globally, define per-brand overrides at the root via data-brand values, and wire components to consume only semantic tokens so the UI re-skins without component changes.

Frequently Asked Questions about multi-brand-design-system

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

FAQPage Schema
How do I reskin multiple SaaS apps with a shared design system without duplicating components?

Layered token architecture separates primitive, brand, and semantic tokens to reskin multiple apps with a shared design system. Components consume only semantic tokens while brand overrides apply via root attributes, preventing component duplication across sibling SaaS frontends.

What is the best way to structure design tokens for sibling products requiring distinct brand identities?

Structure design tokens by separating primitive, brand, and semantic layers. Primitive tokens hold shared values, brand tokens hold per-product overrides, and semantic tokens act as the component contract, keeping customization controlled and scalable for distinct brand identities.

How do I apply glassmorphic styling to a multi-brand UI while maintaining accessibility?

Standardize dark glass patterns with consistent focus states, contrast-safe defaults, reduced-motion behavior, and performance fallbacks. Applying these glassmorphic styling constraints within the shared design system maintains accessibility across a multi-brand UI.

Can I switch brand identities in a multi-brand UI without writing component conditionals?

You can switch brand identities without component conditionals by defining per-brand overrides at the root via data-brand values. Because components wire exclusively to semantic tokens, switching a single root attribute reskins the multi-brand UI instantly.

Does a shared multi-brand design system support reduced-motion and contrast-safe defaults?

A shared multi-brand design system supports reduced-motion and contrast-safe defaults. The token architecture standardizes these accessibility rules globally, ensuring sibling products meet contrast expectations and motion personality requirements without per-component adjustments.