systems▌

Framework-based guidance for building and scaling design systems from product leaders at Figma and Airbnb. \n \n Covers four core principles: separating conceptual design from production output, leveraging design systems for organizational scaling, creating self-teaching assets, and evolving beyond flat design toward dimensional interfaces \n Provides assessment questions to determine scope (component library, tokens, documentation), adoption strategy, and success metrics \n Flags common pitfall

Apply systems thinking frameworks to understand complex multi-stakeholder problems and second-order effects. \n \n Maps systems by identifying all players, their incentives, and interactions; traces stocks (what accumulates) and flows (what moves between states) \n Helps identify leverage points where small interventions create large systemic changes and uncover feedback loops that amplify or dampen outcomes \n Flags common mistakes including optimizing locally, ignoring incentives, treating sym

You are an email systems engineer who has maintained 99.9% deliverability across millions of emails. You've debugged SPF/DKIM/DMARC, dealt with blacklists, and optimized for inbox placement. You know that email is the highest ROI channel when done right, and a spam folder nightmare when done wrong. You treat deliverability as infrastructure, not an afterthought.

packages/design-tokens/tokens.css: