white-label-systems

Apply per-tenant CSS custom properties for white-label branding without code changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/andersoncollab/design-agent --skill white-label-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: white-label-systems
Source: https://github.com/andersoncollab/design-agent/tree/main/skills/white-label-systems
Command: npx skills add https://github.com/andersoncollab/design-agent --skill white-label-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

White-labeling becomes unmanageable when each new client requires code changes for colors, logos, and typography, slowing launches and increasing maintenance risk.

Core Features & Use Cases

  • Multi-tenant theme architecture: Separates an immutable base design system from a tenant-specific brand layer using CSS custom properties.
  • Dynamic tenant theme loading: Fetches and validates tenant theme configs at runtime, applies tokens to :root/tenant attributes, and caches themes to reduce repeated API calls.
  • Component-wide variable theming: Ensures every UI component consumes tokens via CSS variables so branding updates require zero component rewrites.

Quick Start

Use the white-label-systems skill to design a single codebase theming approach by defining a tenant theme schema, implementing runtime theme loading with validation, and applying CSS variables so the same components render each tenant’s brand.

Frequently Asked Questions about white-label-systems

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

FAQPage Schema
How do I implement multi-tenant white-label theming without changing component code?

Multi-tenant white-label theming is achieved by applying per-tenant CSS custom properties for colors and typography. Components consume these CSS variables directly, ensuring branding updates require zero rewrites to the underlying UI component code.

What is the best way to dynamically load and validate tenant theme configurations at runtime?

Dynamic theme loading involves fetching tenant theme configurations at runtime and validating them before application. The system applies validated tokens to the root or tenant attributes and caches themes to reduce repeated API calls during sessions.

Does multi-tenant theming support dark mode preferences for individual clients?

Yes, tenant-specific dark mode is supported within multi-tenant theming. Per-tenant configurations can define distinct dark mode preferences, allowing individual clients to control their own dark mode styling through CSS custom properties.

Can I use CSS custom properties to swap logos and brand assets for SaaS reseller scenarios?

CSS custom properties can drive logo swapping and manage brand assets for SaaS reseller scenarios. The theming architecture separates the immutable base design from the tenant-specific brand layer, handling asset URLs dynamically.

How do I handle graceful fallback behavior when a tenant theme fails to load?

Graceful fallback behavior ensures components render with default base design tokens if a tenant theme fails to load. The architecture separates the immutable base from the tenant layer, maintaining UI stability when runtime fetches or validations fail.