Create clear, actionable user flow diagrams and task flows that visualize how users navigate through your product to accomplish specific goals. This prompt helps UX designers map user paths, identify friction points, optimize conversion funnels, and ensure seamless experiences from entry points to task completion across all user scenarios.
This prompt helps you create detailed user flow diagrams and task flows that visualize how users navigate through your product. Fill in the bracketed placeholders with specific information about your feature, target users, and the goals they want to accomplish. Be clear about entry points, key screens involved, and any existing friction points. The more detailed your input, the more actionable and accurate the resulting flow diagrams will be. Use the output to align teams, identify optimization opportunities, and guide interface design decisions.
User flows and task flows serve different purposes in UX design. Task flows are linear, single-path diagrams showing the steps required to complete one specific task, ideal for focused actions like password reset or checkout processes. User flows are more comprehensive, multi-branched diagrams showing all possible routes users can take, including decision points and alternative paths based on user choices or system states. Task flows assume a consistent starting point and focus on efficiency, while user flows account for multiple entry points and user types. The output will recommend which type best suits your needs based on complexity. Simple, linear tasks benefit from task flows, while complex features with multiple scenarios require full user flows.
The generated flow diagrams follow established UX conventions using standard shapes and symbols for universal understanding. Ovals represent entry and exit points, rectangles show screens or pages, diamonds indicate decision points where paths branch, and arrows show directional flow. Each element is clearly labeled with concise, descriptive text. The diagrams organize visually from left-to-right or top-to-bottom for easy comprehension. Color coding differentiates path types—green for happy paths, yellow for alternatives, and red for error states. The output includes a legend explaining all symbols and colors used. Complex flows are broken into manageable sections or swimlanes to maintain readability while capturing all scenarios.
The flow diagrams comprehensively map the entire user journey from entry to exit. They identify all entry points including homepage, landing pages, email links, notifications, or deep links, as different origins may affect subsequent paths. Each screen, page, or interface state is represented with user actions required and system responses triggered. Decision points show where user choices or system validations create branching paths. The output documents happy paths where users successfully complete their goal, alternative valid paths, error states with recovery options, and edge cases for first-time users, returning users, or special permissions. This comprehensive view reveals the complete user experience across all scenarios.
The output includes actionable recommendations to optimize flows by reducing friction and streamlining user paths. It identifies opportunities to minimize steps, eliminate unnecessary decision points, pre-fill known information, or provide skip options for experienced users. Each flow includes success metrics like completion rate, time-to-task-completion, and error frequency to measure effectiveness. The output suggests specific analytics tracking points at critical steps and decision nodes. It recommends A/B testing opportunities for alternative approaches and proposes usability testing scenarios to validate flow assumptions. Documentation includes business rules, technical dependencies, and edge case handling to support implementation and future maintenance.
You are an expert interaction designer specializing in creating intuitive button states and delightful micro-interactions that provide clear feedback, enhance usability, and create engaging user experiences. Design a comprehensive button state system and micro-interaction framework for [PROJECT/APPLICATION NAME] targeting [PLATFORM: web, iOS, Android, desktop]. The button system should serve [USER PERSONA] and support [PRIMARY USE CASES/ACTIONS]. ## Project Context: **Application Overview:** - Product type: [e.g., SaaS dashboard, e-commerce, mobile app, enterprise tool] - Primary user actions: [e.g., form submissions, transactions, content creation] - Interaction complexity: [simple clicks, multi-step processes, real-time updates] - Brand personality: [professional, playful, minimalist, dynamic] **Technical Environment:** - Platform: [Web, iOS, Android, Cross-platform] - Implementation: [CSS animations, JavaScript, React/Vue components, native animations] - Performance constraints: [60fps requirement, low-end device support, accessibility needs] - Animation preferences: [subtle, moderate, expressive] ## Button Types & Hierarchy: Define button styles for: **Primary Buttons:** - Purpose: [Main CTAs like Submit, Purchase, Save, Create] - Visual weight: Highest emphasis with solid fill - Usage guideline: [One per screen/section, for primary action] **Secondary Buttons:** - Purpose: [Alternative actions like Cancel, Go Back, Learn More] - Visual weight: Medium emphasis with outline or ghost style - Usage guideline: [Supporting actions alongside primary] **Tertiary/Text Buttons:** - Purpose: [Low-priority actions like Skip, Dismiss, View Details] - Visual weight: Minimal emphasis, text-only or subtle styling - Usage guideline: [Optional or less critical actions] **Icon Buttons:** - Purpose: [Compact actions like Close, Menu, Share, Favorite] - Visual weight: Varies by context - Usage guideline: [Navigation, toolbars, inline actions] **Additional Types:** - Floating Action Button (FAB): [Mobile primary action] - Toggle Buttons: [On/Off states, selection groups] - Split Buttons: [Primary action with dropdown alternatives] ## Complete Button State System: Design specifications for all essential states: ### 1. Default/Enabled State **Visual Characteristics:** - Color: [PRIMARY BRAND COLOR with sufficient contrast] - Typography: [Font family, size, weight, letter-spacing] - Padding: [Vertical and horizontal spacing, minimum 44x44px touch target] - Border radius: [0px sharp, 4px slight, 8px rounded, full pill] - Shadow/elevation: [None, subtle 2px, medium 4px] - Cursor: pointer **Design Principles:** - Clearly indicates clickability through color and positioning - Sufficient contrast ratio: 4.5:1 text-to-background minimum for WCAG AA - Distinctive from surrounding elements - Consistent with brand visual language ### 2. Hover State **Visual Changes:** - Color shift: [Lighten by 10%, darken by 15%, or specify hex] - Background transformation: [Opacity change, gradient shift, color transition] - Border modification: [Add outline, increase width, change color] - Shadow enhancement: [Elevate from 2px to 4px, add glow effect] - Scale transformation: [Scale(1.02) subtle grow effect] - Cursor: pointer **Transition Specifications:** - Duration: [150ms-200ms for responsiveness without lag] - Easing: [ease-in-out, cubic-bezier(0.4, 0, 0.2, 1)] - Properties: [background-color, box-shadow, transform] **Design Principles:** - Immediate feedback within 100ms of hover - Subtle enough not to distract, clear enough to notice - Consistent hover behavior across all button types ### 3. Focus State **Visual Indicators:** - Focus ring: [2-3px outline in contrasting color, 2px offset] - Focus color: [Brand color, high-contrast blue, or accessible choice] - Background change: [Optional subtle highlight] - Combination: [Both outline and background for clarity] **Accessibility Requirements:** - Minimum 3:1 contrast ratio for focus indicator against background - Visible on all interactive elements for keyboard navigation - Never remove default focus without providing alternative - Sufficient offset to prevent clipping by button edges **Keyboard Behavior:** - Focus via Tab key navigation - Activate via Enter or Space key - Clear focus order following logical reading flow ### 4. Active/Pressed State **Visual Feedback:** - Color: [Darker shade, 20-30% darker than default] - Transform: [Scale(0.98) to simulate depression] - Shadow: [Reduce or inset shadow for pressed effect] - Position: [Translate(0, 1px) downward shift] **Timing:** - Instant response on mousedown/touchstart - Duration: 50-100ms for tactile feel - Return to hover state on mouseup within button - Return to default if mouseup outside button **Design Principles:** - Mimics physical button pressing for familiarity - Provides immediate tactile-like feedback - Prevents accidental double-clicks through visual confirmation ### 5. Disabled State **Visual Characteristics:** - Color: [Gray scale, desaturated version of default] - Opacity: [40-60% of enabled state] - Cursor: not-allowed or default - Text color: [Reduced contrast while maintaining readability] - Remove shadows and interactive effects **Behavior:** - No hover, focus, or click responses - Aria-disabled="true" for screen readers - Tooltip explanation when disabled (optional) **Usage Guidelines:** - Use when action is temporarily unavailable - Provide context for why button is disabled when possible - Re-enable dynamically when conditions are met - Avoid hiding buttons; show disabled state for awareness ### 6. Loading State **Visual Elements:** - Loading indicator: [Spinner, progress bar, skeleton, animated dots] - Button text: [Replace with "Loading..." or keep original with spinner] - Width: [Maintain original width to prevent layout shift] - Disabled interactions during load - Cursor: wait or progress **Animation Specifications:** - Spinner: [Size 16-20px, 1-2s rotation duration, infinite loop] - Position: [Replace text, inline before/after text, overlay] - Color: [Contrast with button background, typically white or brand] **Design Principles:** - Prevent multiple submissions through disabled state - Provide immediate feedback that action is processing - Loading duration visibility: instant for <500ms, show for longer - Maintain button dimensions to prevent layout reflow ### 7. Success State (Optional) **Visual Confirmation:** - Icon: [Checkmark, animated success icon] - Color transition: [Change to success green] - Animation: [Checkmark draw-in, scale pulse] - Duration: [1-2 seconds before returning or navigating] **Use Cases:** - Form submissions - Payment confirmations - Save actions - Item additions to cart/favorites ### 8. Error State (Optional) **Visual Feedback:** - Color: [Error red background or border] - Icon: [Error icon, shake animation] - Text: [Change to error message] - Animation: [Horizontal shake, border pulse] **Use Cases:** - Failed submissions - Validation errors - Network failures - Permission denials ## Micro-Interactions Framework: Design purposeful micro-interactions for: **Button Hover Effects:** - Subtle scale or lift animations - Color transitions and gradient shifts - Icon animations (arrows sliding, icons rotating) - Underline or border animations **Click Feedback:** - Ripple effect from click point - Scale down then up (press effect) - Color pulse or flash - Particle effects for celebratory actions **State Transitions:** - Smooth morphing between states - Loading to success animations - Error shake with recovery - Disabled to enabled fade-in **Contextual Micro-Interactions:** - Icon changes on hover (arrow to checkmark) - Badge count updates with bounce - Tooltip appearances on focus - Progress indicators for multi-step actions ## Animation Specifications: **Timing Guidelines:** - Immediate feedback: 0-100ms (hover, focus detection) - Quick transitions: 100-300ms (state changes, color shifts) - Moderate animations: 300-500ms (loading indicators, success confirmations) - Extended animations: 500-1000ms (complex multi-step feedback) **Easing Functions:** - Linear: Progress bars, loading spinners - Ease-in-out: Most button state transitions - Ease-out: Entrance animations, expanding elements - Ease-in: Exit animations, collapsing elements - Custom cubic-bezier: [Specify for brand-specific motion] **Performance Considerations:** - Use transform and opacity for 60fps performance - Avoid animating width, height, left, right, top, bottom - Use will-change sparingly for complex animations - Provide reduced-motion alternative for accessibility - Test on low-end devices for smooth performance ## Accessibility Requirements: - Keyboard navigation with visible focus indicators - ARIA labels for icon-only buttons - aria-disabled, aria-pressed, aria-expanded states - Minimum 44x44px touch targets for mobile - Support for prefers-reduced-motion media query - Screen reader announcements for state changes - Sufficient color contrast in all states (WCAG AA minimum) - No reliance on color alone to convey state ## Deliverables: 1. **Button State Design System:** - Visual designs for all 8 button states across all button types - Side-by-side comparison showing state transitions - Organized in [Figma/Sketch/Adobe XD] with component variants - Responsive behavior for mobile, tablet, desktop 2. **Micro-Interaction Library:** - Animated prototypes demonstrating each interaction - Timing and easing specifications document - Animation flows showing transition sequences - Video or GIF exports for developer reference 3. **Technical Specifications:** - CSS code snippets for each state - Animation keyframes and transitions - JavaScript interaction logic (if needed) - Framework-specific components [React, Vue, Angular] 4. **Implementation Guide:** - Code examples with inline comments - Accessibility implementation checklist - Performance optimization recommendations - Browser compatibility notes - Testing scenarios for QA 5. **Design Documentation:** - When to use each button type - State transition diagrams - Do's and don'ts with visual examples - Accessibility guidelines and WCAG compliance notes - Motion design principles and brand motion language Ensure all button states and micro-interactions achieve: - 100-150ms response time for immediate feedback - 60fps smooth animations without jank - WCAG 2.2 AA compliance minimum - Consistent behavior across all platforms - Purposeful design that enhances rather than decorates
Create comprehensive voice and tone guidelines for [BRAND NAME] in the [INDUSTRY/SECTOR] industry. The brand offers [PRODUCTS/SERVICES] targeting [TARGET AUDIENCE]. Core brand values include [BRAND VALUES], and the brand personality can be described as [BRAND PERSONALITY]. Include a brand voice overview, 3-5 voice characteristics with 'We are/We are not' statements, tone variations for different channels and contexts, practical writing guidelines, and examples of the voice in action.
You are a world-class Design Thinking facilitator. Guide me through the complete design thinking process to solve this challenge: [DESCRIBE YOUR CHALLENGE/PROJECT/PROBLEM]. The target users/stakeholders are [DESCRIBE TARGET AUDIENCE], and the primary objectives are [DESCRIBE KEY GOALS]. I am [BEGINNER/INTERMEDIATE/EXPERT] with design thinking. Please adjust your guidance accordingly.