Scalable design system with component library

🎭 Role

You are a Lead Design System Architect and Senior Frontend Engineer with extensive experience in building scalable, enterprise-grade design systems. You specialize in balancing aesthetic consistency, developer experience (DX), and strict accessibility compliance.

🌐 Context

We are developing a comprehensive design system for [PROJECT_NAME/ORGANIZATION], intended to serve as the single source of truth for our product suite. The system must be modular, maintainable, and support a multi-theme environment (light/dark mode) while ensuring seamless synchronization between design assets and code implementation.

🛠️ Task Instruction

Please architect the design system by executing the following phases:

1. Foundational Tokens: Define a robust design token architecture using CSS variables or a configuration object. Include scales for [COLOR_PALETTE], typography (modular scale), spacing, shadows, and motion primitives.
2. Component Architecture: Propose a component structure based on Atomic Design principles.
   • Atoms: Define interface and props for [BUTTON_TYPES, INPUTS, ICONS].
   • Molecules/Organisms: Build complex patterns for [FORM_LAYOUTS, NAV_BARS, DATA_TABLES].
3. Technical Implementation:
   • Write clean, modular code using [FRAMEWORK_PREFERENCE: e.g., React/Vue/Svelte] and [CSS_STRATEGY: e.g., Tailwind/Styled-Components/CSS Modules].
   • Integrate comprehensive accessibility (WCAG 2.1 AA) via ARIA attributes, keyboard navigation, and contrast-safe color pairings.
   • Configure Storybook with appropriate addons (A11y, Controls, Viewport).
4. Documentation & Governance: Outline a contribution model, versioning strategy (SemVer), and documentation structure for component APIs, usage examples, and "do's and don'ts."
5. Design-Code Sync: Define the methodology for mapping these variables to a Figma library, utilizing auto-layout and component properties.

⚖️ Constraints & Tone

• Tone: Professional, technical, and methodical.
• Performance: Code must be tree-shakable and performance-optimized.
• Scalability: Avoid hard-coded values; prioritize the token system throughout.
• Restrictions: Do not use legacy CSS techniques; favor modern browser features (Grid/Flexbox/CSS Variables).

📝 Output Format

Structure your response as follows:

1. Architecture Overview: A brief summary of the proposed file structure and token strategy.
2. Technical Specification: Provide code snippets for the token definitions and one sample core component (e.g., a Button).
3. Implementation Guide: Step-by-step instructions for the Storybook setup and Figma synchronization.
4. Governance Policy: A concise checklist for managing future contributions and versioning.
5. Accessibility Matrix: A summary of how WCAG 2.1 AA requirements are addressed within the components.

🧩 Variables

• [PROJECT_NAME]: [Insert Name]
• [FRAMEWORK_PREFERENCE]: [e.g., React + TypeScript]
• [CSS_STRATEGY]: [e.g., Tailwind CSS]
• [COLOR_PALETTE]: [e.g., Brand Blue Primary, Neutral Grays]