Build Comprehensive Design System Documentation

Act as a design systems lead with experience building and scaling design systems at enterprise-level organizations. Create thorough design system documentation for [PRODUCT/COMPANY NAME], a [PRODUCT TYPE, e.g., B2B analytics platform, consumer health app, multi-brand retail system] built with [TECH STACK/FRAMEWORK, e.g., React + Tailwind CSS, SwiftUI, Flutter]. The documentation should cover the following sections: 1. **Design Principles (4-6 principles):** Define the core design philosophy that guides all component and pattern decisions. Each principle should have a name, a one-sentence definition, and a practical 'Do/Don't' example. 2. **Design Tokens:** Document the foundational tokens including: - Spacing scale (e.g., 4px base unit system) - Typography scale (font families, sizes, weights, line heights) - Color tokens (referencing semantic naming like `color-primary`, `color-error`, `color-surface`) - Border radius, shadows, and elevation levels - Breakpoints for responsive design 3. **Component Library (document 8-10 core components):** For each component (e.g., Button, Input Field, Modal, Card, Toast, Avatar, Badge, Tabs), provide: - Description and purpose - Variants (e.g., primary, secondary, destructive, ghost) - Props/properties table with type, default value, and description - States (default, hover, active, focused, disabled, loading) - Accessibility requirements (ARIA labels, keyboard navigation, screen reader behavior) - Usage guidelines with Do's and Don'ts 4. **Layout & Grid System:** Describe the grid structure, column counts, gutter widths, and container max-widths for [NUMBER OF BREAKPOINTS, e.g., 3-5] breakpoints. 5. **Iconography & Illustration Guidelines:** Define icon style (outlined, filled, duotone), sizing standards, and rules for when to use icons vs. text labels. 6. **Content & Voice Guidelines:** Provide tone-of-voice rules for UI copy, including standards for button labels, error messages, empty states, and tooltips. 7. **Contribution Guidelines:** Outline the process for proposing, reviewing, and adding new components to the design system, including naming conventions and versioning strategy. Format everything with clear headings, tables where appropriate, and code-ready token naming conventions.