Platforms overview
Prism powers a family of product operating systems. They share every component and token, yet each feels like its own product because of a signature — a single attribute that re-points the accent roles to a canonical domain hue, swaps the hero gradient and the first chart series, and recommends a density.
<html data-signature="health" data-density="compact">
That is the whole mechanism. There is no per-product fork, no parallel component set. A button in HealthOS and a button in CommerceOS are the same button, skinned by the cascade.
The family
| Product | Signature | Recommended density | Character |
|---|---|---|---|
| CommerceOS | commerce | comfortable | Operational retail and inventory |
| CampusOS | campus | relaxed | Admissions and student-facing |
| FinanceOS | finance | compact | Dense, numeric, trust-forward |
| HealthOS | health | compact | Clinical, calm, information-dense |
| HospitalityOS | hospitality | comfortable | Warm, guest-facing, on-property |
| MediaOS | media | comfortable (cinema on TV) | Cinematic, ten-foot capable |
Designing for a platform
Always work in the target signature, not the default cobalt. Emphasis, contrast and the feel of a screen change with the accent hue, so a layout that looks balanced in cobalt can feel off in amber or green. Set the signature on your canvas first, then compose.
The pages that follow describe each product's character and the kits it leans on. The reference compositions live in the design system's template set.