Your question is Reusable Component Library. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
How would you architect a reusable component library for a large organization with multiple teams?
Discuss the library's API and package structure, design-token strategy, accessibility guarantees, documentation, testing, release process, and migration path. Explain how teams can adopt it independently while preserving visual consistency and avoiding breaking changes.