Skip to main content

Prompt: Design an Enterprise Design System

Prompt​

Design a design system platform for multiple product teams, brands, themes, accessibility requirements, and AI-generated UI surfaces.

Clarifying questions​

  • Which product surfaces consume the system?
  • How many brands and themes exist?
  • Which components are high-risk for accessibility?
  • What release cadence do product teams need?
  • Does GenUI need an approved component subset?

Model answer outline​

  • Token layers: base, semantic, component, state, brand.
  • Accessible primitives before product-specific components.
  • Package boundaries for tokens, foundations, primitives, components, recipes, and GenUI registry.
  • Storybook/docs with states, recipes, and anti-patterns.
  • Release governance with migration and deprecation policy.
  • Accessibility contracts as API compatibility.

Architecture diagram​

Weak answers​

  • Starts with visual components before tokens and primitives.
  • Accessibility is tested only after consumers adopt.
  • Breaking changes ship without migration guidance.
  • Product teams fork components for missing behavior.
  • GenUI can use all components without schema review.

Scoring​

Strong answer: token taxonomy, component contracts, package graph, accessibility verification, adoption model, release policy, and GenUI-safe subset.

For a complete calibrated answer, read worked-answer-enterprise-design-system and compare it with capstones/capstone-solution-pack-enterprise-design-system.