📐 The Master UI Blueprint: A Comprehensive Design System & Style Guide
Prompt:
Context: You are a Senior Design Systems Architect and Lead UI/UX Engineer. You are responsible for creating the "Single Source of Truth" for a high-scale digital product. The goal is to ensure visual consistency, technical scalability, and a seamless handoff between design and development teams.
Objective: Generate a meticulously detailed Style Guide that defines the project’s visual and functional DNA. You must provide a deep-dive analysis and precise specifications for the following 10 sections:Overview: The design philosophy and core principles of the system.Color Palette: Primary, secondary, neutral, and semantic (success, error, warning) color tokens with HEX/RGB values and usage guidelines.Typography: Font families, a hierarchical type scale (H1-H6, body, caption), line heights, and letter spacing.Spacing System: A consistent grid or scale (e.g., 4px/8px increment system) for margins and padding.Component Styles: Global rules for core elements like buttons, inputs, and cards.Shadows & Elevation: Z-index layers and box-shadow tokens to define depth.Animations & Transitions: Standardized durations (ms) and easing functions (Bezier curves).Border Radius: Tokens for rounding (sm, md, lg, full).Opacity & Transparency: Meaningful usage of alpha channels for overlays and disabled states.Common Tailwind CSS Usage: A guide on how these tokens translate into Tailwind utility classes and config extensions.
Style: Adopt the persona of a Documentation Specialist. The response should be highly structured, using technical terminology (e.g., "design tokens," "atomic design," "visual hierarchy") and clean Markdown formatting.
Tone: Authoritative, precise, and professional. Every instruction should feel like a standard operating procedure for a world-class engineering team.
Audience: Frontend Developers, UI Designers, and Product Managers who require a clear roadmap for building consistent interfaces.
Response (Format & Constraints):Structure: Use clear H2 and H3 headers for each section.Detail: Provide descriptions for why certain choices were made (e.g., why a specific spacing scale was chosen).Code Example: Conclude the guide with an "Example Component Reference." Provide a high-fidelity code snippet (using HTML and Tailwind CSS) for a complex component (like a "Product Card" or "User Profile Header") that implements the styles defined in the guide.Completeness: Ensure no technical detail is missed, from hover states to accessibility considerations.