white-label-config

Generate type-safe white-label configuration with layered files, environment variables, and defaults.

8|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/SufficientDaikon/omniskill --skill white-label-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: white-label-config
Source: https://github.com/SufficientDaikon/omniskill/tree/main/skills/white-label-config
Command: npx skills add https://github.com/SufficientDaikon/omniskill --skill white-label-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables the transformation of a single application codebase into multiple, distinct white-labeled products with unique branding, themes, and feature sets, all managed through a type-safe configuration system.

Core Features & Use Cases

  • Type-Safe Configuration: Utilizes defineConfig for robust TypeScript autocompletion and validation.
  • Layered Configuration: Supports configuration through files, environment variables, and runtime defaults with a defined priority.
  • Feature Toggling: Manages feature availability via flags, controlling UI elements and API endpoints.
  • Use Case: A SaaS provider can use this skill to offer a base product that can be easily rebranded and customized by their clients, each with their own logos, color schemes, and enabled features.

Quick Start

Use the white-label-config skill to create a new app.config.ts file with default branding and feature flags.

Frequently Asked Questions about white-label-config

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

FAQPage Schema
How do I set up type-safe configuration for white-labeling a TypeScript application?

Type-safe white-label configuration is generated using a `defineConfig` utility, providing TypeScript autocompletion and validation for branding, theming, authentication, internationalization, and feature flags in an `app.config.ts` file.

What is the best way to manage feature flags for self-hosted instances?

Feature flags for self-hosted instances are managed through a layered configuration system, allowing dynamic control over UI elements and API endpoint gating based on settings derived from files, environment variables, and runtime defaults.

How does configuration priority layering work with environment variables and runtime defaults?

Configuration priority layering resolves settings by checking runtime defaults, environment variables, and configuration files sequentially, ensuring the highest priority source overrides the others for accurate white-label deployment.

Can I dynamically toggle UI components and API endpoints based on configuration?

You can dynamically toggle UI components and gate API endpoints by utilizing the integrated feature flags, which read the current white-label configuration to determine availability at runtime.

Do I need external dependencies to handle internationalization and branding for my SaaS?

No external dependencies are required to handle internationalization and branding, as the configuration system natively manages these aspects alongside authentication and feature flags within your TypeScript codebase.

What are the limitations of using file-based configuration for multi-tenant white-labeling?

File-based configuration for multi-tenant white-labeling requires managing separate configuration files per tenant, which can become complex to maintain if dynamic runtime updates are needed without restarting the application.