Working Design skill
Govern a multibrand design system
Govern a multibrand design system through shared foundations, semantic variation, accessibility, contribution, release, exceptions, migration, and consumer evidence.
When to use
- Use for product families, acquisitions, white labels, regions, or themes.
- Do not encode brand variation by forking inaccessible or unmaintained components.
Procedure
- Inventory brands, products, consumers, platforms, obligations, owners, and current forks.
- Separate shared behavior and accessibility from semantic brand expression.
- Define token layers, component contracts, content rules, assets, themes, and fallback.
- Establish contribution, review, decision, exception, expiry, and dispute governance.
- Test brand combinations, contrast, motion, typography, localization, density, and assistive use.
- Version releases, communicate change, migrate consumers, and measure adoption plus task health.
- Retire forks only after parity and rollback evidence.
Failure plan
- Keep a governed exception when forced convergence would harm users or legal obligations.
Worked example
Three brands share accessible form behavior while color, type, tone, and illustration vary semantically.
--- name: govern-a-multibrand-design-system category: design description: Govern a multibrand design system through shared foundations, semantic variation, accessibility, contribution, release, exceptions, migration, and consumer evidence. Use when several brands share product infrastructure. --- # govern-a-multibrand-design-system ## When to use - Use for product families, acquisitions, white labels, regions, or themes. - Do not encode brand variation by forking inaccessible or unmaintained components. ## Procedure 1. Inventory brands, products, consumers, platforms, obligations, owners, and current forks. 2. Separate shared behavior and accessibility from semantic brand expression. 3. Define token layers, component contracts, content rules, assets, themes, and fallback. 4. Establish contribution, review, decision, exception, expiry, and dispute governance. 5. Test brand combinations, contrast, motion, typography, localization, density, and assistive use. 6. Version releases, communicate change, migrate consumers, and measure adoption plus task health. 7. Retire forks only after parity and rollback evidence. ## Failure plan - Keep a governed exception when forced convergence would harm users or legal obligations. ## Worked example Three brands share accessible form behavior while color, type, tone, and illustration vary semantically. ## Done - A multibrand governance report records consumers, foundations, token layers, components, accessibility, decisions, exceptions, releases, and migration - Brand, contrast, motion, localization, platform, consumer, exception-expiry, rollback, and task-health checks verify operation