Scalable React Component Architecture with Design System
Defines component structure, design tokens, and conventions for a scalable React/Next.js design system.
Build a reusable, consistent component architecture that accelerates frontend development and ensures visual uniformity across the entire application.
At a glance
Access
Free prompt
Open to copy without upgrading.
Prompt objective
Build a reusable, consistent component architecture that accelerates frontend development and ensures visual uniformity across the entire application.
Real use case
Rio de Janeiro fintech PagaRapido has 12 frontend developers working across 4 squads. Each squad built their own buttons, modals, and forms, resulting in 47 duplicate component variations and visual inconsistencies that confuse users.
Customize these fields first
Replace the placeholders with your own context before you run the prompt. That usually improves the first output more than adding more instructions later.
Prompt
Design a complete design system architecture for [PROJECT NAME], a [TYPE: SaaS/e-commerce/marketplace] application built with React and [NEXT.JS/VITE/REMIX].\\\\\\\\n\\\\\\\\n**Context:**\\\\\\\\n- Team: [NUMBER] frontend developers in [NUMBER] squads\\\\\\\\n- Existing components: [NUMBER] (many duplicates)\\\\\\\\n- Current styling library: [TAILWIND/STYLED-COMPONENTS/CSS MODULES]\\\\\\\\n\\\\\\\\n**1) Design Token Structure:**\\\\\\\\n- Color palette (primary, secondary, neutral, semantic)\\\\\\\\n- Typography (font families, 8-size scale, line-heights)\\\\\\\\n- Spacing (4px scale: 4, 8, 12, 16, 24, 32, 48, 64)\\\\\\\\n- Borders, shadows, breakpoints\\\\\\\\n- Implementation with CSS variables + Tailwind config\\\\\\\\n\\\\\\\\n**2) Component Hierarchy:**\\\\\\\\n- Atoms: Button, Input, Badge, Avatar, Icon (variants and props)\\\\\\\\n- Molecules: FormField, SearchBar, Card, Toast, Dropdown\\\\\\\\n- Organisms: Header, Sidebar, DataTable, Modal, Form\\\\\\\\n- Templates: DashboardLayout, AuthLayout, LandingLayout\\\\\\\\n- For each level: TypeScript interface, variants, states, accessibility\\\\\\\\n\\\\\\\\n**3) Code Conventions:**\\\\\\\\n- Folder structure (feature-based vs. atomic)\\\\\\\\n- Naming conventions for props, files, exports\\\\\\\\n- Composition pattern (compound components vs. render props)\\\\\\\\n- Storybook: how to document each component\\\\\\\\n\\\\\\\\n**4) Migration Strategy:**\\\\\\\\n- Inventory of current components\\\\\\\\n- Prioritization (which to migrate first)\\\\\\\\n- Coexistence during transition\\\\\\\\n- Design system adoption metrics\\\\\\\\n\\\\\\\\nInclude TypeScript code examples for the 3 most critical components.
Open directly in an AI — the text is pre-filled:
How to use this prompt
- 1Replace the key placeholders first: PROJECT NAME, TYPE: SaaS/e-commerce/marketplace, NEXT.JS/VITE/REMIX, NUMBER.
- 2Replace any bracketed placeholders like [this] with your own context.
- 3Add extra background information when you want more tailored results.
- 4Combine multiple prompts in one conversation when you need a richer output.
- 5Save your best-performing prompts so they are easy to reuse later.
Next best step
Open the guide first, then branch only if you still need more.
A guide for technical builders choosing between prompts, coding workflows, and agent-based implementation.
If this prompt is close but not quite right, generate variants next. If the job is recurring, move into the course library after the guide.
Related prompts
View allNext.js Performance Optimization with Core Web Vitals
Diagnosis and action plan to improve LCP, FID, and CLS in Next.js applications.
Best for
Identify performance bottlenecks and implement optimizations that improve Core Web Vitals to achieve green status on PageSpeed Insights.
WCAG 2.1 AA Accessibility Implementation in React Applications
Complete guide to making a React application accessible following WCAG 2.1 Level AA guidelines.
Best for
Ensure the application meets WCAG 2.1 AA accessibility requirements, complying with Brazil's Accessibility Law and expanding the audience reached.
Complex state management with Zustand and React Query
State architecture that separates server state and client state using Zustand + TanStack Query.
Best for
Define a clear state management strategy that eliminates unnecessary re-renders, simplifies code, and improves developer experience.
Design system creation with Storybook, Tailwind, and visual tests
Complete Storybook setup with interactive documentation, visual tests, and CI/CD integration.
Best for
Establish a component development and documentation environment with Storybook that serves as the single source of truth for the team's design system.
Explore other prompt categories
Move sideways into adjacent libraries when the current category is not the full answer.
Free browsing stays open. Premium prompts unlock the reusable workflow layer.
Use the guides and role paths to validate the job first. Upgrade when you want the full prompt text, editable premium prompts, and the surrounding course paths in one place.
Free access
- Browse guides, role paths, and category pages.
- Preview prompts before you decide to upgrade.
- Find the right starting point without friction.
Membership access
- Unlock premium prompts and the full copy text.
- See more workflow paths and course connections.
- Keep the reusable templates in one place.
