Generate comprehensive responsive breakpoint specifications for multi-device UI design projects. This prompt creates detailed breakpoint strategies with layout adaptations, component behaviors, and implementation guidelines that ensure seamless user experiences across all screen sizes and devices.
This prompt is designed for UI/UX designers, front-end developers, and product teams creating responsive web applications or websites. Fill in the bracketed placeholders with your project-specific information, including target devices, user analytics data showing actual device usage, and content priorities. The prompt generates comprehensive breakpoint specifications that serve as a complete reference guide throughout the design and development process. Use this early in the design phase to establish a consistent responsive strategy across your entire project.
Modern responsive design offers multiple approaches to defining breakpoints, each with distinct advantages. Device-based breakpoints target specific device categories (mobile at 480px, tablet at 768px, desktop at 1024px) and provide predictable, industry-standard reference points that align with common frameworks. Content-based breakpoints focus on where your specific layout breaks or becomes suboptimal, creating a more customized approach that prioritizes design integrity over device categories. For most projects, a hybrid approach works best: start with industry-standard device breakpoints as a foundation, then add content-specific breakpoints where your layout requires additional adjustment. Always prioritize your actual user analytics data showing device usage patterns over theoretical device sizes.
The mobile-first approach designs for the smallest screen first and progressively enhances for larger screens, aligning with how most users access websites in 2025. This methodology forces content prioritization and ensures essential functionality works on constrained devices before adding enhancements. Start by designing a single-column mobile layout at 320-480px, then expand to tablet layouts around 768px, and finally desktop at 1024px and above. Write CSS media queries using min-width to progressively add styles as screens grow larger, resulting in cleaner, more maintainable code. Mobile-first design naturally improves performance since heavy assets and complex interactions load conditionally for larger screens rather than being hidden on mobile.
Beyond page-level breakpoints, modern responsive design requires component-specific breakpoints that allow UI elements to adapt independently. A navigation component might transform from horizontal tabs to a hamburger menu at 1024px, while a card grid might shift from four columns to two at 768px and single column at 480px. Document these component breakpoints separately from global layout breakpoints, as they often differ based on content density and functionality. Use CSS container queries where browser support allows, enabling components to respond to their container size rather than viewport width, creating truly modular responsive components that work in any layout context.
Responsive design specifications must be validated on actual devices, not just browser resize tools or emulators. Browser developer tools provide a starting point for testing breakpoints, but they cannot replicate real device rendering engines, touch interactions, or performance characteristics. Prioritize testing on the most common devices in your user analytics, ensuring coverage across iOS and Android for mobile, iPads and Android tablets, and various desktop screen sizes. Test both portrait and landscape orientations for mobile and tablet breakpoints. Use cloud-based device testing platforms to access a broad range of devices without maintaining a physical device lab, and conduct at least quarterly reviews of your breakpoint strategy as device landscapes evolve.
You are an expert UI/UX design system architect with extensive experience in creating scalable, accessible, and maintainable design systems and component libraries. Create a comprehensive design system and component library for [PROJECT/PRODUCT NAME] that serves [TARGET USERS/TEAM SIZE]. The design system should support [PLATFORM/TECHNOLOGY STACK] and align with [BRAND/DESIGN PHILOSOPHY]. ## Core Requirements: 1. **Design Principles & Foundation** - Define [NUMBER] core design principles that reflect [BRAND VALUES/PRODUCT GOALS] - Establish design tokens for colors, typography, spacing, and elevation - Create a cohesive visual language that ensures [SPECIFIC CONSISTENCY GOALS] 2. **Component Library Structure** - Design [SPECIFY COMPONENT TYPES: e.g., buttons, forms, navigation, modals, cards, data tables] - Include component variants, states (default, hover, active, disabled, error), and responsive behaviors - Ensure WCAG 2.2 AA compliance with proper ARIA labels, semantic HTML, and keyboard navigation - Provide [LIGHT/DARK/BOTH] theme support 3. **Documentation Requirements** - Component usage guidelines with do's and don'ts - Code snippets for [FRAMEWORK: React, Vue, Angular, Web Components, etc.] - Accessibility implementation notes and screen reader compatibility - Visual examples showing component applications in real contexts 4. **Technical Specifications** - Design tokens in [FORMAT: CSS variables, JSON, SASS, etc.] - Responsive breakpoints for [DEVICE TARGETS] - Grid system with [COLUMN COUNT] columns - Naming conventions following [BEM/ATOMIC/CUSTOM] methodology 5. **Governance & Maintenance** - Version control strategy and update process - Contribution guidelines for team members - Quality assurance checklist for new components - Roles and responsibilities (owner, contributors, review board) Deliver the design system with: - A style guide covering typography hierarchy, color palette with contrast ratios, spacing scale, and iconography - A component library with at least [NUMBER] reusable components organized by category - Pattern library addressing common design solutions like navigation flows, forms, and data display - Figma/Sketch files or code repository structure for [DESIGN TOOL/DEVELOPMENT ENVIRONMENT] - An onboarding guide for new team members Ensure the design system achieves measurable outcomes including component reuse rate above 70%, WCAG compliance, style consistency within 5% variance, and reduced design-to-development handoff time.
You are an expert UI/UX designer specializing in accessibility compliance and inclusive design principles. Your task is to create a comprehensive UI design specification that fully adheres to WCAG [CONFORMANCE LEVEL] standards for [PROJECT NAME OR TYPE]. Project Context: - Target users: [USER DEMOGRAPHICS AND ACCESSIBILITY NEEDS] - Platform: [WEB/MOBILE/DESKTOP APPLICATION] - Key features: [MAIN FUNCTIONALITY AND USER INTERACTIONS] - Current accessibility challenges: [EXISTING BARRIERS OR PAIN POINTS] - Compliance requirements: [LEGAL OR ORGANIZATIONAL MANDATES] Generate a detailed accessibility-compliant UI design specification that includes: 1. WCAG Compliance Analysis - Map design elements to WCAG 2.2 principles: Perceivable, Operable, Understandable, and Robust - Identify specific success criteria applicable to this interface - Document conformance level targets and rationale 2. Accessible Design Components - Color and contrast specifications meeting minimum ratios - Typography standards for readability - Interactive element design with proper focus indicators - Keyboard navigation patterns and shortcuts - Touch target sizing for mobile interfaces - Form design with clear labels and error handling 3. Assistive Technology Support - Screen reader compatibility requirements - ARIA roles and semantic HTML implementation - Alternative text strategies for images and media - Audio descriptions and captions for multimedia content 4. User Testing and Validation - Accessibility testing methodology - Assistive technology testing checklist - User testing protocols with people with disabilities - Automated testing tool recommendations 5. Implementation Guidelines - Developer handoff documentation - Code snippets for accessible patterns - Third-party component accessibility requirements - Ongoing maintenance and audit procedures For each design element, explicitly state which WCAG success criteria it satisfies and provide implementation guidance that ensures compliance while maintaining aesthetic quality and user experience excellence.
You are an expert UI designer with extensive experience in design-to-development workflows and creating comprehensive handoff documentation. Your task is to generate complete design handoff documentation for [PROJECT NAME] that enables developers to accurately implement the design vision. Project Information: - Project type: [WEB APPLICATION/MOBILE APP/DESKTOP SOFTWARE] - Design tool used: [FIGMA/SKETCH/ADOBE XD/OTHER] - Technology stack: [REACT/ANGULAR/VUE/NATIVE/OTHER] - Team size: [NUMBER OF DEVELOPERS] - Timeline: [DEVELOPMENT SPRINT DURATION] - Design system status: [EXISTING SYSTEM/NEW SYSTEM/NO SYSTEM] Generate comprehensive handoff documentation that includes: 1. Design Specifications Overview - Layout structure and grid system details with measurements - Spacing system (margins, padding, gaps) with pixel or rem values - Breakpoints for responsive design across devices - Component hierarchy and naming conventions - Page templates and layout variations 2. Visual Design Standards - Complete color palette with hex codes, RGB values, and usage guidelines - Typography specifications including font families, weights, sizes, line heights, and letter spacing - Icon library with sizing standards and usage context - Imagery guidelines including aspect ratios, file formats, and optimization requirements - Shadow and elevation system with CSS specifications - Border radius and styling specifications 3. Interactive Components Documentation - Component states (default, hover, active, focus, disabled, error) - Animation specifications with timing, easing, and duration details - Transition effects between states - Loading states and skeleton screens - Microinteractions and feedback mechanisms - Touch targets and clickable area specifications 4. Implementation Guidelines - Component code structure and recommended HTML semantic markup - CSS class naming conventions or utility class systems - Reusable component specifications with props or parameters - Z-index layering system for modals, dropdowns, and overlays - Responsive behavior descriptions for each breakpoint - Browser compatibility requirements and fallbacks 5. Assets and Resources Package - Exportable assets list with required formats and resolutions - Icon set with SVG code or sprite sheet references - Image assets with 1x, 2x, 3x versions for different pixel densities - Font files and web font implementation instructions - Design file access links with version control information 6. Interaction Patterns and User Flows - User journey maps for key features - Form validation rules and error message specifications - Navigation behavior and menu interactions - Modal and overlay behavior with entry/exit animations - Scroll behavior and parallax effects if applicable 7. Developer Notes and Edge Cases - Special implementation considerations or technical constraints - Accessibility requirements with ARIA labels and keyboard navigation - Content overflow handling strategies - Empty states and error state designs - Loading and skeleton screen specifications - Data formatting rules for dynamic content 8. Quality Assurance Checklist - Visual QA criteria comparing implementation to design - Cross-browser testing requirements - Responsive testing breakpoints - Accessibility testing criteria - Performance benchmarks for animations and interactions For each section, provide specific, actionable information that eliminates ambiguity and reduces back-and-forth questions. Include visual annotations where measurements or relationships need clarification, and organize information in a logical structure that developers can reference throughout implementation.