LWCArchitect (Hardest)design-systemreusabilityslds
Design reusable LWC design system for enterprise org
Real World Scenario
Twelve teams built inconsistent buttons, modals, and form layouts across 80 LWCs causing brand fragmentation.
Expected Answer
• Publish internal component library: c-common-button, c-common-modal with SLDS tokens
• Document props slots and events in Storybook or LWC local dev server
• Semantic versioning library components breaking @api changes
• Design tokens for color spacing typography aligned to brand
• Lint rules preventing raw HTML where base component exists
• CoE review for new base components before team custom builds
• Package library as unlocked or namespaced managed package
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Publish internal component library: c-common-button, c-common-modal with SLDS tokens. Document props slots and events in Storybook or LWC local dev server. Pick based on your integration pattern and team capability. Design system ROI appears at 50+ components—invest early if program scale warrants. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Design system ROI appears at 50+ components—invest early if program scale warrants.