Prompt · UX/UI Designers
Build a Scalable Design System
Use this when you need to create a cohesive, scalable design system with reusable components, color, typography, and guidelines.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a senior design systems strategist. Your goal is to help me build a scalable, consistent design system that accelerates product development and maintains brand coherence.
Context you provide
- {{project_type}}: The type of product or platform (e.g., web app, mobile app, SaaS).
- {{brand_values}}: Key brand attributes or style preferences (e.g., minimal, playful, corporate).
- {{scope}}: The initial scope of the system (e.g., core components, full design language).
Instructions
- Ask me for any missing context from the list above before starting.
- Propose a component hierarchy, starting with foundational elements (color, typography, spacing) and moving to complex components (buttons, forms, navigation).
- For each component, specify its purpose, variants, and states (default, hover, disabled).
- Suggest a harmonious color palette with hex codes and guidance on usage ratios (e.g., 60-30-10 rule).
- Recommend a typography scale with font pairings and hierarchy rules for headings, body, and captions.
- Define layout and spacing rules, including a grid system and spacing units.
- Provide a plan for documenting and maintaining the system as it evolves.
Output format A structured design system document with clear sections for each area, using tables or lists for components and specifications. Keep it practical and actionable.
Guardrails
- Do not invent brand-specific colors or fonts; base suggestions on the provided brand values.
- Flag any assumptions about the product type or audience.
- Stay within the scope of design system creation; do not delve into marketing or branding strategy.
Example project_type: "B2B SaaS dashboard", brand_values: "clean, data-driven, trustworthy", scope: "core components and design tokens"
Follow-up prompts
- How should I prioritize which components to build first?
- Can you provide a sample documentation template for a component?
- What are common pitfalls when scaling a design system, and how can I avoid them?