🎨 Design Systems

The Senior Mindset: A good design system should make the “right” way to build a UI the “easiest” way. If a developer has to write custom CSS for a standard margin or color, your design system has a gap.

💎 1. Design Tokens (The Atomic Level)

Design tokens are the visual atoms of the system—agnostic variables that store values for colors, typography, spacing, and shadows.

The Power of Aliasing: Don’t just use color-blue-500. Use Semantic Tokens like action-primary-background. This allows you to change the entire brand’s look (or switch to Dark Mode) just by swapping the values of the semantic tokens.
Multi-Platform: Tokens should be stored in a format (like JSON) that can be transformed (using tools like Style Dictionary) into CSS variables, SCSS, Swift (iOS), or XML (Android).

📕 2. Storybook (The Development Environment)

Storybook is the industry standard for building UI components in isolation.

Component Documentation: It’s not just for seeing components; it’s for documenting their API (Props). Use “Args” to let designers play with component states without touching code.
The “Workbench” Effect: Building in Storybook forces you to handle edge cases (like extremely long text in a button) that you might miss when building inside a specific page layout.
Add-ons: Use the A11y add-on to catch accessibility issues and the Viewport add-on to test responsiveness instantly.

🏗️ 3. Component Architecture

A senior engineer organizes a design system following a clear hierarchy (often inspired by Atomic Design):

Atoms: Basic HTML elements (Buttons, Inputs, Labels).
Molecules: Groups of atoms functioning together (Search Bar = Input + Button).
Organisms: Complex UI sections (Header, Sidebar, Navigation).
Templates/Pages: High-level layouts.

The “Slot” Pattern: Instead of passing 20 props to a component, use Slots (or children in React) to allow consumers to inject their own content while keeping the layout consistent.

📜 4. Guidelines & Governance

A design system without guidelines is just a library. You need to define the “How” and “Why.”

Usage Guidelines: “Use a Primary Button for the main call to action. Never use more than one Primary Button per view.”
The Contribution Model: How does a developer suggest a new component?
- Sovereign Model: A dedicated team builds everything.
- Federated Model: Developers from different teams contribute back to the system (Best for scaling).
Versioning: Use Semantic Versioning (SemVer). Breaking changes in the Design System should be handled with extreme care to avoid breaking the entire company’s product.

🛠️ Senior Implementation Patterns

1. Headless UI Components

For maximum flexibility, use Headless Libraries (like Radix UI, Headless UI, or TanStack Table).

Strategy: These libraries handle the logic, state, and accessibility (ARIA), but provide zero styles. You then apply your Design Tokens/CSS on top. This prevents you from “fighting the framework” to match your brand’s unique look.

2. Layout Components

Avoid “Magic Numbers” in CSS.

Senior Move: Create components like <Stack>, <Grid>, and <Box> that only handle spacing. This ensures that every margin and padding in your app comes from your Design Tokens.

3. Visual Regression Testing

As mentioned in the testing section, use Chromatic or similar tools integrated with Storybook. Every time you change a Design Token, these tools will show you exactly how that change affects every component in the system.

💡 Seniority Note: The biggest challenge of a Design System is Adoption. If developers find it too rigid or poorly documented, they will go back to writing custom CSS. Spend 50% of your time on the code and 50% on internal marketing and documentation.

[[Frontend-Acessibilidade-WCAG]]
[[Frontend-Frameworks-Architecture]]
[[CSS-Methodologies-BEM-Tailwind]]