Compose styles
Rather than blending styles toward a middle, this gives them roles. The first one carries the structure, the next comes in as the accent, and anything after that shows up in a single detail. Where they fight each other, it says so before you start.
How to divide the work
- Composition
- Follow Ant Design: Set table and form columns first; show relationships through alignment rather than extra space
- Type
- Set in Ant Design's manner (Keep body text compact and separate labels, values and help text through weight and color), and let GitHub Primer's lettering (Use one plain sans for body and labels; build hierarchy through weight and color) appear only where you want the eye to catch.
- Material
- Ground in Ant Design's material (Start with white, fine borders and a blue primary action; hold every state color to one meaning); bring in exactly one thing from GitHub Primer (Start from neutrals; reserve blue for links and semantic colors for success, warning and danger).
- Colour
- Build on #FFFFFF, #1677FF, #1F1F1F and admit one accent from #F6F8FA, #0969DA, #24292F.
Where they fight
- Ant Design and GitHub Primer both belong to Platform Screen Languages, so the difference is small. Push the roles further apart than feels comfortable.
Caution
- Ant Design A component catalog dropped onto a page can look orderly while leaving the actual workflow undesigned.
- GitHub Primer Adding borders and tiny controls to look like GitHub only creates a cramped admin screen when the work has no clear priority.
Image prompt
Produce four original images that take their structure from Ant Design (style, 2015–) and their accent from GitHub Primer (style, 2017–). ## What to make Make the kind of thing Ant Design exists for: enterprise admin screens with many tables, forms, permissions and states, or standardizing component behavior and exceptions in international products. Choose one subject and hold it across all four. ## Structure comes from Ant Design - Dense tables set in small type and fine rules - Blue primary actions with explicit semantic colors - Consistent forms, pagination, trees and tables - Readability achieved through alignment and repetition, not generous space Composition: Set table and form columns first; show relationships through alignment rather than extra space. Type and lettering: Keep body text compact and separate labels, values and help text through weight and color. ## Accent comes from GitHub Primer, used sparingly - Neutral surfaces with blue links and restrained status colors - Octicons paired with short action labels - Thin borders separating lists, tabs and sidebars - Consistent steps of type and spacing even at high density Let one material quality come from it: Start from neutrals; reserve blue for links and semantic colors for success, warning and danger. ## Colour and feeling Build the ground on #FFFFFF, carry the structure in #1677FF and #1F1F1F, and let a single accent come from #0969DA. These are read off real works, so a direction rather than a fixed palette. Feeling to carry: technique, trust, calm. ## Where they fight - Ant Design and GitHub Primer both belong to Platform Screen Languages, so the difference is small. Push the roles further apart than feels comfortable. ## What goes wrong - Ant Design: A component catalog dropped onto a page can look orderly while leaving the actual workflow undesigned. - GitHub Primer: Adding borders and tiny controls to look like GitHub only creates a cramped admin screen when the work has no clear priority. ## Across the four Keep the roles fixed in all four. Vary the framing, the scale and the arrangement so the set shows what this pairing can do rather than four versions of one picture. ## Constraints - Do not imitate, reference or name any specific artist, studio, brand, character or copyrighted work. - Do not reproduce the composition of an existing work. - Produce original compositions in the general period languages described above.
Related entries
- Ant Design 2015– / Style / Platform Screen Languages
A design system that keeps enterprise web applications at low entropy through reusable components and page patterns. Its values — Natural, Certain, Meaningful and Growing — systematize tables, forms, hierarchy and state without reducing information density.
- GitHub Primer 2017– / Style / Platform Screen Languages
GitHub's design system for turning dense development workflows into shared rules for color, type, icons, spacing and components. It favors flow over decoration, keeping many states and actions in a small area without giving up accessibility or responsive behavior.
Share this composition:https://indexstyle.org/compose?ids=ant-design+github-primer