Superfamily
A matched set of serif, sans, mono, or other families built from the same underlying letter shapes, ready to work as one type system.
See it
What it is
A superfamily is a coordinated set of type families across categories, usually serif and sans, sometimes with slab, condensed, or monospaced relatives. They share proportions, construction, and voice while changing enough to do different jobs. Charles Bigelow and Kris Holmes built the first proper one with Lucida in 1985; IBM Plex Sans, Serif, and Mono, drawn by Mike Abbink with Bold Monday, are the clean modern example: three textures built from one design system.
Reach for a superfamily when a product needs contrast without the risk of an awkward font pairing. Use the serif for editorial or display moments, the sans for interface text, and the mono for code or data. Shared skeletons make the handoff feel related even when the category changes.
The gotcha is that 'superfamily' is a design relationship, not one CSS font-family value. Each branch has its own files, family name, weights, metrics, and possibly license. Matching DNA also does not guarantee identical line breaks, so test swaps instead of assuming the serif and sans occupy the same width.
Ask AI for it
Build this type system with the IBM Plex superfamily from Google Fonts. Use IBM Plex Serif at 600 for editorial headings, IBM Plex Sans at 400 and 500 for body and interface text, and IBM Plex Mono at 400 for code and tabular data. Declare each as a separate CSS font-family with appropriate generic fallbacks, load only those four weights, and map them to design tokens named '--font-display', '--font-body', and '--font-code'. Show a specimen where all three set the same words at the same font-size, since the Plex branches already share cap height and x-height, so their common skeleton is visible.