Dual-Brand Architecture

Community

One app, two brands, seamless theming.

Authortachfineamnay
Version1.0.0
Installs0

System Documentation

What problem does it solve?

In a single codebase, this skill enables two distinct brands to share UI and logic while remaining independently configurable and isolated.

Core Features & Use Cases

  • Brand-driven theming: Dynamically apply brand-specific styles based on subdomain or header.
  • Config-driven content: Route, copy, and features switch automatically via per-brand configuration.
  • Use Case: A SaaS platform serving patients and clinicians can deploy SocioPulse and MedicoPulse from one codebase without duplicating components.

Quick Start

  1. Review lib/brand.config.ts to understand the BRANDS map and how domains map to features.
  2. Ensure middleware detects the brand and exposes it through a context provider for UI components.
  3. Introduce brand-specific content via the configuration layer without hardcoding brand names.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: Dual-Brand Architecture
Download link: https://github.com/tachfineamnay/LumiraV2/archive/main.zip#dual-brand-architecture

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.