AI Prompts Packs

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.

Create a comprehensive empathy map for [TARGET PERSONA] in the context of [SPECIFIC CONTEXT/SITUATION]. Follow the empathy map framework with sections for thinking/feeling, seeing, hearing, saying/doing, pains, and gains. Include 5-7 detailed points for each section written from the persona's perspective.

Create a Hook Model for [PRODUCT/SERVICE] targeting [USER SEGMENT]. Define the following components: 1. EXTERNAL TRIGGERS: What external cues prompt the user to take action? 2. INTERNAL TRIGGERS: What emotions or thoughts drive the user to act? 3. ACTION: What is the simplest behavior in anticipation of a reward? 4. VARIABLE REWARD: What variable outcomes keep the user engaged? 5. INVESTMENT: What effort or input does the user contribute to increase the likelihood of returning?

Analyze [PRODUCT/SERVICE] using the Jobs to Be Done framework. Identify and explore the functional, emotional, and social jobs that customers are trying to accomplish when they 'hire' this product or service. Target audience is [TARGET AUDIENCE]. Current pain points include [PAIN POINTS]. Provide analysis of core functional jobs, emotional jobs, social jobs, job statement formulations, competing solutions, and innovation opportunities.

Create a detailed user journey map for [PERSONA NAME: age, occupation, tech proficiency level, relevant characteristics], who is trying to [SPECIFIC GOAL WITH CONTEXT AND MOTIVATION]

You are an expert Product Manager and Agile practitioner. Create a comprehensive set of well-formed user stories for [DESCRIBE YOUR PROJECT/PRODUCT/FEATURE]. I'm working on this for [DESCRIBE TARGET USERS], and our primary business objectives are [DESCRIBE KEY BUSINESS GOALS]. Focus on user stories for these key functionality areas: [LIST SPECIFIC FUNCTIONALITY AREAS].

Kickstart a UX project for [PROJECT NAME] targeting [USER SEGMENT]. Define the following: 1. PROJECT GOALS: What are the primary objectives? 2. USER NEEDS: What are the key needs and pain points of the target users? 3. DESIGN PRINCIPLES: What principles will guide the design process? 4. SUCCESS METRICS: How will success be measured?

You are an expert strategic planning consultant with 20+ years of experience advising Fortune 500 executives and leadership teams. Your expertise spans multiple strategic frameworks including Balanced Scorecard, OKRs, SWOT analysis, Porter's Five Forces, and McKinsey 7S Model. Your task is to develop a comprehensive strategic plan and vision statement for [ORGANIZATION NAME AND INDUSTRY] that will guide the organization over the next [TIME PERIOD]. Context and Background: - Organization size and structure: [CURRENT ORGANIZATIONAL DETAILS] - Current market position: [MARKET POSITION AND COMPETITIVE LANDSCAPE] - Key challenges faced: [PRIMARY CHALLENGES AND PAIN POINTS] - Available resources: [BUDGET, TEAM, TECHNOLOGY, AND OTHER RESOURCES] - Stakeholder priorities: [KEY STAKEHOLDER EXPECTATIONS AND REQUIREMENTS] Deliver a strategic plan that includes: 1. Vision Statement: A compelling, aspirational statement (2-3 sentences) that articulates where the organization aims to be in [TIME PERIOD]. This should inspire stakeholders and provide clear directional guidance. 2. Mission Alignment: Explain how this vision aligns with the organization's core mission, values, and purpose. 3. Strategic Analysis: Conduct a comprehensive situational analysis using: - SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats) - Key market trends and external factors (PESTEL if applicable) - Competitive positioning assessment 4. Strategic Goals and Objectives: Define 3-5 SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound) that directly support the vision. Each goal should include: - Clear success metrics and KPIs - Resource requirements - Potential risks and mitigation strategies 5. Action Plan and Priorities: For each strategic goal, outline: - Key initiatives and action steps - Responsible parties and governance structure - Quarterly milestones for the first year - Dependencies and critical path items 6. Stakeholder Engagement Strategy: Detail how you will communicate the vision and strategic plan to different stakeholder groups (board, employees, customers, partners) and secure buy-in. 7. Performance Monitoring Framework: Recommend a framework (such as Balanced Scorecard or OKR methodology) for tracking progress, including: - Review cadence (monthly, quarterly, annually) - Dashboard metrics and reporting structure - Adjustment mechanisms for course correction Format your response as an executive-ready strategic planning document with clear sections, actionable insights, and data-driven recommendations. Include relevant strategic frameworks and best practices from leading organizations. Ensure the plan is realistic yet ambitious, accounting for organizational constraints while pushing for transformational growth.

You are an expert executive communications strategist with 15+ years of experience helping C-suite leaders present to boards of directors and manage complex stakeholder relationships. Your expertise spans boardroom dynamics, high-stakes presentation design, stakeholder engagement frameworks (including EDGE model, RACI matrices, and stakeholder mapping), and executive narrative development. Your task is to develop a comprehensive board presentation and stakeholder communication strategy for [ORGANIZATION NAME AND INDUSTRY]. Context and Background: - Type of presentation/communication: [BOARD MEETING TYPE - e.g., quarterly update, strategic initiative approval, crisis management, performance review] - Key decision or outcome needed from board: [SPECIFIC BOARD REQUEST OR DECISION REQUIRED] - Stakeholder groups: [LIST OF KEY STAKEHOLDER GROUPS - board members, investors, employees, partners, customers, regulators] - Primary message or thesis: [CORE MESSAGE OR GOVERNING IDEA TO COMMUNICATE] - Current organizational context: [RELEVANT CONTEXT - market conditions, recent events, performance metrics, challenges] - Audience sophistication level: [BOARD/STAKEHOLDER EXPERTISE LEVEL - financial literacy, industry knowledge, technical understanding] - Available presentation time: [ALLOCATED TIME FOR PRESENTATION AND Q&A] Deliver a comprehensive board presentation and stakeholder communication plan that includes: 1. Executive Presentation Strategy: - Governing Thesis: A compelling, big-idea statement (1-2 sentences) that captures the main point of your discussion and provides the lens through which the board should evaluate your proposal or update. - High-Level Narrative Arc: Outline the logical flow of your presentation from context-setting to decision/recommendation, structured to maintain engagement and build toward your key ask. - Visual Strategy: Describe how you will use data visualization, charts, infographics, and storytelling elements to make complex information accessible while maintaining executive rigor. 2. Board Presentation Structure (15-30 minutes format): - Opening Slide: Hook statement, context, and agenda preview - Section 1 - Situation Analysis: Market context, competitive landscape, organizational performance, relevant trends (2-3 slides) - Section 2 - Key Challenges or Opportunities: Core problems/opportunities that necessitate board input (1-2 slides) - Section 3 - Proposed Solutions or Strategic Initiatives: Detailed recommendations with supporting data, risk analysis, and resource requirements (3-4 slides) - Section 4 - Financial Implications: ROI, budget requirements, financial projections, impact on key metrics (2-3 slides) - Section 5 - Implementation Timeline and Milestones: Phasing, governance, and success metrics (1-2 slides) - Closing and Call-to-Action: Clear statement of what approval, guidance, or decision is needed from the board and next steps 3. Data Presentation and Business Case: - Key Performance Indicators (KPIs): Identify 5-7 critical metrics that demonstrate the issue's significance or initiative's value - Financial Analysis: Provide quantified business case including revenue impact, cost savings, ROI calculation, and break-even timeline - Risk Assessment: Outline top 3-5 risks with mitigation strategies and contingency planning - Competitive or Market Justification: Include external data (market research, competitor analysis, industry trends) that validates the approach 4. Tailored Messaging for Different Stakeholder Groups: - Board Members: Focus on fiduciary responsibility, risk management, strategic alignment, and decision-making requirements - Investor/Shareholder Communication: Emphasize financial performance, growth potential, competitive advantage, and value creation - Employee/Internal Stakeholder Communication: Highlight organizational impact, career opportunities, cultural alignment, and implementation roles - External Partners/Customers: Frame around mutual benefits, partnership evolution, and value delivery - Regulatory/Government Stakeholders: Emphasize compliance, transparency, and societal impact 5. Stakeholder Communication Plan: - Communication Objectives (by group): Define what each interaction should achieve (inform, consult, involve, collaborate, empower) - Communication Cadence and Channels: Specify frequency and preferred channels for each stakeholder group (quarterly meetings, monthly emails, webinars, town halls) - Key Messages (by segment): Develop 3-5 core messages customized for each stakeholder group, using accessible language and group-specific interests - Two-Way Engagement Strategy: Outline how you will gather feedback, address concerns, and demonstrate how stakeholder input influenced decisions - Crisis Communication Protocol: Describe how you will adapt communications during challenges or when addressing sensitive topics 6. Presentation Delivery Guidance: - Pre-Presentation Preparation: Materials to send in advance, agenda setting, stakeholder briefing recommendations - Presentation Skills and Tone: Recommended speaking approach, pacing, handling interruptions, and managing difficult questions - Visual Design Principles: Guidance on slide design, data visualization best practices, and avoiding common pitfalls (information overload, excessive text, poor contrast) - Engagement Techniques: Methods to maintain board attention, invite participation, and foster dialogue rather than passive listening 7. Post-Presentation Engagement: - Board Decision Documentation: Framework for capturing decisions, action items, and owner accountability - Feedback Loop: Mechanism for gathering board/stakeholder input after presentations (surveys, follow-up meetings) - Progress Tracking and "You Said, We Did" Communication: System for regular updates demonstrating how stakeholder feedback influenced outcomes and reinforcing transparency 8. EDGE Model Application: - Expanded Role: How will you position yourself as the organization's bridge to the external stakeholder world? - Distinctive Narrative: What proprietary story or unique perspective differentiates your organization in stakeholder communication? - Growth-Oriented Mindset: How will you empower internal and external ambassadors to articulate the organization's vision consistently? - Engaged Posture: What systematic approach will you use to strengthen stakeholder connections and prepare for inevitable challenges? Format your response as an executive-ready communications strategy document with clear sections, annotated presentation outline, stakeholder communication templates, and actionable delivery recommendations. Include specific examples of messaging, visual strategies, and engagement approaches tailored to your organization's context. Ensure recommendations are grounded in boardroom best practices while remaining adaptable to different presentation scenarios.

You are an expert executive advisor and decision scientist with 20+ years of experience helping C-suite leaders navigate complex, high-stakes decisions. Your expertise spans multiple decision-making frameworks including RAPID, SPADE, OODA Loop, Cynefin Framework, Eisenhower Matrix, Vroom-Yetton-Jago Model, Kepner-Tregoe Decision Analysis, Recognition Primed Decision (RPD) model, and Regret Minimization Framework. You understand organizational dynamics, cognitive biases, risk assessment, and the behavioral economics of executive decision-making. Your task is to guide [EXECUTIVE TITLE/NAME] through a structured decision-making process for [ORGANIZATION NAME AND INDUSTRY] regarding the following strategic decision: Decision Context: - Core decision or choice to be made: [SPECIFIC DECISION STATEMENT - e.g., "Should we acquire Company X?", "Should we pivot our business model?", "Should we enter a new market?"] - Strategic importance and urgency: [WHY THIS DECISION MATTERS NOW - market pressures, competitive threats, opportunities] - Decision complexity level: [SIMPLE/COMPLICATED/COMPLEX/CHAOTIC - describe what makes it complex] - Key stakeholders affected: [LIST INTERNAL AND EXTERNAL STAKEHOLDERS IMPACTED] - Available decision timeline: [TIME CONSTRAINT - immediate, weeks, months] - Risk tolerance and constraints: [ORGANIZATIONAL RISK APPETITE, BUDGET LIMITS, REGULATORY CONSTRAINTS] - Previous related decisions or context: [RELEVANT HISTORY, PRIOR INITIATIVES, LESSONS LEARNED] Deliver a comprehensive executive decision-making analysis that includes: 1. Decision Framework Selection and Rationale: - Analyze the decision context using the Cynefin Framework to determine whether the problem is Simple (best practice), Complicated (expert analysis), Complex (probe-sense-respond), or Chaotic (act-sense-respond) - Recommend the most appropriate primary decision framework(s) based on the decision's complexity, urgency, and stakeholder configuration - Explain why this framework is optimal for this specific decision context and what pitfalls it helps avoid 2. RAPID Decision Rights Matrix (for collaborative decisions): - Recommend: Who provides input and makes recommendations? - Agree: Who must formally agree before the decision proceeds (typically limited to 1-2 people with veto power)? - Perform: Who will execute the decision once made? - Input: Who should be consulted for their expertise or perspective? - Decide: Who is the single decision-maker with final authority? Provide specific names, roles, or organizational functions for each RAPID element to eliminate ambiguity and ensure accountability. 3. Structured Decision Analysis: - Problem Definition: Articulate the decision in clear, unambiguous terms. What exactly are we deciding? What are we NOT deciding? - Objectives and Success Criteria: Define 3-5 key objectives this decision must achieve and measurable success criteria - Alternatives Generation: Identify 3-5 viable alternatives or courses of action, including status quo and creative options - Evaluation Criteria: Establish weighted criteria for evaluating alternatives (strategic fit, financial return, risk level, implementation feasibility, stakeholder impact) - Alternatives Assessment: Systematically evaluate each alternative against the criteria using a decision matrix or scorecard approach 4. Risk Assessment and Scenario Analysis: - Best Case Scenario: Outcomes if everything goes optimally - Base Case Scenario: Most likely outcomes based on realistic assumptions - Worst Case Scenario: Downside risks and failure modes - For each scenario, quantify potential financial impact, timeline to results, probability assessment, and early warning indicators - Identify irreversible decisions vs. reversible decisions (two-way vs. one-way doors) - Outline risk mitigation strategies and contingency plans for major risks 5. Cognitive Bias Check and Challenge Questions: - Identify potential cognitive biases that may distort this decision: confirmation bias, anchoring bias, sunk cost fallacy, optimism bias, groupthink, availability heuristic - Generate 5-7 challenging questions designed to stress-test assumptions and surface hidden risks: * "What would have to be true for this decision to fail?" * "What information, if revealed, would completely change our thinking?" * "Are we solving the right problem or treating a symptom?" * "What would our successor CEO decide if starting fresh?" * Custom questions relevant to the specific decision context 6. OODA Loop for Dynamic Environments (if decision involves fast-changing conditions): - Observe: What data, trends, and signals should we continuously monitor? - Orient: How do we interpret this information given our organizational context, culture, and competitive position? - Decide: What decision rules or triggers will prompt action or course correction? - Act: What are the specific actions and rapid implementation steps? - How will we build feedback loops to enable rapid iteration and adaptation? 7. Regret Minimization Framework (for high-stakes, irreversible decisions): - Project forward 10 years: Looking back from the future, which decision would you most regret not making? - Short-term impact (10-10-10 analysis): How will you feel about this decision in 10 minutes, 10 months, and 10 years? - Opportunity cost analysis: What opportunities are we forgoing by choosing this path? - Reversibility assessment: Can this decision be undone or adapted if circumstances change? 8. Implementation Roadmap and Decision Quality Check: - Immediate next steps (first 30 days after decision) - Key milestones and decision gates for reviewing progress - Communication plan: How will the decision be communicated to stakeholders with rationale? - Monitoring framework: What KPIs will track whether the decision is producing intended results? - Decision review schedule: When will we formally review the decision's outcomes and adapt if needed? 9. Decision Quality Assessment: - Evaluate the decision process quality across six dimensions: * Frame: Is the decision framed correctly? Are we solving the right problem? * Alternatives: Have we generated creative, diverse options? * Information: Do we have sufficient, reliable information? * Values: Are our evaluation criteria aligned with organizational values and strategy? * Reasoning: Is our analysis logical, rigorous, and free from major biases? * Commitment: Do key stakeholders have buy-in and commitment to execute? - Identify any quality gaps that need to be addressed before finalizing the decision 10. Executive Recommendation and Call-to-Action: - Provide a clear, evidence-based recommendation on which alternative to pursue - Summarize the 3-5 most compelling reasons supporting this recommendation - Outline what the executive should do next: whose input is still needed, what additional information should be gathered, when the final decision should be made - Specify the "decision trigger" - what condition or milestone will prompt the final commitment Format your response as an executive decision brief with clear sections, visual decision matrices where appropriate, scenario comparisons, and actionable recommendations. Ensure the analysis is rigorous yet concise, balancing thoroughness with executive-level brevity. Ground all recommendations in the specific decision context while leveraging proven decision science principles and frameworks.

You are an expert organizational transformation consultant with 20+ years of experience leading large-scale change initiatives across Fortune 500 companies. Your expertise spans multiple change management frameworks including Kotter's 8-Step Process, ADKAR Model, Lewin's Change Management Model, McKinsey 7-S Model, Bridges' Transition Model, Prosci Methodology, Kübler-Ross Change Curve, Kaizen, Agile Change Management, and LaMarsh Managed Change. You understand change psychology, resistance management, culture transformation, stakeholder engagement, and the emotional dynamics of organizational transitions. Your task is to develop a comprehensive change management and organizational transformation strategy for [ORGANIZATION NAME AND INDUSTRY]. Transformation Context: - Type of change initiative: [SPECIFIC TRANSFORMATION - digital transformation, merger/acquisition integration, restructuring, culture change, business model pivot, technology implementation, process reengineering] - Scope and scale: [BREADTH - company-wide, division-level, functional area] and [DEPTH - incremental improvement vs. fundamental transformation] - Strategic rationale and drivers: [WHY THIS CHANGE IS NECESSARY - market forces, competitive threats, opportunities, performance gaps] - Current organizational state: [BASELINE - culture, capabilities, readiness, recent change history] - Desired future state: [TARGET VISION - what success looks like in 12-24 months] - Timeline and phases: [TRANSFORMATION TIMELINE AND KEY MILESTONES] - Resources available: [BUDGET, CHANGE TEAM, EXECUTIVE SPONSORSHIP, TECHNOLOGY, EXTERNAL SUPPORT] - Key stakeholder groups: [EMPLOYEES, LEADERSHIP, CUSTOMERS, PARTNERS, UNIONS, REGULATORS] - Anticipated resistance sources: [WHERE RESISTANCE IS EXPECTED AND WHY] Deliver a comprehensive change management and organizational transformation plan that includes: 1. Transformation Vision and Strategic Case for Change: - Compelling Change Story: Craft a 3-5 sentence narrative that articulates why change is essential, what's at stake if the organization doesn't change, and the opportunity the transformation creates. This should be emotionally resonant and strategically sound. - Vision Statement: A clear, inspiring description of the desired future state that employees can visualize and rally behind (2-3 sentences) - Strategic Alignment: Explain how this transformation connects to organizational mission, values, competitive strategy, and long-term sustainability - Burning Platform vs. Aspiration: Determine whether the change narrative should emphasize threats (burning platform) or opportunities (aspirational vision) based on organizational culture and change readiness 2. Change Management Framework Selection and Integration: - Primary Framework Recommendation: Select the most appropriate change model(s) for this transformation based on scope, culture, and change type - Kotter's 8-Step Process: For enterprise-wide transformations requiring urgency and leadership coalition - ADKAR Model: For changes requiring individual behavior change and adoption (technology, process changes) - Lewin's 3-Stage Model: For straightforward changes with clear beginning and end points - McKinsey 7-S: For complex organizational redesigns, M&A integration, or holistic system changes - Bridges' Transition Model: For changes with significant emotional impact requiring psychological transition support - Agile Change Management: For iterative, fast-moving transformations in dynamic environments - Framework Integration Strategy: Explain how multiple frameworks can work together (e.g., Kotter for overall program structure with ADKAR for individual adoption tracking) 3. Kotter's 8-Step Process Implementation (if applicable): - Step 1 - Create Urgency: Strategies to help employees understand why change cannot wait, including data, market trends, competitive threats, or customer feedback - Step 2 - Build the Guiding Coalition: Identify 8-15 influential leaders across functions, levels, and informal networks to champion the change. Include specific criteria for selection. - Step 3 - Form a Strategic Vision: Develop a clear, compelling vision with 3-5 strategic initiatives that make the vision operational - Step 4 - Enlist a Volunteer Army: Communication and engagement strategies to mobilize 10-15% of the workforce as change advocates - Step 5 - Enable Action by Removing Barriers: Identify and systematically remove obstacles including outdated systems, structures, processes, policies, or resistant leaders - Step 6 - Generate Short-Term Wins: Define 3-5 visible, meaningful wins achievable in 3-6 months that build momentum and demonstrate progress - Step 7 - Sustain Acceleration: Strategies to maintain momentum after initial wins, avoiding complacency - Step 8 - Anchor Changes in Culture: Methods to embed new behaviors, norms, and mindsets into organizational culture, performance management, and leadership development 4. ADKAR Individual Change Management (if applicable): - Awareness: Communication plan to build awareness of why change is needed, using multiple channels and messages tailored to different stakeholder groups - Desire: Strategies to create desire to participate and support the change, addressing "What's in it for me?" for different employee segments. Include incentive alignment, recognition programs, and consequence management. - Knowledge: Training and capability-building programs covering what to do, how to do it, and why it matters. Include learning paths, certifications, and knowledge management systems. - Ability: Support structures to translate knowledge into performance including coaching, mentoring, practice environments, and performance support tools - Reinforcement: Mechanisms to sustain change including recognition, rewards, performance metrics, feedback loops, and celebrating successes 5. McKinsey 7-S Organizational Alignment Analysis: - Strategy: How will strategy change? What new strategic priorities emerge? - Structure: What organizational structure changes are required (reporting lines, spans of control, layers, functional configuration)? - Systems: What processes, workflows, and technology systems need to be redesigned? - Shared Values: What cultural elements (beliefs, norms, behaviors) need to shift? What should be preserved? - Style: How must leadership style and management practices evolve? - Staff: What talent gaps exist? What workforce planning, hiring, development, or transition is needed? - Skills: What new capabilities must the organization develop? What training and development is required? - Alignment Assessment: Identify misalignments across the 7-S elements and prioritize interventions to achieve coherence 6. Resistance Management and Stakeholder Engagement: - Stakeholder Analysis: Map stakeholders using a 2x2 matrix (High/Low Influence vs. High/Low Impact). Identify champions, supporters, fence-sitters, and resistors. - Resistance Diagnosis: Identify sources of resistance using categories: * Rational resistance (legitimate concerns about strategy, feasibility, or resources) * Political resistance (power shifts, loss of status or control) * Emotional resistance (fear, anxiety, loss, uncertainty) * Cultural resistance (conflicts with values, norms, or identity) - Engagement Strategies by Stakeholder Segment: Tailor approaches using the engagement spectrum (Inform → Consult → Involve → Collaborate → Empower) - Difficult Conversation Frameworks: Guidance for leaders addressing resistance, including empathetic listening, addressing concerns transparently, and knowing when to move forward despite dissent - Consequence Management: Clear protocols for addressing persistent resistance that undermines transformation success 7. Communication and Engagement Plan: - Communication Principles: Establish guidelines for frequency (over-communicate), transparency (address bad news), consistency (aligned messages from all leaders), and multi-channel approach - Key Message Framework: Develop 5-7 core messages that answer: * Why are we changing? (The case for change) * What will change? (Scope and impact) * What will stay the same? (Continuity and stability) * What's in it for me? (Personal benefits) * How will we support you? (Resources and assistance) * What do I need to do? (Specific actions) * When will this happen? (Timeline and milestones) - Communication Channels and Cadence: Town halls (monthly), leader cascades (weekly), email updates (bi-weekly), intranet/digital hub (continuous), small group dialogues (as needed) - Two-Way Communication: Mechanisms for gathering feedback, addressing questions, and demonstrating how employee input shapes the transformation (pulse surveys, listening sessions, crowdsourcing platforms) - Leadership Visibility: Expectations for executive presence, site visits, skip-level meetings, and symbolic actions that demonstrate commitment 8. Bridges' Transition Model - Psychological Journey Management: - Ending, Losing, Letting Go: Help people understand what is ending and process loss. Acknowledge emotions, honor the past, and provide closure rituals. - Neutral Zone: Support people through the confusing transition period between old and new. Provide patience, temporary structures, coaching, and reassurance that discomfort is normal. - New Beginning: Launch new practices with celebration, reinforcement, recognition of early adopters, and clear articulation of new norms and expectations. - Emotional Support Strategies: Manager toolkits, peer support networks, EAP resources, and change coaching 9. Capability Building and Change Team Structure: - Change Leadership Team: Define governance structure including executive sponsor, transformation leader, change management office, workstream leads, and change agent network - Change Agent Network: Recruit 1 change agent per 50-100 employees across all functions and levels. Define roles, training, support, and recognition. - Manager Enablement: Managers are critical to change success. Provide manager-specific training, toolkits, conversation guides, and coaching on leading their teams through transition. - Change Management Capability: Build organizational change management competency through training, certification programs, communities of practice, and methodology documentation 10. Measurement, Monitoring, and Course Correction: - Change Adoption Metrics (Leading Indicators): Training completion, change agent activation, communication reach, employee sentiment (pulse surveys), leadership engagement, early adopter behavior - Business Impact Metrics (Lagging Indicators): Performance KPIs, productivity measures, customer satisfaction, quality metrics, financial results - Resistance and Risk Indicators: Attrition rates, absenteeism, engagement scores, grievances, safety incidents - Feedback Mechanisms: Regular pulse surveys (monthly or quarterly), focus groups, change readiness assessments, after-action reviews - Governance and Review Cadence: Weekly change team meetings, monthly steering committee reviews, quarterly board updates - Adaptation Protocols: Clear decision-making process for adjusting approach based on data, including escalation pathways and decision rights 11. Quick Wins and Momentum Building: - Define 3-5 Quick Wins: Identify visible, meaningful achievements deliverable within 3-6 months that demonstrate progress, build confidence, and create momentum - Quick Win Criteria: Visible to large numbers of people, clearly linked to transformation goals, difficult to argue against, achievable without major controversy - Celebration and Recognition Strategy: How will you amplify successes, recognize contributors, and use wins to build broader support? 12. Sustainability and Culture Embedding: - Performance Management Integration: Align individual goals, performance reviews, and compensation with new behaviors and priorities - Talent and Succession Planning: Ensure hiring profiles, promotion criteria, and succession plans reflect desired culture and capabilities - Leadership Development: Embed new leadership competencies and behaviors into development programs, 360 feedback, and coaching - Onboarding: Update new employee onboarding to socialize new culture, ways of working, and transformation story - Symbolism and Rituals: Identify symbolic actions, policies, or rituals that reinforce the new culture (e.g., meeting formats, decision processes, workspace design) - Sustaining Mechanisms: Create ongoing reinforcement including storytelling, recognition programs, continuous improvement processes, and lessons learned integration Format your response as an executive-ready transformation playbook with clear sections, stakeholder-specific strategies, implementation timelines, and measurable milestones. Include practical tools such as communication templates, resistance management frameworks, and change readiness assessments. Ensure the plan balances strategic rigor with empathy for the human experience of change, recognizing that successful transformation requires both head (rational case) and heart (emotional engagement).

You are an expert UX researcher with extensive experience in planning and conducting user research studies across diverse industries. Your task is to create a comprehensive user research plan and interview guide for the following project: Project Context: [DESCRIBE YOUR PRODUCT, FEATURE, OR DESIGN CHALLENGE] Target Users: [DESCRIBE YOUR TARGET AUDIENCE AND KEY USER SEGMENTS] Research Objectives: [LIST YOUR PRIMARY RESEARCH GOALS AND QUESTIONS] Timeline and Constraints: [SPECIFY AVAILABLE TIME, BUDGET, AND RESOURCES] Based on this information, create a complete user research plan that includes: 1. Problem Statement: A clear articulation of what you're trying to learn and why 2. Research Questions: 3-5 specific questions that align with your objectives 3. Methodology Recommendation: Appropriate research methods (interviews, usability tests, surveys, etc.) with rationale for each selection 4. Participant Recruitment: Detailed criteria for participant selection, sample size recommendations, and screening questions 5. Research Timeline: A realistic schedule with milestones for each phase (planning, recruitment, conducting research, analysis, reporting) 6. Interview Discussion Guide: A structured guide including: - Welcome and introduction script - Ice-breaker questions - Core interview questions organized by theme - Follow-up probes for deeper insights - Closing questions and thank you 7. Data Analysis Approach: Methods for synthesizing findings (thematic analysis, affinity mapping, etc.) 8. Deliverables: Expected outputs (research report, personas, journey maps, etc.) Ensure the interview questions are open-ended, non-leading, and designed to uncover user behaviors, motivations, pain points, and goals. Include both behavioral questions about past experiences and contextual questions about current needs.

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 crisis management and communications consultant with 20+ years of experience advising C-suite executives through major organizational crises including cybersecurity breaches, product failures, leadership scandals, natural disasters, regulatory violations, reputational attacks, workplace incidents, and financial distress. Your expertise spans crisis communication frameworks including the 10Cs Model, SCCT (Situational Crisis Communication Theory), CERC (Crisis and Emergency Risk Communication), stakeholder management protocols, media relations, social media crisis response, and business continuity planning. Your task is to develop a comprehensive crisis communication and management response plan for [ORGANIZATION NAME AND INDUSTRY]. Crisis Context: - Type of crisis: [SPECIFIC CRISIS - cybersecurity breach, product recall, executive misconduct, workplace safety incident, regulatory violation, reputational attack, financial crisis, natural disaster, supply chain disruption, legal action] - Current status: [EMERGING/ACTIVE/ESCALATING/RECOVERING - describe current phase] - Severity and scope: [IMPACT LEVEL - localized vs. widespread, contained vs. spreading, short-term vs. long-term implications] - Stakeholders affected: [EMPLOYEES, CUSTOMERS, INVESTORS, PARTNERS, REGULATORS, MEDIA, COMMUNITIES, PUBLIC] - Known facts and unknowns: [WHAT WE KNOW FOR CERTAIN vs. WHAT REMAINS UNCLEAR] - Timeline: [WHEN CRISIS BEGAN, KEY EVENTS, EXPECTED DURATION] - Root causes (if known): [IMMEDIATE TRIGGERS AND UNDERLYING SYSTEMIC ISSUES] - Regulatory or legal implications: [COMPLIANCE REQUIREMENTS, POTENTIAL PENALTIES, REPORTING OBLIGATIONS] - Media and social media activity: [CURRENT COVERAGE, PUBLIC SENTIMENT, MISINFORMATION SPREAD] - Previous crisis history: [RELEVANT PAST CRISES AND HOW THEY WERE HANDLED] - Available resources: [CRISIS TEAM, SPOKESPERSONS, BUDGET, EXTERNAL SUPPORT] Deliver a comprehensive crisis communication and management plan that includes: 1. Immediate Crisis Assessment and Triage (First 24-48 Hours): - Crisis Classification: Categorize using severity matrix (Low/Medium/High/Catastrophic) and type (operational, reputational, financial, regulatory, safety, security) - Stakeholder Impact Analysis: Identify who is affected, how severely, and what their immediate concerns are - Threat Assessment: Evaluate threats to people safety, financial stability, regulatory compliance, reputation, operational continuity, and long-term viability - Information Gaps: Identify critical unknowns that need immediate investigation to inform response strategy - First Response Priorities: Define the top 3-5 actions that must occur in the first 24-48 hours (safety measures, notification requirements, containment actions) - Activation Threshold: Confirm whether the situation warrants full crisis team activation or can be managed through standard incident response 2. Crisis Management Team Structure and Governance: - Crisis Management Team (CMT) Composition: Define core team including CEO/Executive Sponsor, Crisis Manager/Coordinator, Communications Lead, Legal Counsel, HR Lead, Operations Lead, IT/Security (if relevant), and relevant business unit leaders - Roles and Responsibilities: Clear RACI matrix for key decisions (Who Recommends, who has Authority to approve, who must be Consulted, who is Informed) - Decision-Making Authority and Escalation: Define what decisions can be made by CMT vs. requiring board involvement, with clear thresholds and escalation protocols - Crisis Command Center: Physical or virtual space for team coordination with communication tools, documentation systems, and stakeholder contact databases - Meeting Cadence: Crisis briefing schedule (e.g., every 6-12 hours during acute phase, daily during recovery, with ad-hoc sessions as needed) - Documentation Protocols: Systems for logging decisions, actions, communications, and timestamp records for legal protection and post-crisis review 3. 10Cs Crisis Communication Framework Application: - Care: Demonstrate genuine concern for those affected. Prioritize safety, well-being, and support before defensive positioning - Commitment: Express clear commitment to resolving the issue, supporting affected parties, and preventing recurrence - Consistency: Ensure all spokespersons deliver aligned messages across all channels and touchpoints - Clarity: Use plain language avoiding jargon, legal hedging, or corporate speak that obscures meaning - Control: Take control of the narrative by communicating proactively rather than reactively responding to media inquiries - Confidence: Project calm, competent leadership even amid uncertainty. Acknowledge unknowns without appearing lost or defensive - Competence: Demonstrate organizational capability to handle the crisis through specific actions, expertise deployment, and resource mobilization - Credibility: Build trust through transparency, honesty about mistakes, and follow-through on commitments - Collaboration: Engage stakeholders as partners in resolution rather than adversaries to be managed - Closure: Provide clear information about resolution, lessons learned, and preventive measures to enable stakeholder closure 4. Stakeholder-Specific Communication Strategy: - Employees (Internal First Rule): Always inform employees before external communications. Provide more detail, context, and support resources. Hold town halls, manager briefings, and create internal FAQ. Address job security concerns explicitly. - Customers/Clients: Focus on how they are affected, what actions they should take, how you're protecting them, and what support is available. Provide direct channels for questions and assistance. - Investors/Shareholders: Emphasize financial implications, risk mitigation, governance response, and long-term business impact. Comply with disclosure requirements. Coordinate with investor relations and legal. - Board of Directors: Provide comprehensive briefings on situation, response actions, financial/legal implications, and reputational risks. Seek guidance on major decisions and keep informed of developments. - Media: Designate single spokesperson or small team. Prepare holding statements, press releases, and media Q&A. Establish media monitoring and rapid response protocols. Consider proactive media briefings vs. reactive responses. - Regulators/Government: Understand mandatory reporting requirements and timelines. Assign liaison to coordinate with regulatory bodies. Provide transparent, complete information to demonstrate cooperation and compliance. - Partners/Suppliers: Explain operational impacts, continuity plans, and what support or actions are needed from them. Maintain relationship trust through transparency. - Community/Public: Address broader societal concerns, environmental impacts, or safety issues. Engage community leaders and local officials as appropriate. 5. Core Message Development and Holding Statements: - Primary Message Framework addressing: * Acknowledgment: "What happened and what we know so far" * Concern: "How we feel about the impact on stakeholders" * Action: "What we're doing immediately to address the situation" * Accountability: "Our responsibility and commitment to resolution" * Prevention: "Steps to prevent recurrence" * Support: "Resources available for affected stakeholders" - Holding Statement (if full facts unknown): Template acknowledging situation, expressing concern, outlining immediate actions, and committing to updates as information becomes available - Key Messages by Stakeholder Group: Tailored versions emphasizing different aspects relevant to each audience while maintaining consistency on core facts - Message Discipline: Protocol ensuring all communications are approved through crisis team before release, with version control and audit trail 6. Multi-Channel Communication Execution: - Owned Channels: Website crisis hub, email notifications, employee intranet, customer portals, mobile apps - Social Media: Real-time monitoring, rapid response protocol, coordinated posting schedule, community management guidelines for addressing comments/questions - Traditional Media: Press releases, media briefings, interviews, press conferences (if warranted by severity) - Direct Outreach: Personal calls/emails to key stakeholders (major customers, board members, regulators, partners) - Hotlines/Contact Centers: Dedicated crisis hotline with trained representatives, FAQ scripts, and escalation procedures - Third-Party Channels: Industry associations, advocacy groups, or government agencies who can amplify your messages to relevant constituencies - Communication Cadence: Initial statement (within hours), update at 24 hours, then regular updates (daily during acute phase, less frequent as crisis stabilizes) 7. Media Relations and Spokesperson Strategy: - Spokesperson Selection: Designate primary spokesperson (typically CEO for major crises, crisis manager or relevant executive for smaller incidents). Train backup spokesperson. - Media Training Refresh: Rapid briefing on message discipline, bridging techniques, avoiding speculation, handling hostile questions, and maintaining composure - Media Q&A Preparation: Anticipate 20-30 toughest questions across all angles (facts, accountability, prevention, financial impact, leadership responsibility). Prepare approved responses. - Press Conference Protocols (if needed): Format, timing, location, spokesperson lineup, statement structure, and Q&A ground rules - Media Monitoring: Real-time tracking of news coverage, social media mentions, and narrative evolution. Identify misinformation requiring correction. - Rapid Response Team: Designated team monitoring media and social channels 24/7 during acute crisis phase, empowered to respond quickly within approved parameters 8. Social Media Crisis Response: - Social Listening: Deploy monitoring tools to track mentions, sentiment, trending hashtags, and influencer commentary across platforms - Response Protocols: Guidelines for when to respond publicly vs. privately, when to ignore trolls vs. address legitimate concerns, and approval processes for time-sensitive responses - Comment Moderation: Policies for managing comments on owned channels (delete/hide criteria, engagement guidelines) - Employee Social Media Guidelines: Clear guidance on what employees should/shouldn't post, how to direct inquiries, and avoiding speculation - Influencer Engagement: Identify key influencers (positive, neutral, negative) and strategies for engagement or correction - Content Publishing Suspension: Decision criteria for pausing regular marketing/promotional content during crisis to avoid tone-deaf messaging 9. SCCT Crisis Response Strategy Selection: - Crisis Responsibility Attribution: Assess where crisis falls on responsibility spectrum: * Victim (organization is also a victim - natural disaster, malicious attack) * Accidental (unintentional crisis with minimal organizational responsibility) * Preventable (organization knowingly took risky actions or violated regulations) - Response Strategy Recommendation based on responsibility level: * Victim Crises: Instructing information (what happened, how to protect themselves) and expressions of concern * Accidental Crises: Instructing + Adjusting information (corrective actions) + expressions of concern * Preventable Crises: Rebuild strategies including full apology, compensation for damages, and comprehensive corrective actions - Reputation Threat Assessment: Evaluate crisis history (past similar incidents increase threat), prior relational reputation (strong relationships provide protective buffer) - Response Strategy Justification: Explain why recommended approach matches the crisis type and responsibility attribution 10. Business Continuity and Operational Response: - Immediate Containment Actions: Steps to prevent crisis escalation (product removal, system shutdown, facility evacuation, service suspension) - Continuity Priorities: Critical operations that must continue and workarounds for disrupted functions - Resource Mobilization: Personnel deployment, budget allocation, vendor engagement, and external expert recruitment - Remediation Plan: Specific technical, operational, or procedural fixes to address root causes - Timeline and Milestones: Phased response with clear deliverables and completion targets 11. Legal, Regulatory, and Compliance Considerations: - Mandatory Reporting: Identify all regulatory notification requirements (timing, content, recipients) - Legal Risk Assessment: Potential litigation, penalties, or enforcement actions - Privilege Protection: Guidelines for maintaining attorney-client privilege during investigation and communications - Document Preservation: Legal hold implementation to preserve relevant documents and communications - Settlement/Remediation Authority: Decision rights for financial settlements, corrective action commitments, or regulatory negotiations - Communication Review: Legal and compliance review protocols for external communications to minimize liability while maintaining transparency 12. Recovery, Lessons Learned, and Reputation Restoration: - Recovery Phase Communications: Shift from crisis mode to recovery messaging emphasizing resolution, lessons learned, and strengthened systems - Post-Crisis Review: Structured debrief examining what worked, what didn't, decision quality, communication effectiveness, and stakeholder satisfaction - Corrective Action Plan: Documented improvements to policies, procedures, training, systems, or governance to prevent recurrence - Reputation Monitoring: Ongoing tracking of brand sentiment, stakeholder confidence, and media narrative over 3-6 months post-crisis - Relationship Repair: Targeted engagement with stakeholders whose trust was damaged, including personal outreach, transparency commitments, and demonstrated change - Crisis Plan Updates: Incorporate lessons learned into crisis management plan, communication templates, and team training - Organizational Resilience Building: Long-term investments in risk management, early warning systems, crisis preparedness, and organizational culture that encourages transparency and rapid escalation Format your response as an executive crisis playbook with clear sections, stakeholder communication templates, decision frameworks, and hour-by-hour action plans for the first 72 hours. Include specific messaging examples, media Q&A, and social media response templates tailored to your crisis context. Ensure the plan balances speed with accuracy, transparency with legal protection, and empathy with accountability. Recognize that crisis management is as much about leadership presence, stakeholder trust, and organizational values as it is about tactical communication execution.

You are an expert UX researcher specializing in transforming user research data into actionable personas. Your task is to analyze research findings and create comprehensive user personas that will guide design decisions. Research Data Available: [DESCRIBE YOUR RESEARCH DATA - INCLUDE INTERVIEWS, SURVEYS, ANALYTICS, USABILITY TESTS, ETC.] Product/Project Context: [DESCRIBE THE PRODUCT, SERVICE, OR FEATURE YOU ARE DESIGNING] Key Research Insights: [SUMMARIZE MAIN FINDINGS, PATTERNS, AND THEMES FROM YOUR RESEARCH] Number of Personas Needed: [SPECIFY HOW MANY USER SEGMENTS YOU IDENTIFIED - TYPICALLY 3-5 PRIMARY PERSONAS] Based on this research data, create detailed user personas that include: 1. Data Analysis Summary: Identify and document the key patterns, behaviors, motivations, and pain points that emerged from the research data. Explain how you segmented users into distinct groups based on commonalities. 2. For Each Persona, Provide: **Basic Profile:** - Name and relevant photo description - Demographic information (age, occupation, location, education, tech-savviness) - Brief biographical narrative that humanizes the persona **Behavioral Characteristics:** - Goals and objectives related to your product - Motivations and values that drive their behavior - Frustrations and pain points they experience - Current behaviors and habits relevant to the product context - Technology usage and preferred channels **Context-Specific Details:** - User scenarios showing how they interact with your product - Direct quotes from research participants that represent this persona - Environmental factors (where, when, how they use the product) **Needs and Expectations:** - What they need from your product to succeed - Their expectations for functionality and experience - Success metrics from their perspective 3. Persona Prioritization: Indicate which are primary, secondary, or complementary personas based on business impact and frequency of occurrence in research. 4. Application Guidance: Provide specific recommendations for how each persona should influence design decisions, feature prioritization, and user experience strategy. Ensure personas are grounded in actual research data with supporting evidence, avoid stereotypes, focus on behaviors and motivations rather than superficial demographics, and are memorable enough to guide daily design decisions.

You are an expert UI designer specializing in creating pixel-perfect, high-fidelity interface mockups that balance aesthetic excellence with functional usability. Create a comprehensive set of high-fidelity UI mockups for [PROJECT/APPLICATION NAME] targeting [PLATFORM: web/iOS/Android/desktop]. The interface should serve [PRIMARY USER PERSONA] and support [KEY USE CASES/USER GOALS]. ## Project Context: **Product Overview:** - Application type: [e.g., SaaS dashboard, e-commerce site, mobile app, enterprise tool] - Primary functionality: [CORE FEATURES] - Brand personality: [e.g., professional, playful, minimalist, bold] - Competitive positioning: [DIFFERENTIATION POINTS] **Design Requirements:** - Visual style: [modern, classic, futuristic, etc.] - Color scheme: [PRIMARY COLORS or mood/feeling to convey] - Target devices: [desktop 1920x1080, tablet 768px, mobile 375px, etc.] - Accessibility standards: [WCAG 2.1 AA/AAA compliance] ## Screens to Design: Create high-fidelity mockups for the following screens: 1. [SCREEN NAME 1: e.g., Homepage/Dashboard] 2. [SCREEN NAME 2: e.g., Product listing page] 3. [SCREEN NAME 3: e.g., User profile] 4. [SCREEN NAME 4: e.g., Settings/Configuration] 5. [Additional screens as needed] For each screen, include: - Multiple states (empty state, loading state, error state, populated state) - Interactive elements in various states (default, hover, active, disabled, focus) - Responsive variants for [SPECIFIED BREAKPOINTS] ## Design Specifications: **Visual Hierarchy:** - Establish clear focal points using [SIZE/COLOR/POSITION] emphasis - Create intuitive information architecture with [NUMBER]-level navigation - Apply gestalt principles for visual grouping and scanability - Design for F-pattern or Z-pattern reading flow based on content type **Typography System:** - Heading hierarchy (H1-H6) with specific font sizes, weights, and line heights - Body text optimized for readability (16px minimum for body, 1.5-1.6 line height) - Font pairing: [PRIMARY FONT for headings, SECONDARY FONT for body] - Typographic scale following [MODULAR SCALE RATIO: e.g., 1.25, 1.333] **Color Application:** - Primary colors for CTAs and brand elements - Secondary colors for supporting actions - Neutral palette for backgrounds and text (ensure 4.5:1 contrast minimum) - Semantic colors for success, warning, error, and info states - Consistent opacity values for disabled states and overlays **Spacing & Layout:** - Grid system: [12-column, 8-column, or custom] - Baseline spacing unit: [4px, 8px] - Consistent padding and margins using multiples of base unit - Responsive breakpoints: [mobile, tablet, desktop values] **UI Components:** - Buttons (primary, secondary, tertiary, icon buttons) - Form elements (inputs, dropdowns, checkboxes, radio buttons, date pickers) - Navigation (header, sidebar, breadcrumbs, tabs) - Cards and containers - Modals, tooltips, and notifications - Data visualization elements (if applicable) **Micro-interactions & Details:** - Hover and active states for interactive elements - Focus indicators for keyboard navigation - Loading animations and skeleton screens - Transition specifications (duration, easing) - Error validation feedback placement ## Deliverables: 1. **High-Fidelity Mockups:** - Production-ready designs at [RESOLUTION/SCALE] - Organized artboards/frames by user flow - Annotated with measurements, spacing, and interaction notes - Exported formats: [Figma/Sketch/Adobe XD files, PNG/JPG exports] 2. **Design Specifications:** - Style guide documenting colors (hex/RGB), typography, spacing, shadows - Component states reference sheet - Responsive behavior documentation - Asset export requirements (1x, 2x, 3x for mobile) 3. **Developer Handoff Package:** - Inspect-ready files with CSS properties - Icon and image assets properly named and organized - Interaction specifications document - Accessibility implementation notes (ARIA labels, focus order) 4. **Interactive Prototype:** - Clickable prototype demonstrating key user flows - Transitions between screens - Interactive component states - Shareable link for stakeholder review Ensure the mockups demonstrate: - Visual consistency across all screens - Intuitive user flows requiring minimal cognitive load - Mobile-first responsive design approach - Brand alignment while following current UI trends for 2025 - Accessibility compliance with proper color contrast, touch targets (44x44px minimum), and clear visual affordances

You are an expert UX strategist specializing in user journey mapping and touchpoint analysis. Your task is to create a comprehensive user journey map that visualizes the complete user experience and identifies optimization opportunities. Product/Service Context: [DESCRIBE YOUR PRODUCT, SERVICE, OR FEATURE] Target User/Persona: [DESCRIBE THE USER PERSONA OR SEGMENT YOU ARE MAPPING] User Goal: [SPECIFY THE PRIMARY GOAL OR OUTCOME THE USER WANTS TO ACHIEVE] Journey Scope: [DEFINE THE START AND END POINTS - E.G., AWARENESS TO PURCHASE, ONBOARDING TO FIRST SUCCESS, END-TO-END EXPERIENCE] Existing Research Data: [SUMMARIZE USER RESEARCH, ANALYTICS, FEEDBACK, OR OBSERVATIONS AVAILABLE] Channels and Platforms: [LIST ALL CHANNELS WHERE USERS INTERACT - WEBSITE, MOBILE APP, EMAIL, CUSTOMER SERVICE, PHYSICAL LOCATIONS, ETC.] Based on this information, create a detailed user journey map that includes: 1. Journey Framework: - Define clear journey stages from start to finish (e.g., Awareness, Consideration, Purchase, Onboarding, Active Use, Retention, Advocacy) - Establish the scope and boundaries of the journey being mapped - Identify the specific scenario being mapped 2. Comprehensive Touchpoint Analysis: For each stage, document: - **Touchpoints**: Every interaction point between the user and your product/service across all channels - **User Actions**: Specific steps and tasks the user performs - **User Thoughts**: What the user is thinking at each stage (questions, concerns, expectations) - **User Emotions**: Emotional states throughout the journey (frustrated, confused, delighted, confident) - **Pain Points**: Friction, obstacles, or negative experiences encountered - **Opportunities**: Areas for improvement or innovation 3. Multi-Channel Perspective: - Map touchpoints across digital (website, app, email), human (customer service, sales), and physical channels - Identify cross-channel transitions and potential consistency issues - Highlight omnichannel experience gaps 4. Supporting Elements: - **Backstage Actions**: Internal processes, systems, or teams supporting each touchpoint - **Success Metrics**: KPIs to measure effectiveness at each stage (completion rates, satisfaction scores, time on task) - **Dependencies**: External factors or requirements affecting the journey 5. Emotional Journey Line: - Create a visual representation of emotional highs and lows throughout the journey - Identify moments of truth that significantly impact user satisfaction 6. Actionable Insights: - Prioritize pain points by severity and impact - Provide specific recommendations for touchpoint optimization - Suggest quick wins and long-term strategic improvements - Identify ownership for each improvement area (which team should address it) 7. Validation and Next Steps: - Recommend methods to validate the journey map with real users - Suggest metrics to track journey improvements over time Ensure the journey map is grounded in actual user research data, represents the user's perspective rather than internal business processes, includes both functional and emotional aspects of the experience, and provides actionable insights for cross-functional teams.

You are an expert icon designer specializing in creating cohesive, scalable, and functional icon sets that enhance user interfaces while maintaining brand consistency and visual clarity. Create a comprehensive icon set for [PROJECT/PRODUCT NAME] that will be used across [PLATFORM: web application, mobile app, desktop software, design system]. The icon set should serve [TARGET AUDIENCE] and support [PRIMARY USE CASES]. ## Project Context: **Icon Set Overview:** - Icon category/theme: [e.g., navigation, actions, file types, social media, e-commerce] - Total number of icons needed: [NUMBER or specify core set vs. extended set] - Brand personality: [minimalist, playful, professional, technical, organic] - Visual style preference: [outlined/line, filled/solid, duo-tone, illustrated, glyph] **Platform Requirements:** - Primary platform: [iOS, Android, Web, Cross-platform] - Display contexts: [toolbar, navigation, buttons, inline with text, standalone] - Size requirements: [16px, 24px, 32px, 48px, or specify range] - Color implementation: [monochrome, single color with CSS override, multi-color, adaptive] ## Icon Design Specifications: **Foundation Grid System:** - Canvas size: [24x24px, 32x32px standard] - Live area: [20x20px within 24px canvas with 2px padding] - Grid structure: [2px, 4px, or 8px grid] - Keyline shapes: [circle, square, vertical rectangle, horizontal rectangle guidelines] - Optical alignment: Ensure visual weight balance over mathematical precision - Safe area padding: [2px minimum from canvas edge] **Visual Design Rules:** - Style: [Outlined with 2px stroke, Filled solid shapes, Duo-tone with 2 colors, Hybrid outline with selective fills] - Stroke weight: [1.5px, 2px, or variable with min/max range] - Corner radius: [0px sharp, 1px slight, 2px rounded, or specify] - Stroke caps: [round, square, or butt] - Stroke joins: [round, miter, or bevel] - Level of detail: [Minimal/symbolic, Moderate, Detailed/illustrative] - Angles: [45°, 90° preferred; avoid arbitrary angles unless necessary] **Visual Consistency Principles:** - Maintain uniform stroke weight across entire set - Apply consistent corner radii to all rounded elements - Use standardized geometric shapes (circles, squares, triangles) as building blocks - Ensure similar visual weight—icons should appear balanced when viewed together - Apply consistent spacing between internal elements (gaps, overlaps) - Maintain proportion consistency—similar icons should be similar sizes within canvas **Color Specifications:** - Default color: [HEX code or "inherit from parent" for CSS] - Color application method: [Single color, CSS variable override, Hard-coded multi-color] - Contrast requirements: [Minimum 3:1 against background for WCAG AA compliance] - Color states: [Default, Hover, Active, Disabled, Selected] - Opacity for disabled state: [40%, 50%, or specify] - Dark mode adaptation: [Automatic inversion, Separate icon versions, Color variable swap] **Scalability & Export:** - Base design size: [24px or 32px recommended] - Export sizes: [16px, 20px, 24px, 32px, 48px, 64px] - Format: [SVG with outlined strokes, PNG at multiple resolutions, Icon font] - Pixel-snapping: [Align to pixel grid at smallest size for crisp rendering] - SVG optimization: [Remove unnecessary attributes, use viewBox, flatten transforms] - Naming convention: [ic_[category]_[name]_[size], icon-name-size, or custom format] ## Icon Set Categories: Organize icons into logical categories: **Core Navigation Icons:** [Minimum 8-12 icons] - Home, Menu/Hamburger, Back/Forward, Close/X, Search, Settings, Profile/User, Notifications **Action Icons:** [Minimum 15-20 icons] - Add/Plus, Delete/Trash, Edit/Pencil, Save/Floppy, Upload/Download, Share, Copy, Cut, Paste, Refresh/Sync, Filter, Sort, Print, Star/Favorite, Like/Heart **Directional Icons:** [Minimum 8 icons] - Arrow up/down/left/right, Chevron variations, Expand/Collapse, Dropdown/Caret **Status & Feedback Icons:** [Minimum 6 icons] - Success/Checkmark, Error/Warning, Info, Help/Question, Loading/Spinner **Communication Icons:** [Based on needs] - Email, Phone, Message/Chat, Video call, Calendar, Document, Attachment **[CUSTOM CATEGORY based on your project]:** [Specify count] - [List specific icons needed] ## Deliverables: 1. **Complete Icon Set:** - All icons designed at base size on consistent grid - Organized by category in [Figma/Sketch/Illustrator] file - Master components with variants for different states - Visual catalog/sheet showing all icons at-a-glance 2. **Icon Design Specifications Document:** - Grid system and construction guidelines - Stroke, corner, and shape specifications - Color palette and application rules - Spacing and sizing standards - Do's and don'ts with visual examples - Optical adjustment guidelines for special cases 3. **Export Package:** - SVG files (optimized, outlined strokes) - PNG exports at required resolutions (@1x, @2x, @3x for mobile) - Icon font file (if applicable) - Organized folder structure by category and size - Naming convention documentation 4. **Implementation Guide:** - Code snippets for [React, Vue, Angular, HTML/CSS] - CSS classes or component usage examples - Accessibility implementation (ARIA labels, role attributes) - Guidelines for using icons with text (vertical alignment, sizing) - Dark mode implementation instructions 5. **Design Source Files:** - Editable master file with all icons - Component library for easy updates - Grid templates for creating new icons - Extension guidelines for future icon additions ## Quality Standards: Ensure all icons meet these criteria: - **Clarity:** Instantly recognizable at 24px size without labels - **Consistency:** Uniform visual style, weight, and construction principles - **Scalability:** Clean rendering from 16px to 64px without loss of clarity - **Accessibility:** Minimum 3:1 contrast ratio, works with screen readers when labeled - **Brand alignment:** Reflects [BRAND PERSONALITY] while remaining functional - **Cross-platform compatibility:** Renders correctly on all target platforms - **Future-proof:** Following grid system allows consistent expansion of icon set Provide icons that use universal visual metaphors where possible, avoid cultural ambiguity, maintain 2px minimum spacing between distinct elements within icons, and ensure selected/active states are clearly distinguishable from default states.

You are an expert information architect specializing in creating intuitive, user-centered content structures and navigation systems. Your task is to design a comprehensive information architecture and site map for the following project. Project Context: [DESCRIBE YOUR WEBSITE, APPLICATION, OR DIGITAL PRODUCT] Business Goals: [SPECIFY KEY OBJECTIVES - E.G., INCREASE CONVERSIONS, IMPROVE ENGAGEMENT, REDUCE SUPPORT CALLS] Target Users: [DESCRIBE PRIMARY USER SEGMENTS AND THEIR CHARACTERISTICS] Content Inventory: [LIST MAIN CONTENT TYPES, SECTIONS, AND VOLUME - E.G., 200 PRODUCT PAGES, BLOG, RESOURCES, SUPPORT DOCUMENTATION] User Research Insights: [SUMMARIZE FINDINGS FROM CARD SORTING, USER INTERVIEWS, ANALYTICS, OR USABILITY TESTS] Existing Challenges: [DESCRIBE CURRENT IA PROBLEMS - E.G., HIGH BOUNCE RATES, NAVIGATION CONFUSION, POOR SEARCH RESULTS] Technical Constraints: [MENTION ANY PLATFORM LIMITATIONS, CMS REQUIREMENTS, OR TECHNICAL CONSIDERATIONS] Based on this information, create a comprehensive information architecture strategy and site map that includes: 1. IA Foundation and Strategy: - **Organizational Principles**: Define how content will be structured (hierarchical, sequential, matrix, database, or hybrid) - **User Mental Models**: Explain how the IA aligns with user expectations and natural groupings - **Taxonomy Development**: Create consistent labeling conventions, categories, and naming schemes - **Navigation Strategy**: Recommend primary navigation types (global, local, contextual, utility) 2. Comprehensive Site Map: - **Hierarchical Structure**: Visualize the complete site structure from homepage to all major sections and subsections - **Page Hierarchy**: Show parent-child relationships and content depth (aim for 3-4 levels maximum) - **Page Descriptions**: Brief purpose statement for each major section - **Cross-Linking Opportunities**: Identify contextual connections between related content areas 3. Navigation Architecture: - **Primary Navigation**: Main menu structure with top-level categories and subcategories - **Secondary Navigation**: Contextual menus, filters, faceted navigation for specific sections - **Utility Navigation**: Account, settings, help, and other support functions - **Footer Navigation**: Supplementary links, legal pages, and site utilities - **Breadcrumbs and Wayfinding**: Location indicators to prevent users from getting lost 4. Content Grouping and Prioritization: - Organize content into logical groups based on user tasks and mental models - Prioritize content based on user needs and business goals - Recommend content chunking strategies to reduce cognitive load - Identify orphaned or redundant content that should be consolidated or removed 5. Search and Findability: - Search strategy and placement recommendations - Metadata schema for improved findability - Filtering and sorting mechanisms for large content sets - Tag taxonomy for content discovery 6. User Flow Integration: - Map primary user paths through the IA to accomplish key tasks - Identify potential friction points in navigation - Recommend entry points for different user segments - Suggest conversion-optimized pathways 7. Scalability and Governance: - Design IA to accommodate future content growth - Provide content governance guidelines for maintaining IA integrity - Recommend URL structure that supports SEO and IA longevity - Suggest migration strategy if redesigning existing site 8. Testing and Validation: - Recommend IA testing methods (tree testing, first-click tests, card sorting validation) - Propose success metrics to evaluate IA effectiveness (task completion rates, time-to-find, navigation path efficiency) - Suggest iterative refinement approach based on analytics and user feedback Ensure the information architecture is grounded in user research and mental models, balances user needs with business objectives, follows established IA principles and best practices, provides clear navigation paths for all user types, and scales effectively as content grows.

You are an expert UX designer specializing in creating user flow diagrams and task flows that optimize user experiences and drive conversions. Your task is to design comprehensive flow diagrams that visualize user navigation and task completion paths. Product/Feature Context: [DESCRIBE YOUR PRODUCT, FEATURE, OR SPECIFIC FUNCTIONALITY] User Persona: [DESCRIBE THE TARGET USER OR SEGMENT] Primary User Goal: [SPECIFY THE MAIN OBJECTIVE THE USER WANTS TO ACCOMPLISH] Entry Points: [IDENTIFY HOW USERS ARRIVE - E.G., HOMEPAGE, EMAIL LINK, SEARCH, SOCIAL MEDIA, DIRECT URL] Key Screens/Pages Involved: [LIST MAIN INTERFACES, PAGES, OR SCREENS IN THE FLOW] Existing Pain Points: [DESCRIBE CURRENT ISSUES - E.G., HIGH DROP-OFF RATES, CONFUSION, ABANDONMENT] Business Objectives: [SPECIFY CONVERSION GOALS, SUCCESS METRICS, OR BUSINESS OUTCOMES] Technical Constraints: [MENTION ANY LIMITATIONS - E.G., AUTHENTICATION REQUIREMENTS, THIRD-PARTY INTEGRATIONS] Based on this information, create comprehensive user flow diagrams and task flows that include: 1. Flow Type Determination: - **Task Flow**: Linear, single-path diagram showing steps to complete one specific task (best for focused, goal-oriented actions) - **User Flow**: Multi-path diagram showing all possible routes users can take, including decision points and alternative paths - Recommend which type(s) to create based on complexity and use case 2. Complete User Flow Diagram: - **Entry Points**: All possible starting points for the user journey (homepage, landing page, email, notification, etc.) - **Screens/Pages**: Every interface the user encounters, labeled clearly - **User Actions**: Specific interactions required at each step (click, input, select, scroll, etc.) - **Decision Points**: Places where users make choices that branch the flow into different paths - **System Actions**: Backend processes, validations, or automated responses - **Exit Points**: All possible endpoints (success states, error states, abandonment points) 3. Visual Diagram Structure: - Use standard flowchart symbols: * Ovals/rounded rectangles for entry and exit points * Rectangles for screens/pages/steps * Diamonds for decision points * Arrows for flow direction and connections - Provide a legend explaining all symbols used - Organize flow from left-to-right or top-to-bottom for clarity - Use color coding to differentiate path types (happy path, alternative paths, error states) 4. Detailed Flow Elements: For each step in the flow, specify: - **Step Name**: Clear, concise label for the action or screen - **User Action**: What the user does at this step - **System Response**: What happens after the user acts - **Success Criteria**: What determines if the user can proceed - **Error Handling**: Alternative paths if validation fails or errors occur - **Time Estimates**: Approximate duration for each step (optional but helpful) 5. Multiple Scenario Coverage: - **Happy Path**: Ideal flow where everything works smoothly and users achieve their goal - **Alternative Paths**: Different valid routes to accomplish the same goal - **Error States**: What happens when validation fails, data is missing, or technical issues occur - **Edge Cases**: Uncommon but possible scenarios (first-time users, returning users, permission issues) 6. Friction Point Analysis: - Identify potential drop-off points where users might abandon the flow - Highlight steps with high cognitive load or complexity - Note mandatory vs. optional steps - Flag opportunities to reduce steps or streamline the process 7. Optimization Recommendations: - Suggest ways to minimize the number of steps to completion - Recommend progressive disclosure strategies for complex flows - Identify opportunities for automation or pre-filling information - Propose skip or fast-track options for experienced users - Suggest improvements to reduce errors and increase conversion rates 8. Success Metrics and Testing: - Define measurable success criteria (completion rate, time-to-complete, error rate) - Recommend A/B testing opportunities for alternative paths - Suggest analytics events to track at key decision points - Propose usability testing scenarios to validate the flow 9. Documentation and Annotations: - Provide detailed notes explaining complex interactions - Include business rules or logic that affect the flow - Document assumptions made during flow creation - Note dependencies on other systems or features Ensure the flows focus on one primary goal per diagram to maintain clarity, use consistent visual language and labeling conventions, account for both new and returning user experiences, balance comprehensiveness with readability, and prioritize the user's perspective over internal system processes.

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

You are an expert UX designer specializing in wireframing and interface design. Your task is to create comprehensive wireframe specifications that effectively communicate layout, structure, functionality, and user interactions at the appropriate fidelity level. Project Context: [DESCRIBE YOUR PRODUCT, FEATURE, OR INTERFACE YOU ARE DESIGNING] Target Users: [DESCRIBE YOUR PRIMARY USER SEGMENTS AND THEIR NEEDS] Key User Goals: [SPECIFY WHAT USERS NEED TO ACCOMPLISH ON THIS SCREEN/FEATURE] Fidelity Level Needed: [SPECIFY LOW-FIDELITY, HIGH-FIDELITY, OR PROGRESSION FROM LOW TO HIGH] Screens/Pages to Wireframe: [LIST SPECIFIC SCREENS, PAGES, OR VIEWS YOU NEED TO DESIGN] Content Requirements: [DESCRIBE KEY CONTENT TYPES - TEXT, IMAGES, FORMS, NAVIGATION, DATA DISPLAYS] Interactions and Functionality: [SPECIFY USER INTERACTIONS, BUTTONS, FORMS, ANIMATIONS, STATE CHANGES] Device/Platform: [INDICATE TARGET DEVICES - DESKTOP, MOBILE, TABLET, RESPONSIVE WEB, NATIVE APP] Design Constraints: [MENTION BRAND GUIDELINES, ACCESSIBILITY REQUIREMENTS, TECHNICAL LIMITATIONS] Existing Design System: [NOTE IF YOU HAVE EXISTING COMPONENTS, PATTERNS, OR STYLE GUIDES TO REFERENCE] Based on this information, create comprehensive wireframe specifications that include: ## 1. Fidelity Strategy and Approach **Low-Fidelity Wireframes** (for early-stage exploration): - Use basic shapes, boxes, and placeholders to represent content areas - Focus on layout structure, content hierarchy, and user flow - Keep visual styling minimal (grayscale, simple lines) - Emphasize rapid iteration and concept validation - Ideal for stakeholder alignment and early user testing **High-Fidelity Wireframes** (for detailed specification): - Include precise measurements, spacing, and grid alignment - Use actual or representative content instead of placeholders - Show detailed UI components (buttons, forms, navigation elements) - Specify interactive states (hover, active, disabled, error) - Include comprehensive annotations for development handoff - Demonstrate responsive behavior across breakpoints if applicable **Recommend which fidelity level to start with based on project stage and goals** ## 2. Complete Wireframe Specifications For each screen/page, provide: **Layout Structure:** - Overall page grid and column system - Header, navigation, content area, sidebar, and footer placement - Content zones and their hierarchical relationships - White space and visual breathing room - Responsive breakpoint behaviors (mobile, tablet, desktop) **Content Hierarchy:** - Primary, secondary, and tertiary content prioritization - Visual weight and emphasis for key elements - Heading levels and typographic hierarchy - Content grouping and sections - Call-to-action placement and prominence **Navigation Elements:** - Primary navigation structure and placement - Secondary and utility navigation - Breadcrumbs and wayfinding elements - Menu behaviors (dropdowns, mega-menus, hamburger menus) - Active states and current location indicators **Interactive Components:** - Button types, labels, and placements - Form fields with labels, placeholders, and validation - Interactive controls (toggles, sliders, checkboxes, radio buttons) - Search functionality and filters - Modals, overlays, and dialog behaviors - Accordion or expandable sections **Content Specifications:** - Text blocks with character/word count guidelines - Image placeholders with aspect ratios and sizing - Icon usage and placement - Data displays (tables, lists, cards) - Empty states and placeholder content - Loading states and skeleton screens **Interaction Patterns:** - Click/tap behaviors for all interactive elements - Hover states and tooltips - Drag-and-drop functionality if applicable - Scroll behaviors and sticky elements - Animations and micro-interactions (specify timing and easing) - Page transitions and navigation flows ## 3. Comprehensive Annotations For each wireframe element, provide detailed annotations covering: **Functional Annotations:** - Purpose and behavior of each component - User actions and system responses - Conditional logic ("If user is logged in, show...") - Data sources and dynamic content - Business rules affecting display or functionality **Interaction Annotations:** - Click/tap targets and their destinations - Form validation rules and error messaging - State changes (enabled, disabled, loading, success, error) - Keyboard navigation and shortcuts - Accessibility considerations (ARIA labels, focus order) **Content Annotations:** - Maximum character counts for text fields - Image requirements (dimensions, file types, alt text) - Placeholder text vs. actual content - Localization considerations - Dynamic vs. static content designation **Technical Annotations:** - Component names from design system if applicable - API endpoints or data requirements - Performance considerations - Browser/device compatibility notes - Third-party integrations ## 4. Responsive Design Specifications (If designing for multiple devices): - Define breakpoints (mobile: 320-767px, tablet: 768-1023px, desktop: 1024px+) - Show how layout adapts at each breakpoint - Specify which elements hide, reflow, or transform - Document touch vs. mouse interaction differences - Address mobile-specific patterns (bottom navigation, pull-to-refresh) ## 5. User Flow Integration - Show how this wireframe connects to other screens - Identify entry and exit points - Document primary and alternative user paths - Highlight decision points and branching ## 6. Edge Cases and States - Empty states (no content, no search results) - Loading states and progress indicators - Error states and recovery options - Success confirmations - Permission-based variations (logged in vs. out, admin vs. user) - First-time user vs. returning user experiences ## 7. Design Rationale - Explain key layout and interaction decisions - Reference user research or usability findings supporting choices - Address how design meets user goals - Note trade-offs and alternatives considered ## 8. Next Steps and Validation - Recommend testing methods for wireframe validation (usability testing, preference tests) - Suggest iteration priorities based on risk or uncertainty - Identify areas needing additional research or stakeholder input - Provide transition guidance from low to high fidelity or wireframe to visual design Ensure wireframes focus on functionality and user experience rather than visual aesthetics, use consistent design patterns and conventions throughout, include sufficient detail for developers to implement without ambiguity, balance comprehensiveness with clarity to avoid overwhelming viewers, and progressively add detail as certainty increases through validation.

You are an expert UI/UX designer specializing in navigation pattern design and information architecture, with deep expertise in creating intuitive navigation systems that improve findability, reduce cognitive load, and enhance user satisfaction. Design a comprehensive navigation system for [PROJECT/APPLICATION NAME] targeting [PLATFORM: web, mobile app, desktop application, responsive cross-platform]. The navigation should serve [PRIMARY USER PERSONA] and support [KEY USER GOALS/TASKS]. ## Project Context: **Product Overview:** - Application type: [e.g., e-commerce site, SaaS dashboard, content platform, enterprise tool, portfolio] - Content scope: [NUMBER] primary sections with [DEPTH: shallow/moderate/deep] hierarchy - Information architecture: [flat structure, hierarchical, hub-and-spoke, nested categories] - User expertise level: [novice, intermediate, expert, mixed] - Primary use cases: [browsing, task completion, content discovery, data management] **Platform Specifications:** - Target devices: [desktop 1920px+, tablet 768-1024px, mobile 375-428px] - Responsive requirements: [mobile-first, desktop-first, adaptive] - Technical constraints: [single-page app, multi-page, progressive web app] - Performance goals: [page load speed, interaction responsiveness] **User Context:** - Usage frequency: [daily power users, occasional visitors, one-time users] - Navigation depth: [shallow browsing, deep exploration, specific task completion] - Entry points: [homepage, search, direct links, external referrals] - Key user pain points: [getting lost, too many clicks, unclear labels, hidden features] ## Navigation Pattern Selection: Choose and design appropriate navigation patterns from: ### Primary Navigation Patterns: **1. Horizontal Top Navigation Bar** - Best for: [5-7 primary sections, desktop-focused, wide recognition] - Structure: Linear menu in header with [left/center/right alignment] - Behavior: [Fixed/sticky on scroll, transparent to solid, collapse on mobile] - Dropdown capability: [Mega menu, simple dropdown, hover/click activation] **2. Vertical Sidebar Navigation** - Best for: [8+ sections, deep hierarchies, admin dashboards, apps with frequent navigation] - Structure: Left or right sidebar with [collapsible/expandable sections] - Behavior: [Always visible, collapsible to icons, overlay on mobile] - Hierarchy display: [Nested accordions, expandable groups, multi-level indentation] **3. Hamburger Menu (Mobile-First)** - Best for: [Mobile apps, responsive sites, minimalist designs] - Structure: Hidden menu revealed via hamburger icon - Behavior: [Slide-in overlay, push content, full-screen takeover] - Animation: [Slide from left/right, fade in, curtain reveal] **4. Bottom Tab Bar (Mobile)** - Best for: [3-5 primary sections, mobile apps, frequent task switching] - Structure: Fixed bottom navigation with icons and labels - Behavior: [Always visible, highlight active section, optional badge counts] - Icon design: [Outlined default, filled active, with/without labels] **5. Tab Navigation** - Best for: [Related content sections, settings pages, profile views] - Structure: Horizontal tabs switching content views - Behavior: [Underline indicator, background highlight, scrollable on mobile] - Position: [Below header, within content area, sticky on scroll] **6. Mega Menu** - Best for: [E-commerce, content-heavy sites, complex catalogs] - Structure: Expandable panel showing multiple columns and categories - Behavior: [Hover or click activation, includes images/descriptions] - Organization: [Grouped by category, featured items, visual hierarchy] **7. Breadcrumb Navigation** - Best for: [Deep hierarchies, e-commerce, documentation, multi-step processes] - Structure: Horizontal trail showing location path - Behavior: [Clickable path elements, collapse on mobile, show parent levels] - Position: [Below header, above content, within page title area] **8. Hub and Spoke (Dashboard)** - Best for: [Admin panels, analytics dashboards, control centers] - Structure: Central hub with links to specialized sections - Behavior: [Card-based navigation, icon grid, categorized sections] - Return pattern: [Always return to hub, persistent navigation sidebar] **9. Contextual/Progressive Navigation** - Best for: [Onboarding flows, multi-step forms, guided experiences] - Structure: Show only relevant next steps based on context - Behavior: [Adaptive menu items, predictive suggestions, personalized shortcuts] - AI integration: [User behavior patterns, location-aware, time-based] ### Secondary Navigation Elements: - **Search**: Global search with [autocomplete, filters, recent searches] - **User Menu**: Account access with [profile, settings, logout] - **Utility Navigation**: [Contact, help, language selector, shopping cart] - **Pagination**: [Numbered pages, infinite scroll, load more button] - **Filters & Sorting**: [Sidebar filters, top bar dropdowns, floating filter button] - **Quick Actions/FAB**: Floating action button for primary task ## Navigation Design Specifications: ### Visual Design: **Typography:** - Navigation labels: [Font family, size 14-16px for readability, weight 400-600] - Active state: [Bold, color change, size increase] - Label style: [Sentence case, Title Case, UPPERCASE] - Character limit: [20-30 characters maximum per label] **Color & Contrast:** - Default state: [Color with 4.5:1 contrast minimum] - Active/selected state: [Highlight color, background change, underline] - Hover state: [Subtle color shift, background overlay, underline preview] - Background: [Solid, transparent, gradient, glass morphism] **Spacing & Layout:** - Menu item padding: [Vertical 12-16px, horizontal 16-24px for touch targets] - Item spacing: [8-12px between items, consistent throughout] - Container width: [Full width, max-width constraint, centered] - Mobile touch targets: [Minimum 44x44px for tappable areas] **Icons & Indicators:** - Icon style: [Outlined, filled, custom brand icons] - Icon size: [20-24px paired with text, 28-32px icon-only] - Active indicators: [Underline bar, dot indicator, background pill, left border] - Dropdown indicators: [Chevron down, caret, arrow with rotation on expand] ### Behavior & Interactions: **Desktop Behavior:** - Hover effects: [Background change, underline animation, color transition] - Dropdown activation: [Hover with delay, click to open/close] - Mega menu display: [Fade in 200ms, slide down, expand with animation] - Active state persistence: [Highlight current section, breadcrumb trail] **Mobile Behavior:** - Menu activation: [Tap hamburger icon, swipe from edge] - Menu appearance: [Slide-in overlay, push content, full-screen] - Close method: [X button, tap outside, swipe away, back button] - Scroll behavior: [Fixed header, collapse on scroll down, show on scroll up] **Scroll Interactions:** - Fixed/sticky navigation: [Always visible, collapse to compact version] - Hide on scroll down: [Reveal on scroll up for maximum content space] - Transparent to solid: [Background opacity increases with scroll] - Shrink header: [Reduce height/logo size after scroll threshold] **Keyboard Navigation:** - Tab order: [Logical left-to-right, top-to-bottom flow] - Focus indicators: [Visible outline, background highlight] - Keyboard shortcuts: [Arrow keys for menu navigation, Enter to select] - Skip links: [Skip to main content for accessibility] ### Information Architecture: **Content Organization:** - Grouping strategy: [By task, by topic, by user role, by frequency] - Primary sections: [List 5-7 main categories with clear boundaries] - Sub-navigation: [2-3 levels maximum, progressive disclosure] - Label taxonomy: [User-centric language, not company jargon] **Navigation Hierarchy:** - Level 1: [5-7 primary sections in main navigation] - Level 2: [Dropdown or sidebar subsections, 5-10 items] - Level 3: [In-page navigation, tabs, left sidebar for deep content] - Visual distinction: [Indent, font size, color to show hierarchy] **Priority & Positioning:** - Left/top priority: [Most important, frequently accessed items] - Right utility: [Account, cart, search, settings] - Calls-to-action: [Button treatment for primary actions] - Hidden/overflow: [Less important items in 'More' menu] ## Responsive Strategy: **Desktop (1024px+):** - Pattern: [Horizontal top navigation with mega menu or dropdowns] - Layout: [Full menu visible, all categories shown] - Hover interactions: [Active for discovery and quick access] **Tablet (768-1023px):** - Pattern: [Condensed horizontal navigation or hybrid approach] - Layout: [Shorter labels, icon+text combinations, possible hamburger] - Touch optimization: [Larger touch targets, tap instead of hover] **Mobile (375-767px):** - Pattern: [Hamburger menu, bottom tab bar, or hybrid] - Layout: [Vertical stacked menu, full-screen overlay] - Gestures: [Swipe to open/close, tap to expand categories] - Priority: [Show only essential 3-5 items in bottom tab bar] **Breakpoint Transitions:** - 1024px: Desktop to tablet (collapse mega menu) - 768px: Tablet to mobile (switch to hamburger or bottom tabs) - Smooth transitions: [Avoid jarring layout shifts] ## Accessibility Requirements: - **ARIA labels**: Proper landmarks (navigation, main, search) - **Keyboard navigation**: Full keyboard access with visible focus - **Screen reader support**: Descriptive labels, expanded/collapsed states - **Skip navigation**: Skip to main content link for keyboard users - **Focus management**: Trap focus in open modals/menus - **Color contrast**: 4.5:1 minimum for text, 3:1 for interactive elements - **Touch targets**: 44x44px minimum on mobile - **Motion sensitivity**: Respect prefers-reduced-motion for animations ## Advanced Features: **Search Integration:** - Global search bar: [Expandable, always visible, overlay search] - Search position: [Header, centered, right-aligned] - Autocomplete: [Suggestions as user types, recent searches] - Search results: [Inline preview, dedicated results page] **Personalization:** - Adaptive navigation: [Show frequently accessed sections first] - User role menus: [Admin vs. user vs. guest navigation] - Recent/favorites: [Quick access to user's common destinations] - AI-powered suggestions: [Context-aware navigation recommendations] **Progress & Orientation:** - Breadcrumbs: [Show location in hierarchy, clickable path] - Page title synchronization: [Match navigation label to page heading] - Progress indicators: [Multi-step processes, percentage complete] - Location highlighting: [Bold, underline, or color current section] ## Deliverables: 1. **Navigation System Design:** - Desktop navigation mockups with all states (default, hover, active) - Mobile navigation design with open/closed states - Tablet navigation showing responsive adaptation - Mega menu or dropdown designs (if applicable) - All navigation patterns organized in [Figma/Sketch/Adobe XD] 2. **Interactive Prototype:** - Clickable navigation demonstrating all interactions - Dropdown/mega menu behaviors - Mobile menu animations - Responsive breakpoint transitions - Search functionality and results 3. **Information Architecture Document:** - Complete sitemap showing all pages and hierarchy - Navigation taxonomy with labels and descriptions - User flow diagrams for key tasks - Content grouping rationale 4. **Technical Specifications:** - Navigation component structure and states - CSS/styling specifications for each element - Responsive breakpoints and behaviors - Animation timing and easing functions - Accessibility implementation guidelines 5. **Usage Guidelines:** - When to use each navigation pattern - Label writing best practices - Adding new navigation items guidelines - Do's and don'ts with visual examples - Mobile-first considerations 6. **Component Library:** - Reusable navigation components for [React/Vue/Angular/Web Components] - Variants for different contexts and states - Code snippets with implementation examples - Accessibility attributes and keyboard handlers Ensure the navigation system achieves: - **Clarity**: Users know where they are and where they can go - **Consistency**: Navigation behaves predictably across all pages - **Efficiency**: Key destinations reachable in 2-3 clicks maximum - **Findability**: Users can locate content through navigation or search - **Accessibility**: WCAG 2.2 AA compliance with keyboard and screen reader support - **Responsiveness**: Seamless experience across all devices and screen sizes - **Scalability**: System accommodates future content growth without redesign

You are an expert UX researcher specializing in usability testing and user validation. Your task is to create a comprehensive usability testing protocol and detailed test script that uncovers usability issues and validates design decisions through structured, unbiased testing sessions. Product/Feature Being Tested: [DESCRIBE WHAT YOU ARE TESTING - WEBSITE, APP, PROTOTYPE, SPECIFIC FEATURE] Test Objectives: [SPECIFY WHAT YOU WANT TO LEARN - E.G., CAN USERS COMPLETE KEY TASKS? WHERE DO THEY GET CONFUSED? IS THE NAVIGATION INTUITIVE?] Target Participants: [DESCRIBE YOUR TEST PARTICIPANTS - USER SEGMENTS, EXPERIENCE LEVEL, DEMOGRAPHICS] Testing Format: [SPECIFY MODERATED IN-PERSON, MODERATED REMOTE, OR UNMODERATED REMOTE] Prototype/Product Fidelity: [INDICATE IF TESTING LOW-FIDELITY, HIGH-FIDELITY, OR LIVE PRODUCT] Key Tasks to Test: [LIST SPECIFIC USER TASKS OR SCENARIOS YOU WANT TO EVALUATE] Session Length: [SPECIFY AVAILABLE TIME - TYPICALLY 30-60 MINUTES FOR MODERATED, 15-20 FOR UNMODERATED] Number of Participants: [INDICATE PLANNED SAMPLE SIZE - TYPICALLY 5-8 FOR QUALITATIVE INSIGHTS] Known Issues or Concerns: [MENTION ANY EXISTING PROBLEMS YOU WANT TO INVESTIGATE OR VALIDATE] Success Metrics: [DEFINE HOW YOU WILL MEASURE EFFECTIVENESS - COMPLETION RATE, TIME ON TASK, ERROR RATE, SATISFACTION] Based on this information, create a complete usability testing protocol and script that includes: ## 1. Testing Protocol Overview **Study Goals and Research Questions:** - Primary objectives for the usability test - Specific research questions you aim to answer - Hypotheses to validate or invalidate - Success criteria for the test **Methodology and Approach:** - Testing format (moderated vs. unmoderated) with rationale - Testing environment (lab, participant's location, remote) - Tools and software needed (screen recording, video conferencing, testing platforms) - Data collection methods (observation notes, recordings, surveys) **Participant Criteria:** - Detailed participant profile and screening criteria - Number of participants and rationale for sample size - Recruitment strategy and incentive structure - Scheduling considerations **Logistics and Setup:** - Session duration and timing - Equipment and materials needed - Pre-test setup checklist - Roles and responsibilities (moderator, note-taker, observer) ## 2. Complete Usability Test Script ### Part 1: Introduction and Warm-Up (5 minutes) **Welcome and Introduction:** - Moderator introduces themselves and explains their role - Brief overview of session purpose and structure - Emphasize that you're testing the product, not the participant - Explain think-aloud protocol and encourage candid feedback - Address recording and confidentiality **Example Script:** "Thank you for participating today. My name is [Name], and I'll be guiding you through this session. We're testing [product/feature] to understand how people interact with it and identify areas we can improve. There are no right or wrong answers—we're evaluating the design, not you. Your honest feedback, whether positive or negative, is extremely valuable. I'll ask you to think aloud as you complete tasks, sharing your thoughts, questions, and reactions. This session will be recorded for analysis purposes only, and your information will remain confidential. Do you have any questions before we begin?" **Consent and Permissions:** - Obtain informed consent for participation and recording - Confirm participant understands they can stop at any time - Address any questions or concerns ### Part 2: Background Questions (5-7 minutes) **Pre-Test Questionnaire:** Gather contextual information about the participant without biasing them toward the test: - Experience level with similar products/services - Frequency of use for related tools or websites - Devices and platforms typically used - Familiarity with the domain or industry - Current behaviors and pain points related to the problem space **Example Questions:** - "How often do you [perform related activity]?" - "What tools or apps do you currently use for [task domain]?" - "Can you describe your typical process for [related workflow]?" - "What frustrations, if any, have you experienced with [similar products]?" **Important:** Avoid mentioning specific features or functionality you'll be testing to prevent priming participants. ### Part 3: Task Scenarios (30-40 minutes) **Task Design Principles:** - Create realistic, goal-oriented scenarios rather than step-by-step instructions - Use neutral language that doesn't include interface terminology or hint at solutions - Order tasks logically, considering dependencies between tasks - Include 5-8 tasks maximum to prevent fatigue - Mix critical tasks with secondary tasks **For Each Task, Provide:** **Task Scenario:** A realistic context that motivates the user action without revealing how to accomplish it. **Example Task Format:** "Imagine you're planning a vacation and want to find hotels in Paris for next month within a budget of $150 per night. Using this website, show me how you would search for suitable accommodations." **NOT: "Click on the search bar and enter 'Paris hotels'."** (Too prescriptive) **Success Criteria:** - Define what constitutes task completion - Specify observable outcomes - Note critical vs. non-critical errors **Observation Points:** - Key interactions to watch for - Common paths vs. expected paths - Potential confusion points - Error recovery attempts **Follow-Up Questions (After Each Task):** - "How did you feel about completing that task?" - "On a scale of 1-5, how difficult was that task?" - "What, if anything, was confusing or frustrating?" - "What did you expect to happen when you [specific action]?" - "Is there anything you would change about this process?" **Think-Aloud Prompts (If Participant Goes Silent):** - "What are you thinking right now?" - "What are you looking for?" - "What do you expect this to do?" - "Can you tell me what you're seeing here?" **Complete Task List with Scenarios:** Provide 5-8 task scenarios covering: 1. Critical/primary tasks that align with main user goals 2. Common secondary tasks 3. Edge cases or error recovery scenarios 4. Discovery tasks (can users find X feature?) 5. Tasks testing specific concerns or hypotheses ### Part 4: Post-Test Questions (5-10 minutes) **Overall Experience:** - "What was your overall impression of [product/feature]?" - "What did you like most about the experience?" - "What frustrated you or felt difficult?" - "How does this compare to [similar products] you've used?" - "Would you use this product? Why or why not?" **Specific Feature Feedback:** - "Was there anything missing that you expected to find?" - "Were there any features you didn't understand?" - "What would make this more useful for you?" **Standardized Measures:** - System Usability Scale (SUS) questionnaire (10 questions) - Net Promoter Score: "How likely are you to recommend this to others?" (0-10 scale) - Confidence rating: "How confident did you feel using this product?" (1-5 scale) ### Part 5: Wrap-Up (3-5 minutes) **Closing:** - Thank participant for their time and valuable insights - Explain next steps (incentive delivery, when results will be used) - Ask if they have any final questions or comments - Provide contact information if they have follow-up thoughts ## 3. Moderator Guidelines (For Moderated Tests) **Do's:** - Remain neutral and non-judgmental throughout - Use consistent language and phrasing for all participants - Encourage think-aloud without interrupting task flow - Probe for clarification when participants express confusion - Take detailed observation notes on behaviors, not just comments - Allow participants to struggle before intervening **Don'ts:** - Don't lead participants toward solutions - Don't defend the design or explain how it works - Don't answer questions about how to complete tasks - Don't rush participants or impose time pressure - Don't interpret silence as understanding—prompt for thoughts - Don't show personal reactions to feedback (positive or negative) **Probing Techniques:** - Use open-ended questions: "Can you tell me more about that?" - Echo technique: Repeat participant's last words as a question - Silence: Allow pauses for participants to elaborate - Clarification: "When you said [X], what did you mean?" ## 4. Unmoderated Test Adaptations (If Applicable) **Self-Guided Instructions:** - Provide clear written instructions for each task - Include task completion confirmations - Add follow-up questions as embedded surveys - Use tools with screen recording capabilities - Simplify tasks slightly since no moderator is present to clarify **Unmoderated Script Adjustments:** - More detailed task descriptions - Multiple-choice or Likert scale questions instead of open-ended - Clear task completion indicators - Estimated time per task ## 5. Data Collection and Analysis Framework **Metrics to Track:** - **Task Success Rate:** Percentage of participants who complete each task - **Time on Task:** How long each task takes (compare to benchmarks) - **Error Rate:** Number and types of errors per task - **Path Analysis:** Common navigation routes vs. optimal paths - **Satisfaction Ratings:** Post-task and overall satisfaction scores **Observation Categories:** - Critical usability issues (prevent task completion) - Major issues (cause significant frustration or delay) - Minor issues (small annoyances) - Positive findings (what works well) **Analysis Methods:** - Thematic analysis of qualitative feedback - Severity rating for identified issues - Prioritization based on frequency and impact - Recommendations tied to specific observations ## 6. Pilot Test Plan **Before Full Testing:** - Run pilot test with 1-2 colleagues not involved in design - Validate task clarity and timing - Test recording equipment and tools - Refine script based on pilot feedback - Ensure tasks are achievable with current prototype state ## 7. Reporting Framework **Deliverable Structure:** - Executive summary with key findings - Methodology overview - Participant demographics - Task-by-task analysis with success rates and observations - Prioritized list of usability issues with severity ratings - Video clips or quotes illustrating key findings - Actionable recommendations for each issue - Next steps and follow-up testing needs Ensure the protocol maintains consistency across all participants, eliminates bias in questions and task wording, gathers both quantitative metrics and qualitative insights, provides clear guidance for moderators and note-takers, and produces actionable findings that directly inform design improvements.

You are an expert UI/UX designer specializing in form design and data entry interfaces, with deep knowledge of usability principles, accessibility standards, and conversion optimization techniques that maximize form completion rates. Design a comprehensive form and input field system for [PROJECT/APPLICATION NAME] targeting [PLATFORM: web, mobile app, tablet, responsive]. The form serves [PRIMARY PURPOSE: user registration, checkout, profile creation, data collection, lead generation] for [TARGET USER PERSONA]. ## Project Context: **Form Overview:** - Form purpose: [e.g., account signup, checkout, contact form, survey, application] - User motivation: [highly motivated, moderately interested, reluctant/required] - Completion environment: [focused task, quick mobile interaction, complex workflow] - Expected frequency: [one-time, occasional, daily use] - Data sensitivity: [public information, personal data, financial/health data] **Business Requirements:** - Required fields: [List essential data points that must be collected] - Optional fields: [List nice-to-have information] - Validation rules: [Format requirements, character limits, dependencies] - Conversion goals: [Target completion rate, time to complete] - Compliance needs: [GDPR, CCPA, HIPAA, accessibility standards] **Technical Environment:** - Platform: [Web responsive, native iOS, native Android, progressive web app] - Framework: [React, Vue, Angular, vanilla HTML/CSS] - Validation approach: [Real-time inline, on blur, on submit, hybrid] - Backend integration: [API endpoints, submission handling, error responses] ## Form Structure & Architecture: ### Overall Form Design: **Layout Pattern:** - Format: [Single column (recommended), multi-column, grid layout] - Orientation: [Vertical stacking, horizontal grouping for related fields] - Width: [Max-width 600px for readability, full-width for complex forms] - Spacing: [Consistent vertical rhythm using 16-24px between fields] **Form Length Strategy:** - Approach: [Single page, multi-step wizard, progressive disclosure, accordion sections] - Field count: [Aim for minimum viable fields, typically 5-7 visible at once] - Grouping: [Logical sections with clear headings: Personal Info, Payment, Preferences] - Progress indication: [Step indicators, progress bar, "Step X of Y" for multi-page] **Visual Hierarchy:** - Section headings: [H2-H3 tags, 18-24px font size, bold weight] - Field labels: [14-16px, medium weight, distinct from help text] - Help text: [12-14px, lighter weight or muted color] - Error messages: [Same size as help text, error color, icon for emphasis] ## Input Field Design Specifications: ### Field Types & Components: Design appropriate input types for: **1. Text Input Fields** - **Use cases**: Name, email, address, search, comments - **Specifications**: - Height: [44-56px for comfortable touch targets] - Padding: [12-16px horizontal, 12-14px vertical] - Border: [1-2px solid, subtle gray default, prominent on focus] - Border radius: [0px sharp, 4px slight, 8px rounded] - Font size: [16px minimum on mobile to prevent zoom] - Background: [White or subtle gray, distinct from page background] **2. Text Area (Multi-line)** - **Use cases**: Comments, descriptions, messages, feedback - **Specifications**: - Minimum height: [80-120px, 3-5 visible lines] - Resize behavior: [Vertical only, auto-expand, fixed] - Character counter: [Show remaining/used characters if limited] **3. Select Dropdown** - **Use cases**: Country selection, categories, options >5 items - **Specifications**: - Default state: ["Select..." placeholder or pre-selected common option] - Dropdown style: [Native browser, custom styled, searchable] - Mobile behavior: [Native picker overlay, full-screen modal] - Maximum visible options: [5-7 before scrolling] **4. Radio Buttons** - **Use cases**: Mutually exclusive options, 2-5 choices, important visibility - **Specifications**: - Size: [20-24px clickable area, 16-18px visual indicator] - Spacing: [16-20px between options] - Layout: [Vertical stacking (preferred), horizontal for 2-3 short options] - Label position: [Right of button, clickable label expands hit area] **5. Checkboxes** - **Use cases**: Multiple selections, terms acceptance, preferences - **Specifications**: - Size: [20-24px clickable area] - Spacing: [12-16px between options] - Indeterminate state: [For "Select All" or parent selections] - Label: [Clear, concise, clickable] **6. Toggle Switches** - **Use cases**: On/off settings, feature enables, binary choices with immediate effect - **Specifications**: - Size: [48-56px width, 24-28px height] - States: [Clear on/off visual distinction, smooth transition animation] - Labels: ["On" and "Off" labels or descriptive state indicators] **7. Date Picker** - **Use cases**: Birthdate, appointment scheduling, date ranges - **Specifications**: - Input format: [MM/DD/YYYY with clear display format] - Picker type: [Calendar overlay, native mobile picker, text input with validation] - Constraints: [Min/max dates, disabled dates, default to today] **8. Time Picker** - **Use cases**: Appointment times, scheduling - **Specifications**: - Format: [12-hour with AM/PM, 24-hour based on locale] - Input method: [Dropdown, stepper, native picker, text with validation] - Increment: [15-minute, 30-minute, custom intervals] **9. File Upload** - **Use cases**: Document submission, image upload, attachments - **Specifications**: - Trigger: [Button click, drag-and-drop area, both] - Preview: [Thumbnail for images, filename for documents] - Progress: [Upload progress bar, status indicators] - Validation: [File type restrictions, size limits, preview before upload] **10. Number Input** - **Use cases**: Quantity, age, price, measurements - **Specifications**: - Steppers: [Plus/minus buttons for easy increment/decrement] - Mobile keyboard: [Numeric keyboard with inputmode="numeric"] - Constraints: [Min/max values, step increments] **11. Search Input** - **Use cases**: Filter fields, lookup, autocomplete - **Specifications**: - Icon: [Magnifying glass icon inside field] - Clear button: [X icon to clear input when populated] - Autocomplete: [Dropdown suggestions as user types] - Debouncing: [300-500ms delay before search triggers] **12. Password Input** - **Use cases**: Authentication, account creation - **Specifications**: - Visibility toggle: [Eye icon to show/hide password] - Strength indicator: [Visual bar showing weak/medium/strong] - Requirements: [Display password rules clearly upfront] - Confirmation field: [Match validation for new password creation] ### Input Field States: Design comprehensive states for all inputs: **Default/Empty State:** - Border: [1px solid, neutral gray #CCCCCC or similar] - Background: [White or very light gray] - Placeholder: [Lighter gray text, example format or hint] - Cursor: text or pointer **Focus State:** - Border: [2px solid, primary brand color or high-contrast blue] - Background: [Same as default or slight highlight] - Outline: [Additional focus ring for accessibility, 2-3px offset] - Shadow: [Optional subtle glow effect matching border color] - Label: [Color change or bold to reinforce focus] **Filled/Valid State:** - Border: [Maintain focus color or return to subtle default] - Text: [Dark, readable color at 16px minimum] - Icon: [Optional checkmark for confirmed valid input] - Background: [Standard background, no change needed] **Error State:** - Border: [2px solid, error red #D32F2F or similar] - Background: [Optional light red tint #FFEBEE] - Icon: [Error icon (exclamation, X) in red] - Message: [Clear, specific error text below field in red] - Label: [Optional red color to reinforce error] **Disabled State:** - Border: [Lighter gray, reduced opacity] - Background: [Light gray #F5F5F5 to show unavailability] - Text: [Gray, reduced opacity 50-60%] - Cursor: not-allowed or default - Label: [Muted color matching disabled appearance] **Loading State:** - Indicator: [Spinner or skeleton animation inside field] - Behavior: [Disabled interaction during processing] - Use cases: [Address lookup, username availability check] ### Label Design: **Label Positioning:** - Position: [Top-aligned above field (recommended for accessibility)] - Alternative: [Floating label that moves up on focus/fill] - Avoid: [Left-aligned labels create uneven form, harder to scan] **Label Content:** - Clarity: [Clear, concise, descriptive wording] - Length: [2-5 words typically, avoid lengthy questions] - Language: [Use user's vocabulary, avoid jargon] - Required indicator: [Asterisk (*) or "(required)" text] - Optional indicator: ["(optional)" for fields in mostly-required forms] **Label Typography:** - Font size: [14-16px for readability] - Font weight: [500-600 medium to bold] - Color: [Dark gray or black for contrast, 4.5:1 minimum ratio] - Line height: [1.4-1.5 for multi-line labels] ### Placeholder Text: **Best Practices:** - Purpose: [Show format example, not replace label] - Content: ["Example: [email protected]" or "MM/DD/YYYY"] - Avoid: [Using placeholder as label, disappears on focus] - Color: [Light gray with 3:1 contrast minimum] - Never replace labels: [Placeholders alone fail accessibility] ### Help Text & Hints: **Placement & Content:** - Position: [Below field, above field for critical pre-entry info] - Content: [Format requirements, character limits, examples] - Tone: [Helpful, concise, plain language] - Visibility: [Always visible for critical info, tooltip for optional] **Typography:** - Font size: [12-14px, smaller than label] - Color: [Medium gray for neutral hints, error red for problems] - Icon: [Info icon for tooltips, error/warning icon for issues] ## Validation & Error Handling: ### Validation Timing: **Real-time Validation (Inline):** - Trigger: [On blur (leaving field), during typing for specific fields] - Best for: [Format validation (email, phone), availability checks (username)] - Show success: [Checkmark icon for confirmed valid input] - Show errors: [Immediately after user stops typing, not during] **On-submit Validation:** - Trigger: [When user clicks submit button] - Best for: [Required field checks, final validation pass] - Error summary: [List all errors at top of form with anchor links] - Focus management: [Move focus to first error field] **Hybrid Approach (Recommended):** - Format validation: [Real-time on blur] - Required checks: [On submit] - Complex rules: [On submit to avoid premature errors] - Success confirmation: [Real-time to build confidence] ### Error Message Design: **Message Characteristics:** - Specificity: ["Email must include @" not "Invalid email"] - Tone: [Helpful and constructive, never blame user] - Length: [One sentence, 50-75 characters maximum] - Action: [Tell user how to fix: "Enter 10 digits" vs. "Invalid"] **Visual Design:** - Color: [Error red for text and border] - Icon: [Error icon (exclamation, X) for visual emphasis] - Position: [Directly below field, connected to specific input] - Persistence: [Remain until corrected, don't flash briefly] **Accessibility:** - ARIA: [aria-invalid="true", aria-describedby linking to error message] - Screen reader: [Error announced immediately on trigger] - Focus: [Move focus to first error field on submit] ### Success Feedback: **Visual Confirmation:** - Indicator: [Green checkmark icon inside or beside field] - Border: [Optional green border for extra confirmation] - Message: [Optional "Looks good!" or similar positive reinforcement] - Use sparingly: [Important fields only to avoid visual clutter] ## Form Actions & Submission: ### Submit Button: **Design Specifications:** - Size: [Prominent, minimum 44x44px touch target] - Width: [Full-width on mobile, fixed or content-width on desktop] - Position: [Bottom of form, left-aligned with fields] - Style: [Primary button styling, highest visual weight] - Label: [Action-oriented: "Create Account", "Complete Purchase", not generic "Submit"] **Loading State:** - Indicator: [Spinner replacing or alongside button text] - Text: ["Creating Account..." or "Processing..."] - Disabled: [Prevent double-submission] - Width: [Maintain size to prevent layout shift] **Success State:** - Feedback: [Success message, redirect, or confirmation screen] - Timing: [Immediate feedback within 100ms] - Persistence: [Keep data until confirmed saved] ### Secondary Actions: **Cancel/Back Button:** - Style: [Secondary or tertiary button, lower visual weight] - Position: [Left of submit, or above form] - Behavior: [Confirm if substantial data entered] **Save Draft/Progress:** - Function: [Auto-save for long forms, manual save option] - Feedback: ["Saved" indicator with timestamp] - Recovery: [Restore on return to form] **Reset/Clear:** - Caution: [Avoid unless necessary, requires confirmation] - Position: [Far from submit to prevent accidental clicks] ## Mobile Optimization: ### Touch Targets: - Minimum size: [44x44px for all interactive elements] - Spacing: [8px minimum between tappable elements] - Field height: [48-56px for comfortable thumb reach] ### Keyboard Behavior: - Input type: [Use appropriate inputmode/type for numeric, email, tel, url] - Keyboard display: [Numeric for numbers, email keyboard for email fields] - Next/Done: [Proper field tabbing, submit on keyboard action] - Autocomplete: [Enable browser autocomplete attributes] ### Mobile-Specific Patterns: - Single column: [Always use vertical stacking on mobile] - Auto-focus: [Avoid on mobile, causes keyboard jump] - Fixed buttons: [Consider sticky submit button at bottom] - Field labels: [Always use floating or top labels, never side-by-side] ## Accessibility Requirements: ### Semantic HTML: - Use proper: [<form>, <label>, <input>, <button> elements] - Field association: [Label for="fieldID" linking labels to inputs] - Fieldset/Legend: [Group related fields like radio button sets] ### ARIA Attributes: - aria-required: ["true" for required fields] - aria-invalid: ["true" for error states] - aria-describedby: [Link to help text and error messages] - aria-label: [For icon-only buttons or inputs without visible labels] - role: [Proper roles for custom components] ### Keyboard Navigation: - Tab order: [Logical top-to-bottom, left-to-right flow] - Focus indicators: [Visible focus ring on all interactive elements] - Shortcuts: [Enter to submit, Esc to cancel modal forms] - Skip links: [Skip to form or skip past form navigation] ### Visual Accessibility: - Color contrast: [4.5:1 for text, 3:1 for interactive elements] - Focus indicators: [3:1 contrast against background] - Error indication: [Never rely on color alone, use icons and text] - Font size: [16px minimum on mobile, 14px desktop] ### Screen Reader Support: - Field labels: [Always present, properly associated] - Error announcements: [Live regions for dynamic errors] - Form instructions: [Read before form interaction begins] - Progress updates: [Announce multi-step progress changes] ## Advanced Features: ### Smart Defaults & Auto-fill: - Browser autocomplete: [Proper autocomplete attributes for standard fields] - Remembered values: [Pre-fill returning user data] - Intelligent defaults: [Country based on IP, common selections] - Address lookup: [API integration for address autocomplete] ### Progressive Disclosure: - Conditional fields: [Show fields based on previous answers] - Show more: [Collapse optional or advanced fields] - Multi-step: [Break long forms into logical steps] ### Data Format Handling: - Auto-formatting: [Phone numbers, credit cards, dates as user types] - Flexible input: [Accept various formats, normalize on backend] - Mask inputs: [Show expected format with underscores or dashes] ### Privacy & Security: - Password visibility: [Toggle to show/hide] - Sensitive data: [Mask credit cards, SSN after entry] - HTTPS: [Always use for forms collecting personal data] - Clear data policy: [Link to privacy policy near sensitive fields] ## Deliverables: 1. **Complete Form Design:** - All field types with states (default, focus, filled, error, disabled) - Mobile and desktop responsive layouts - Multi-step flow designs if applicable - Success and error screen designs - Organized in [Figma/Sketch/Adobe XD] with components 2. **Interactive Prototype:** - Working form with validation behavior - Error state demonstrations - Mobile keyboard interactions - Success flow and feedback 3. **Technical Specifications:** - HTML structure with semantic markup - CSS specifications for all states - Validation rules documentation - ARIA attributes and accessibility implementation - Framework components [React/Vue/Angular] 4. **Validation Logic Document:** - Field-by-field validation rules - Error message library - Timing specifications (when to validate) - Edge case handling 5. **Usage Guidelines:** - When to use each field type - Label and help text writing guide - Error message tone and style guide - Do's and don'ts with visual examples - Mobile-specific considerations 6. **Accessibility Checklist:** - WCAG 2.2 AA compliance verification - Keyboard navigation testing results - Screen reader compatibility notes - Color contrast verification Ensure the form design achieves: - **High completion rates**: 70%+ for optional forms, 90%+ for required flows - **Fast completion time**: Target 2-3 minutes for standard registration forms - **Low error rates**: Clear validation reduces submission errors by 50%+ - **Accessibility compliance**: WCAG 2.2 AA minimum, AAA where possible - **Mobile optimization**: Equal or better experience on mobile devices - **Cross-browser compatibility**: Consistent experience across all major browsers

You are an expert UX researcher specializing in heuristic evaluation and usability assessment. Create a comprehensive heuristic evaluation framework for the following product: Product/Interface: [PRODUCT NAME AND TYPE] Target Users: [PRIMARY USER DEMOGRAPHICS AND PERSONAS] Business Goals: [KEY BUSINESS OBJECTIVES] Evaluation Scope: [SPECIFIC FEATURES OR FLOWS TO EVALUATE] Based on Jakob Nielsen's 10 usability heuristics, develop a detailed evaluation framework that includes: 1. HEURISTIC CRITERIA For each of the 10 heuristics (Visibility of system status, Match between system and real world, User control and freedom, Consistency and standards, Error prevention, Recognition rather than recall, Flexibility and efficiency of use, Aesthetic and minimalist design, Help users recognize and recover from errors, Help and documentation), provide: - Specific evaluation questions tailored to the product - Observable indicators of compliance or violation - Examples relevant to the interface type 2. SEVERITY RATING SYSTEM Define a clear severity scale (e.g., 0-4) for categorizing usability issues: - Rating criteria for each level - Impact assessment guidelines - Prioritization framework based on user impact and business goals 3. EVALUATION PROCESS Outline the step-by-step methodology: - Pre-evaluation preparation and evaluator briefing - Independent evaluation procedures - Documentation and reporting templates - Aggregation and synthesis methods - Debriefing and prioritization sessions 4. REPORTING STRUCTURE Create a framework for documenting findings: - Issue description format - Heuristic violation mapping - Severity assignment - Screenshot or evidence documentation - Actionable recommendations - Priority ranking based on severity and frequency 5. ACTIONABLE RECOMMENDATIONS Provide guidelines for translating findings into design improvements: - Quick wins vs. long-term solutions - Resource allocation suggestions - Implementation roadmap considerations Ensure the framework is practical, actionable, and aligned with both user needs and business objectives. Include specific examples where applicable to make the evaluation criteria concrete and measurable.

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.

You are an expert UX researcher specializing in information architecture and usability testing methodologies. Create a comprehensive research plan that includes both card sorting and tree testing studies for the following project: Project Overview: [PRODUCT OR WEBSITE NAME AND PURPOSE] Current IA Status: [NEW DESIGN, REDESIGN, OR OPTIMIZATION] Content Scope: [NUMBER AND TYPE OF CONTENT ITEMS TO ORGANIZE] Target Users: [PRIMARY USER DEMOGRAPHICS AND BEHAVIORS] Key User Tasks: [TOP 3-5 TASKS USERS NEED TO ACCOMPLISH] Research Timeline: [AVAILABLE TIMEFRAME FOR STUDIES] Research Budget: [AVAILABLE RESOURCES AND TOOLS] Develop a complete research plan that includes: 1. CARD SORTING STUDY DESIGN - Study type selection (open, closed, or hybrid) with rationale based on project goals - Card preparation: How many cards, content selection criteria, and card labeling guidelines - Category considerations: Pre-defined categories for closed sorts or category creation instructions for open sorts - Participant recruitment: Sample size recommendations (minimum 15-30 participants), screening criteria, and recruitment channels - Moderated vs unmoderated approach with pros and cons for this specific context - Step-by-step session protocol including instructions, time estimates, and facilitator guidelines - Tools and platforms recommendation (online vs physical, specific software options) 2. TREE TESTING STUDY DESIGN - Tree structure preparation: How to build the text-only hierarchy from card sorting results or existing IA - Task scenario development: 5-10 realistic, specific tasks that reflect actual user goals - Task wording best practices to avoid leading participants or revealing answers - Participant requirements: Sample size (30-60 recommended), overlap with card sorting participants or fresh panel - Success metrics definition: Direct vs indirect paths, task completion rates, time-on-task benchmarks - Testing tool selection and setup instructions - Session flow and participant instructions 3. SEQUENTIAL RESEARCH WORKFLOW - Phase 1: Card sorting execution timeline and milestones - Analysis transition: How to synthesize card sorting data into testable tree structures - Phase 2: Tree testing execution based on card sorting insights - Iteration strategy: When and how to conduct follow-up tests - Decision points: Criteria for moving from one phase to next 4. DATA ANALYSIS FRAMEWORK Card Sorting Analysis: - Similarity matrix and dendrogram interpretation - Agreement scores and consensus metrics - Category naming analysis from open sorts - Pattern identification across participant groups - Outlier and edge case handling Tree Testing Analysis: - Success rate calculations and benchmarks - Path analysis: Direct, indirect, and failed attempts - First-click analysis and its significance - Time-on-task patterns - Problem area identification (where users get lost) - Comparative analysis if testing multiple structures 5. DELIVERABLES AND RECOMMENDATIONS - Recommended IA structure with evidence-based rationale - Navigation labeling recommendations - Problem areas requiring attention with severity assessment - Quick wins vs long-term improvements - Visual documentation: Site maps, user flow diagrams, comparison matrices - Stakeholder presentation format with key insights and actionable recommendations 6. RISK MITIGATION AND QUALITY ASSURANCE - Pilot testing approach to validate study design - Common pitfalls and how to avoid them - Participant fatigue management - Data quality checks and validation methods - Contingency plans for low participation or inconclusive results Ensure the plan is practical, scientifically rigorous, and aligned with industry best practices. Provide specific guidance that accounts for the project context, timeline, and resources while maintaining methodological integrity.

You are an expert UX researcher and experimentation specialist with deep knowledge of A/B testing methodology and statistical analysis. Create a comprehensive A/B testing plan with a strong hypothesis and experimental design for the following scenario: Product/Feature: [PRODUCT NAME AND SPECIFIC FEATURE OR PAGE] Current Challenge: [SPECIFIC PROBLEM OR OPPORTUNITY IDENTIFIED] User Behavior Data: [RELEVANT ANALYTICS, USER FEEDBACK, OR RESEARCH INSIGHTS] Business Context: [BUSINESS GOALS AND CONSTRAINTS] Target Audience: [SPECIFIC USER SEGMENTS TO TEST] Traffic Volume: [ESTIMATED MONTHLY VISITORS OR USERS] Test Duration Constraints: [AVAILABLE TIMEFRAME] Develop a complete A/B testing plan that includes: 1. EVIDENCE-BASED HYPOTHESIS FORMULATION Create a clear, testable hypothesis using the structure: "If [SPECIFIC CHANGE], then [EXPECTED OUTCOME], because [EVIDENCE-BASED REASONING]" Provide: - Problem statement grounded in user data and behavioral insights - Root cause analysis of the current issue based on available evidence - Proposed solution with design rationale tied to UX principles or proven patterns - Expected impact quantified where possible - Alternative hypotheses to consider if primary test shows negative or neutral results - Risk assessment: What could go wrong and potential negative impacts 2. EXPERIMENT DESIGN STRUCTURE Control and Variant Specifications: - Detailed description of Control (A): Current design baseline - Detailed description of Variant (B): Proposed change with specific modifications - Visual or textual specifications of exactly what differs between versions - Rationale for limiting test to one variable (or justification for multivariate approach) - Edge cases and responsive design considerations for the variant Randomization and Assignment: - User assignment methodology (random, stratified, etc.) - Consistency requirements (should same user always see same version) - New vs returning user considerations - Device and platform distribution strategy 3. SUCCESS METRICS FRAMEWORK Primary Metric: - Single, clearly defined metric that directly measures hypothesis success - Current baseline performance with specific numbers - Minimum detectable effect (MDE): Smallest improvement worth detecting - Success threshold: What level of improvement validates the change Guardrail Metrics: - 3-5 secondary metrics to ensure change doesn't harm other aspects - Acceptable ranges for each guardrail metric - Business health indicators (revenue, retention, engagement) Measurement Implementation: - Tracking mechanism and tools required - Event instrumentation specifications - Data validation checkpoints 4. STATISTICAL RIGOR AND SAMPLE SIZE - Sample size calculation based on traffic, baseline conversion, and MDE - Statistical significance threshold (typically 95% confidence level) - Statistical power target (typically 80%) - Estimated test duration to reach statistical significance - Early stopping criteria and sequential testing considerations - Handling of multiple comparisons if testing more than two variants 5. IMPLEMENTATION SPECIFICATIONS Technical Requirements: - A/B testing platform or tool recommendations - Traffic allocation percentages (e.g., 50/50 split) - Triggering conditions: When does test activate - Exclusion criteria: Which users or sessions to exclude - Quality assurance checklist before launch Rollout Strategy: - Pilot phase: Test with small percentage first (e.g., 5% of traffic) - Monitoring plan for first 24-48 hours - Escalation procedures if technical issues arise - Full rollout timeline once pilot validates technical implementation 6. EXTERNAL VARIABLE CONTROL Identify and plan for: - Seasonal variations or time-based confounds - Marketing campaigns or promotional periods that could skew results - Device type, browser, or geographic segmentation needs - Known bugs or technical issues that could contaminate results - User segment differences that require stratified analysis 7. ANALYSIS AND DECISION FRAMEWORK Data Analysis Plan: - When and how to check results (avoid peeking bias) - Segmentation analysis: Break down results by user type, device, traffic source - Statistical test to use (t-test, chi-square, etc.) - Confidence interval reporting alongside point estimates Decision Criteria: - Clear "ship it" criteria: What results trigger implementation of variant - "Keep testing" criteria: Inconclusive results requiring extended duration - "Abandon" criteria: Negative or neutral results that kill the hypothesis - Learning extraction: What to document regardless of outcome - Iteration planning: Next experiments based on various result scenarios 8. COMMUNICATION AND DOCUMENTATION - Stakeholder briefing template explaining test purpose and expected timeline - Results presentation format with visual data representations - Key insights and recommendations format - Test documentation for future reference and organizational learning - Post-test action items and owner assignments Ensure the plan follows A/B testing best practices, maintains scientific rigor, and provides actionable guidance for running a reliable experiment. Balance statistical validity with practical business constraints. Make the plan specific enough to execute while remaining flexible for unforeseen circumstances.

You are an expert responsive UI designer specializing in creating adaptive layouts that deliver exceptional user experiences across all devices and screen sizes. Your task is to generate comprehensive responsive breakpoint specifications for [PROJECT NAME OR WEBSITE TYPE]. Project Context: - Primary target devices: [MOBILE/TABLET/DESKTOP/ALL] - User analytics data: [MOST COMMON DEVICE SIZES FROM ANALYTICS] - Content priorities: [KEY CONTENT AND FEATURES TO PRIORITIZE] - Design approach: [MOBILE-FIRST/DESKTOP-FIRST/CONTENT-FIRST] - Framework or grid system: [BOOTSTRAP/TAILWIND/CUSTOM/NONE] - Performance requirements: [LOADING TIME GOALS AND CONSTRAINTS] Generate a detailed responsive breakpoint specification document that includes: 1. Breakpoint Strategy Overview - Rationale for chosen breakpoint approach (device-based vs content-based) - Number of breakpoints and justification for each - Design philosophy (progressive enhancement or graceful degradation) - Target devices and orientations for each breakpoint - Analytics-driven insights supporting breakpoint decisions 2. Breakpoint Definitions - Exact pixel values or rem-based measurements for each breakpoint - Media query specifications with min-width and max-width ranges - Naming conventions for breakpoints (XS, SM, MD, LG, XL or custom names) - Viewport meta tag specifications - Container max-widths at each breakpoint - Orientation-specific breakpoints for portrait and landscape modes 3. Layout Adaptations by Breakpoint For each defined breakpoint, specify: - Grid column structure and changes (12-column to 4-column, etc.) - Content arrangement and stacking order - Sidebar behavior (visible, collapsed, off-canvas) - Navigation pattern transformations (horizontal nav to hamburger menu) - Typography scale adjustments (heading sizes, body text, line heights) - Spacing system modifications (margins, padding, gaps) - Image sizing and aspect ratio adjustments 4. Component-Specific Breakpoint Behavior Document how key UI components adapt: - Navigation menus (mega menu to mobile drawer) - Cards and grid layouts (4-column to 2-column to single column) - Forms and input fields (multi-column to stacked) - Tables (horizontal scroll, stacked rows, or data transformation) - Modals and overlays (full-screen vs centered) - Hero sections and banners (height and content adjustments) - Buttons and CTAs (sizing and positioning changes) - Search bars and filters (expanded vs collapsed states) 5. Content Prioritization Strategy - Content hierarchy at each breakpoint - Elements to show, hide, or collapse at smaller screens - Progressive disclosure patterns for complex content - Lazy loading strategies for images and heavy content - Content reordering techniques using CSS flexbox or grid - Text truncation and "Read More" implementation guidelines 6. Touch and Interaction Considerations - Minimum touch target sizes (44x44px for mobile) - Spacing between interactive elements - Hover state alternatives for touch devices - Gesture support (swipe, pinch, long-press) at mobile breakpoints - Keyboard navigation enhancements for all breakpoints - Click area expansion for small elements on mobile 7. Performance Optimization by Breakpoint - Image srcset specifications for responsive images - Different image assets to load at each breakpoint - Font loading strategies per device size - JavaScript functionality to conditionally load or disable - Animation complexity adjustments for performance - Asset size budgets for each breakpoint 8. Testing and Quality Assurance Matrix - Specific devices and screen sizes to test for each breakpoint - Browser compatibility requirements per breakpoint - Orientation testing checklist (portrait and landscape) - Edge case scenarios (in-between sizes, unusual aspect ratios) - Visual regression testing checkpoints - Performance benchmarks for each breakpoint 9. Developer Implementation Guidelines - CSS media query code templates for each breakpoint - Mobile-first vs desktop-first CSS cascade approach - Utility class naming for responsive behaviors - Breakpoint variables for Sass, Less, or CSS custom properties - JavaScript breakpoint detection methods - Debugging and inspection techniques for responsive issues 10. Documentation and Design File Organization - Artboard or frame naming conventions in design files - How to organize and present breakpoint variations to stakeholders - Annotation standards for responsive behavior - Version control for breakpoint specifications - Handoff documentation structure for developers Provide specific pixel values, CSS code examples, and visual descriptions for layout changes. Create a clear hierarchy of breakpoints that balances comprehensive coverage with maintainability. Ensure specifications are actionable and eliminate ambiguity for designers and developers implementing responsive layouts.

You are an expert UX researcher specializing in qualitative data analysis, research synthesis, and insight generation. Create a comprehensive framework for synthesizing user feedback and extracting actionable insights for the following project: Project Context: [PRODUCT NAME AND STAGE - NEW FEATURE, REDESIGN, OR ONGOING OPTIMIZATION] Feedback Sources: [LIST ALL SOURCES - USER INTERVIEWS, SURVEYS, SUPPORT TICKETS, APP REVIEWS, USABILITY TESTS, ETC.] Data Volume: [APPROXIMATE AMOUNT OF FEEDBACK - NUMBER OF INTERVIEWS, SURVEY RESPONSES, TICKETS, ETC.] Research Objectives: [KEY QUESTIONS YOU NEED TO ANSWER] Stakeholders: [WHO WILL USE THESE INSIGHTS - DESIGNERS, PRODUCT MANAGERS, EXECUTIVES, ETC.] Timeline: [TIMEFRAME FOR SYNTHESIS AND DELIVERY] Team Resources: [NUMBER OF RESEARCHERS OR TEAM MEMBERS INVOLVED] Develop a complete synthesis framework that includes: 1. DATA PREPARATION AND ORGANIZATION Data Collection Strategy: - Centralization approach: How to gather feedback from disparate sources into one location - Data formatting standards: Structuring transcripts, survey responses, and unstructured feedback - Metadata tagging: User demographics, context, date, source, sentiment indicators - Data cleaning: Handling duplicates, irrelevant content, and incomplete responses - Privacy and anonymization considerations - Tools and platforms recommendation (Dovetail, Miro, Airtable, spreadsheets, etc.) Initial Familiarization: - Immersion process: How team members should engage with raw data - Note-taking protocols during familiarization phase - Initial observation documentation without premature conclusions - Bias awareness and mitigation strategies 2. SYSTEMATIC CODING AND ANALYSIS METHODOLOGY Thematic Analysis Framework: - First-cycle coding: Open coding process for initial label generation - Code definitions: Creating a codebook with clear descriptions and examples - Coding consistency: Inter-rater reliability if multiple researchers are coding - Second-cycle coding: Axial coding to identify relationships between codes - Theme development: Aggregating codes into broader, meaningful themes - Theme validation: Checking themes against raw data for accuracy Coding Approach: - Inductive vs deductive coding strategy based on research objectives - Unit of analysis: Determining what to code (sentences, paragraphs, concepts) - Frequency tracking: Quantifying how often themes appear - Sentiment coding: Labeling feedback as positive, negative, neutral, or mixed - Severity or impact rating: Assessing criticality of issues raised 3. AFFINITY MAPPING AND PATTERN IDENTIFICATION Affinity Diagramming Process: - Data atomization: Breaking feedback into discrete, actionable insights on individual notes - Silent grouping exercise: Team-based clustering without premature discussion - Labeling clusters: Creating meaningful category names that reflect content - Hierarchical organization: Creating sub-groups and super-groups as needed - Relationship mapping: Identifying connections between different theme clusters - Digital vs physical approach: Choosing the right medium for your team Pattern Recognition Techniques: - Identifying recurring pain points across different user segments - Spotting contradictions or conflicting feedback and how to interpret them - Recognizing edge cases vs. widespread issues - Finding unexpected insights that challenge assumptions - Temporal patterns: Issues that emerge at specific journey stages - Segment-specific patterns: How feedback differs by user type, geography, or behavior 4. MULTI-SOURCE TRIANGULATION Integrating Diverse Feedback Types: - Combining qualitative insights (interviews, open-ended surveys) with quantitative data (ratings, usage analytics) - Cross-validating findings across different feedback sources - Identifying where different sources agree or diverge - Weighting feedback: Balancing vocal minorities vs. silent majorities - Contextualizing feedback with behavioral data to validate stated vs. revealed preferences Conflict Resolution: - Handling contradictory feedback from different user segments - Distinguishing between preference-based feedback and usability issues - Prioritizing when feedback conflicts with business goals or technical constraints 5. INSIGHT GENERATION AND PRIORITIZATION Transforming Themes into Actionable Insights: - Root cause analysis: Moving from symptoms to underlying problems - Opportunity framing: Reframing problems as design opportunities - User impact assessment: Estimating how many users are affected - Business impact evaluation: Connecting user needs to business outcomes - Effort estimation: Considering implementation complexity - Creating insight statements: [USER SEGMENT] needs/wants [OUTCOME] because [REASON] Prioritization Framework: - Impact vs. effort matrix for categorizing insights - Severity scoring based on user pain level and frequency - Strategic alignment: Matching insights to product vision and roadmap - Quick wins identification: Low-effort, high-impact improvements - Long-term opportunities: Strategic initiatives requiring significant investment 6. CONTEXTUAL ENRICHMENT Journey Mapping Integration: - Plotting feedback along the user journey to identify critical touchpoints - Emotion mapping: Documenting user sentiment at each stage - Pain point concentration: Finding where most issues cluster - Moment of delight identification: Recognizing what works well Persona and Segment Analysis: - Breaking down insights by user personas or segments - Identifying segment-specific needs and pain points - Finding universal issues that affect all users - Understanding how different user types experience the same feature differently 7. VISUALIZATION AND COMMUNICATION Insight Documentation: - Executive summary: High-level findings for stakeholders (1-2 pages) - Detailed findings report: Comprehensive documentation with supporting evidence - Theme hierarchy: Visual representation of relationships between themes - Quote library: Compelling user quotes that illustrate each theme - Photo or video evidence from usability sessions where applicable Visualization Techniques: - Thematic maps showing theme relationships and hierarchies - Journey maps annotated with feedback and pain points - Prioritization matrices (impact vs. effort, severity vs. frequency) - Before-after scenarios illustrating potential improvements - Quantitative overlays: Charts showing frequency of themes or sentiment distribution 8. ACTIONABLE RECOMMENDATIONS Recommendation Framework: - Specific design recommendations tied to each major insight - Rationale connecting recommendations back to user feedback - Expected outcomes: How recommendations will address user needs - Success metrics: How to measure if recommendations worked - Implementation considerations: Dependencies, constraints, risks Roadmap Integration: - Now/Next/Later categorization for phased implementation - Feature prioritization based on synthesis findings - Design sprint opportunities: Focused workshops to tackle key insights - Follow-up research needs: Gaps requiring additional investigation 9. VALIDATION AND ITERATION Insight Validation Approaches: - Stakeholder review sessions to validate interpretation - Follow-up research to test hypotheses generated from synthesis - Quantitative validation: Using analytics or surveys to confirm qualitative patterns - Design validation: Testing prototypes based on insights to verify solutions work Continuous Synthesis: - Repository creation: Building a searchable database of insights over time - Longitudinal tracking: Monitoring how themes evolve across research cycles - Feedback loops: Regularly updating synthesis as new data arrives - Knowledge management: Making insights accessible to entire organization 10. STAKEHOLDER ENGAGEMENT AND STORYTELLING Presentation Strategy: - Audience-tailored formats: Different deliverables for designers, PMs, executives - Storytelling techniques: Using narrative arcs to make insights memorable - User voice amplification: Video clips, quotes, and stories that bring data to life - Workshop facilitation: Interactive sessions where teams explore insights together - Evidence-based persuasion: Using data to build consensus for design direction Follow-up and Impact: - Action item tracking: Ensuring insights lead to actual changes - Impact measurement: Documenting how synthesis influenced decisions - Closing the loop: Sharing results with research participants when appropriate - Organizational learning: Building UX maturity through insight sharing Ensure the framework is practical, scientifically rigorous, and produces insights that drive meaningful product improvements. Balance thoroughness with efficiency given timeline constraints. Provide specific guidance that accounts for team size, data volume, and stakeholder needs while maintaining methodological integrity.

You are an expert UI designer specializing in visual hierarchy, typography systems, and spatial design principles. Your task is to create a comprehensive visual hierarchy and spacing system specification for [PROJECT NAME OR PRODUCT TYPE]. Project Context: - Product type: [WEB APPLICATION/MOBILE APP/DASHBOARD/MARKETING SITE] - Brand personality: [MODERN/PLAYFUL/PROFESSIONAL/MINIMALIST/BOLD] - Content density: [HIGH/MEDIUM/LOW] - Target audience: [USER DEMOGRAPHICS AND TECHNICAL PROFICIENCY] - Design system status: [BUILDING NEW/EXPANDING EXISTING/AUDIT AND REFINE] - Primary use cases: [KEY USER TASKS AND CONTENT TYPES] Generate a detailed visual hierarchy and spacing system specification that includes: 1. Visual Hierarchy Principles and Strategy - Core hierarchy philosophy aligned with user goals and content priorities - Information architecture approach (flat vs deep hierarchy) - Attention flow patterns (F-pattern, Z-pattern, or custom) - Primary, secondary, and tertiary content classification system - Principles for distinguishing interactive vs static elements - Hierarchy adaptation strategy across different screen sizes 2. Typography Hierarchy System - Complete type scale with specific sizes, weights, and line heights - Heading levels (H1 through H6) with use cases and context - Body text variations (large, regular, small) with applications - Display typography for hero sections and promotional content - Supporting text styles (captions, labels, helper text, footnotes) - Font weight progression system (light, regular, medium, semibold, bold) - Letter spacing adjustments for different sizes and weights - Text decoration styles (links, emphasis, code, strikethrough) - Paragraph spacing and text block composition rules - Responsive typography scaling across breakpoints 3. Spacing System Foundation - Base unit selection and mathematical progression (4px, 8px system) - Spacing scale with values and naming conventions (XS, S, M, L, XL, etc.) - Design tokens for spacing (margin, padding, gap values) - Vertical rhythm system for consistent baseline alignment - Horizontal spacing rules for layouts and grid gutters - Component-specific spacing standards (form fields, cards, lists) - Relationship between spacing and visual grouping (proximity principle) - Responsive spacing adjustments (denser on mobile, airier on desktop) 4. Size and Scale Hierarchy - Element sizing system beyond typography (icons, buttons, inputs) - Icon size scale with contextual usage (16px, 24px, 32px, etc.) - Button sizing variants (small, medium, large) with touch targets - Image and media sizing guidelines - Container and card sizing standards - Scale relationships creating visual importance (large = important) - Proportional scaling rules maintaining hierarchy across breakpoints 5. Color Hierarchy and Emphasis - Color application strategy for hierarchy (primary, secondary, tertiary) - Contrast ratios creating visual separation and importance - Background color layering system (elevation and depth) - Color coding for different content types or status indicators - Accent color usage for calls-to-action and important elements - Neutral color progression for de-emphasizing content - Text color hierarchy (headings darker, body text medium, captions lighter) 6. Visual Weight and Emphasis Techniques - Font weight as hierarchy indicator - Border weight system (1px, 2px, 4px) and applications - Shadow and elevation system creating depth hierarchy - Opacity variations for de-emphasis and disabled states - Negative space (whitespace) as a hierarchy tool - Containment strategies (boxes, borders, backgrounds) for grouping - Visual markers (icons, badges, indicators) drawing attention 7. Layout and Compositional Hierarchy - Content block spacing creating clear sections - Grid column allocation reflecting content importance - Positioning strategies (top-left priority in Western interfaces) - Alignment rules reinforcing visual relationships - Grouping and proximity patterns (related items closer together) - Separation techniques (dividers, whitespace, color blocks) - Container hierarchy (cards within sections within pages) - Z-index layering system for overlapping elements 8. Interactive Element Hierarchy - Button hierarchy (primary, secondary, tertiary, ghost) - Link styling differentiating from body text - Form input visual weight and focus states - Navigation prominence (main nav vs utility nav vs footer) - Call-to-action emphasis techniques - Icon button vs text button hierarchy - Hover and active state visual changes 9. Content Scanning and Readability Optimization - Scannable patterns using hierarchy (headings, bullets, bold keywords) - Line length limits for optimal reading (45-75 characters) - Paragraph length recommendations - Visual breaks preventing wall-of-text syndrome - Progressive disclosure hierarchy (show less, expand for more) - Summary-to-detail hierarchy patterns - Table and data visualization hierarchy within dense information 10. Design Tokens and Implementation - Token naming conventions for spacing and typography - CSS custom properties or variable structure - Documentation format for developers - Figma or design tool variable setup - Component library integration - Validation rules ensuring hierarchy consistency - Version control and evolution strategy 11. Testing and Validation Methods - Squint test technique (blur to check hierarchy) - Heatmap analysis expectations - User testing protocols for information finding - A/B testing hierarchy variations - Accessibility testing ensuring hierarchy works for screen readers - Cross-device hierarchy validation 12. Common Patterns and Applications - Card component hierarchy (image, title, description, action) - Form layout hierarchy (labels, inputs, help text, errors) - Dashboard hierarchy (KPIs, charts, tables, filters) - Article/blog post hierarchy (title, metadata, body, related content) - Navigation hierarchy (primary items, dropdowns, utility links) - Modal and overlay hierarchy (title, content, actions) For each component of the system, provide specific values (pixel sizes, rem units, spacing tokens), usage guidelines, and visual examples or descriptions. Ensure the system is scalable, maintainable, and creates clear visual relationships that guide users naturally through content and interactions.

You are an expert UX researcher and designer specializing in identifying and solving user experience pain points. Your task is to conduct a comprehensive pain point analysis for [PRODUCT OR SERVICE NAME] targeting [TARGET USER GROUP]. Based on the following context, develop a detailed pain point identification and solution strategy: Project Context: - Product/Service: [PRODUCT OR SERVICE NAME] - Target Users: [TARGET USER GROUP] - Current Stage: [DEVELOPMENT STAGE - e.g., existing product, redesign, new feature] - Business Goals: [PRIMARY BUSINESS OBJECTIVES] - Available Resources: [RESEARCH METHODS AND TOOLS AVAILABLE] Your analysis should include: 1. Pain Point Discovery Strategy - Recommend specific research methodologies (qualitative and quantitative) appropriate for this context - Design a research plan including user interviews, contextual inquiry, usability testing, analytics review, and feedback analysis - Identify key touchpoints in the user journey to investigate - Specify data collection methods and tools 2. Pain Point Classification Categorize identified pain points across three levels: - Interaction-level: Specific UI/UX friction points in individual tasks - Journey-level: Issues spanning multiple steps or stages - Relationship-level: Broader concerns affecting overall user satisfaction and trust For each pain point, document: - Description of the issue - User impact and emotional response - Frequency and severity - Root cause analysis - Supporting evidence from research 3. Prioritization Framework Rank pain points using: - Impact vs Effort Matrix (quick wins, major projects, fill-ins, time sinks) - Severity scoring: frequency, user impact, business impact, and feasibility - User feedback weight and analytics data validation 4. Solution Development For top-priority pain points, provide: - Multiple solution concepts with clear rationale - Design recommendations aligned with user needs - Implementation approach (quick fixes vs long-term improvements) - Success metrics and validation methods - Prototyping and testing strategy 5. Action Plan Create a roadmap that includes: - Phased implementation timeline - Resource requirements - Stakeholder alignment strategy - Measurement and iteration plan Deliver your findings in a structured format with clear documentation, visual frameworks where appropriate, and actionable recommendations that balance user needs with business constraints.

You are an expert UI/UX designer specializing in motion design and animation specifications. Create comprehensive animation and transition specifications for [PROJECT NAME OR INTERFACE TYPE]. Project Context: - Platform: [WEB/MOBILE APP/DESKTOP/CROSS-PLATFORM] - Design System: [MATERIAL DESIGN/FLUENT/CUSTOM/OTHER] - Target Audience: [USER DEMOGRAPHIC AND TECHNICAL PROFICIENCY] - Performance Constraints: [DEVICE CAPABILITIES, BANDWIDTH CONSIDERATIONS] Generate detailed specifications covering: 1. **Duration Standards** - Micro-interactions (buttons, toggles, hovers) - Medium transitions (modals, dropdowns, notifications) - Large transitions (page changes, screen transitions) - Loading states and progress indicators 2. **Easing Functions** - Entry animations (elements appearing) - Exit animations (elements disappearing) - Emphasis animations (drawing attention) - Interactive feedback animations 3. **Animation Behaviors** - Fade specifications (opacity transitions) - Scale transformations (size changes) - Movement patterns (directional motion) - Combined animations (multi-property transitions) 4. **Implementation Guidelines** - CSS/JavaScript specifications - Accessibility considerations (prefers-reduced-motion) - Performance optimization techniques - Fallback behaviors for low-performance devices 5. **Use Cases and Examples** - Navigation transitions - Form feedback animations - Content loading patterns - Error and success states - Contextual overlays and modals For each specification, provide: - Exact timing values in milliseconds - Easing curve specifications (cubic-bezier values or named curves) - Properties being animated - Rationale for the chosen approach - Code snippets or pseudo-code where applicable Ensure all specifications prioritize user experience, maintain consistency across the interface, and follow accessibility best practices.

You are an expert UI/UX designer specializing in loading states and skeleton screen design. Create a comprehensive loading state and skeleton screen design system for [PROJECT NAME OR APPLICATION TYPE]. Project Context: - Platform: [WEB/MOBILE APP/DESKTOP/PROGRESSIVE WEB APP] - Content Types: [TEXT-HEAVY/IMAGE-HEAVY/DATA TABLES/MIXED CONTENT/VIDEO] - Average Load Times: [FAST <500MS/MODERATE 500MS-2S/SLOW >2S] - Target Network Conditions: [4G/5G/VARIABLE/LOW-BANDWIDTH] - Design System: [MATERIAL DESIGN/FLUENT/CUSTOM/BRAND-SPECIFIC] Generate detailed specifications covering: 1. **Skeleton Screen Patterns** - Text content placeholders (headlines, paragraphs, captions) - Media placeholders (images, videos, avatars) - Card and list item structures - Data table and chart placeholders - Navigation and menu skeletons - Form field placeholders 2. **Animation Specifications** - Shimmer/pulse animation timing and easing - Wave progression patterns - Fade-in transition from skeleton to real content - Staggered loading sequences for multiple elements - Animation duration recommendations (1-2 seconds optimal) 3. **Visual Design Guidelines** - Color palette (neutral grays #e0e0e0 to #f5f5f5 range) - Shape specifications (rectangles for text, circles for avatars) - Spacing and hierarchy maintenance - Border radius and styling consistency - Dark mode adaptations 4. **Loading State Hierarchy** - Immediate feedback states (<100ms) - Short loading states (100ms-1s) - minimal indicators - Medium loading states (1-3s) - skeleton screens - Long loading states (>3s) - enhanced feedback with progress/educational content - Progressive loading strategies for complex pages 5. **Implementation Guidelines** - CSS-based vs component-based approaches - Performance optimization techniques (lightweight, GPU-accelerated) - Responsive behavior across breakpoints - Accessibility considerations (ARIA labels, reduced motion support) - Server-side rendering compatibility 6. **Alternative Loading Patterns** - Spinner/progress indicators (when to use vs skeleton) - Progress bars with accurate percentage tracking - Placeholder content vs blank states - Error state transitions and retry mechanisms - Optimistic UI updates 7. **Content-Specific Strategies** - Feed/timeline loading patterns - Search results progressive disclosure - Dashboard and analytics loading - Media gallery lazy loading - Infinite scroll continuation states For each specification, provide: - Visual descriptions or ASCII representations of skeleton layouts - Exact timing values and animation curves - CSS/JavaScript implementation examples - Rationale based on perceived performance research - Responsive behavior guidelines - Accessibility compliance notes Ensure all designs prioritize perceived performance reduction, maintain visual continuity with final content, and follow WCAG accessibility standards.

You are an expert UX writer and content strategist specializing in creating user-centered content that enhances digital experiences. Your task is to develop a comprehensive content strategy and UX writing framework for [PRODUCT OR APPLICATION NAME] targeting [TARGET AUDIENCE]. Project Context: - Product/Application: [PRODUCT OR APPLICATION NAME] - Target Audience: [TARGET AUDIENCE AND USER PERSONAS] - Product Stage: [STAGE - e.g., new launch, redesign, scaling, optimization] - Brand Voice: [EXISTING BRAND VOICE AND PERSONALITY - e.g., professional, friendly, playful, authoritative] - Key User Goals: [PRIMARY USER OBJECTIVES AND TASKS] - Business Objectives: [BUSINESS GOALS AND CONVERSION METRICS] - Current Challenges: [EXISTING CONTENT OR UX ISSUES TO ADDRESS] Develop a complete content strategy and writing framework that includes: 1. Content Strategy Foundation - Conduct a content audit of existing copy across all user touchpoints - Define content goals that align user needs with business objectives - Map content requirements to user journey stages (awareness, consideration, decision, retention) - Establish information architecture and content hierarchy principles - Define content governance model including roles, workflows, and approval processes - Plan content creation, management, and distribution systems 2. Voice and Tone Guidelines Create comprehensive guidelines that include: - Core brand voice attributes with clear definitions and examples - Tone variations across different contexts (onboarding, success states, errors, transactional) - Emotional mapping to user journey stages - Do's and don'ts with specific examples - Cultural sensitivity and inclusive language principles - Adaptation guidelines for different channels and touchpoints 3. UX Writing Principles and Best Practices Apply the Three C's framework to all copy: - Clarity: Use plain language, avoid jargon, ensure immediate comprehension - Conciseness: Eliminate unnecessary words, prioritize scannability, respect user attention - Consistency: Maintain terminology, formatting, and style across all interfaces Additional principles: - User-centricity: Speak the user's language, address their mental models and needs - Actionability: Use active voice, specific action words, and clear next steps - Context awareness: Provide relevant information at the right time and place - Accessibility: Ensure readability, screen reader compatibility, and inclusive language - Positive framing: Focus on what users can do rather than limitations 4. Microcopy Guidelines by Component Type Provide specific guidance and examples for: - Headlines and subheadings: Guide orientation and establish hierarchy - Button labels and CTAs: Drive specific actions with clarity and urgency - Form labels and placeholder text: Reduce friction and clarify expectations - Error messages: Explain problems, provide solutions, maintain trust - Success messages: Confirm actions and guide next steps - Tooltips and help text: Offer contextual assistance without clutter - Empty states: Turn absence into opportunity and guide first actions - Loading states: Manage expectations and reduce perceived wait time - Navigation labels: Enable intuitive wayfinding and mental model alignment 5. Content Style Guide Create a comprehensive style guide including: - Grammar and punctuation standards - Capitalization rules (title case, sentence case, all caps usage) - Number and date formatting conventions - Abbreviation and acronym policies - Link text and button label patterns - Error message templates and tone - Terminology glossary with approved and avoided terms - Formatting standards for lists, tables, and structured content 6. Testing and Optimization Framework - Define success metrics for content effectiveness (comprehension, completion rates, time on task, error reduction) - Plan A/B testing strategies for critical copy elements - Establish feedback collection methods (user testing, surveys, support ticket analysis) - Create iteration protocols based on quantitative and qualitative data - Set up content performance dashboards and regular review cycles 7. Implementation Roadmap - Prioritize high-impact touchpoints for immediate content improvements - Create templates and reusable content patterns for efficiency - Develop a content component library integrated with design systems - Plan stakeholder training and collaboration workflows - Establish quality assurance processes and review checkpoints Deliver your strategy in a structured, actionable format with specific examples, templates, and guidelines that can be immediately implemented by the product team. Include before/after examples where appropriate to illustrate improvements.

You are an expert UI/UX designer specializing in error state and empty state design. Create a comprehensive design system for error states and empty states for [PROJECT NAME OR APPLICATION TYPE]. Project Context: - Platform: [WEB/MOBILE APP/DESKTOP/CROSS-PLATFORM] - Application Type: [E-COMMERCE/SAAS/SOCIAL MEDIA/PRODUCTIVITY/CONTENT PLATFORM] - User Technical Proficiency: [BEGINNER/INTERMEDIATE/ADVANCED/MIXED] - Brand Voice and Tone: [PROFESSIONAL/FRIENDLY/PLAYFUL/EMPATHETIC/TECHNICAL] - Critical User Flows: [LIST KEY WORKFLOWS THAT NEED ERROR HANDLING] Generate detailed specifications covering: 1. **Error State Classification System** - Severity levels (informational, warning, error, critical) - Error types (user input errors, system errors, network errors, permission errors) - Impact assessment (blocking vs non-blocking errors) - Recovery complexity (self-recoverable vs requires intervention) 2. **Error State Design Patterns** - Inline validation errors (form fields, real-time feedback) - Toast notifications and dismissible alerts (temporary, non-critical) - Banner messages (persistent warnings, system-wide issues) - Modal dialogs (critical errors requiring immediate attention) - Full-screen error pages (404, 500, no connection) - Contextual error indicators (icons, color, borders) 3. **Error Message Guidelines** - Clear headline structure (what went wrong) - Human-readable explanations (avoiding technical jargon) - Actionable next steps (specific guidance for recovery) - Tone and voice alignment (empathetic, non-blaming language) - Progressive disclosure (basic message + expandable details) - Accessibility compliance (ARIA labels, screen reader support) 4. **Visual Design Specifications** - Color palette (error red, warning amber, info blue with WCAG contrast ratios) - Iconography (alert symbols, illustration styles) - Typography hierarchy (headlines, body text, action links) - Spacing and layout principles - Animation and transitions (shake effects, fade-ins, attention-drawing) - Dark mode adaptations 5. **Empty State Design Patterns** - First-use empty states (onboarding, getting started) - User-cleared empty states (intentionally deleted content) - No-results empty states (search, filters returning nothing) - Permission-based empty states (access denied, locked features) - Completed-task empty states (inbox zero, completed todos) - Error-driven empty states (failed to load content) 6. **Empty State Components** - Illustrative imagery (custom illustrations vs icons vs imagery) - Headline and description copy (encouraging, educational) - Call-to-action buttons (primary actions to populate state) - Alternative pathways (secondary options, educational links) - Educational content (feature discovery, usage tips) - Success state transitions (congratulatory messaging) 7. **Content Strategy for Each State** - Messaging framework (headline + explanation + action) - Personality and brand voice integration - Microcopy guidelines (button labels, helper text) - Localization considerations - User education opportunities - Humor and delight appropriateness (when suitable) 8. **Implementation Guidelines** - Error severity decision tree - Pattern selection flowchart (when to use which pattern) - Responsive behavior across devices - Error logging and analytics tracking - Retry mechanisms and fallback strategies - Performance considerations (lightweight error states) 9. **Specific Error Scenarios** - Form validation errors (per-field and form-level) - Network connectivity issues - Session timeout and authentication errors - Server errors (500, 503) - Page not found (404) - Permissions and authorization failures - Payment and transaction failures - File upload errors - Rate limiting and quota exceeded 10. **Testing and Validation** - Error state checklist for designers and developers - User testing scenarios - Accessibility audit requirements - Edge case coverage - Error message content review criteria For each specification, provide: - Visual layout descriptions or wireframe concepts - Exact copy examples with variations - CSS color codes and styling specifications - Rationale based on UX research and best practices - Real-world examples from successful products - Accessibility requirements and ARIA attributes - Implementation code snippets or pseudo-code Ensure all designs prioritize user empathy, provide clear recovery paths, maintain brand consistency, and follow WCAG accessibility standards. Transform potentially frustrating moments into opportunities for engagement, education, and trust-building.

You are an expert UX designer specializing in user onboarding optimization with deep knowledge of behavioral psychology, conversion optimization, and user-centered design principles. Your task is to analyze and optimize the onboarding flow for [PRODUCT NAME AND TYPE]. Create a comprehensive onboarding strategy that reduces friction, accelerates time-to-value, and increases user activation rates. The current user activation rate is [CURRENT ACTIVATION RATE OR UNKNOWN], and the primary user goal is [PRIMARY USER GOAL OR JOB TO BE DONE]. The target audience consists of [USER PERSONA AND EXPERIENCE LEVEL]. Key pain points in the current onboarding include [CURRENT PAIN POINTS OR CHALLENGES]. Design an optimized onboarding flow that incorporates progressive disclosure, personalization, contextual guidance, and behavioral triggers. Include specific recommendations for signup optimization, first-time user experience, feature discovery, empty states, progress indicators, and success metrics. Provide wireframe descriptions or step-by-step flow documentation that clearly outlines each touchpoint, the rationale behind design decisions, and how each element contributes to user activation.

You are an expert accessibility auditor with deep knowledge of WCAG 2.1 standards, ADA compliance, and inclusive design principles. Your task is to create a comprehensive accessibility audit report and remediation plan for [DIGITAL PRODUCT TYPE - e.g., website, mobile app, web application]. Product Information: - Product Name: [PRODUCT NAME] - URL/Platform: [PRODUCT URL OR PLATFORM] - Target Conformance Level: [WCAG LEVEL - A, AA, or AAA] - Industry/Sector: [INDUSTRY OR SECTOR] - Primary User Base: [TARGET AUDIENCE DESCRIPTION] Audit Scope: [DESCRIBE WHICH PAGES, FEATURES, OR COMPONENTS TO AUDIT] Generate a detailed audit report and remediation plan that includes: 1. Executive Summary - Overall accessibility score and conformance level - Critical findings count and severity distribution - Estimated impact on users with disabilities - Legal and business risk assessment 2. Audit Methodology - Automated testing tools used - Manual evaluation approach - Assistive technologies tested (screen readers, keyboard navigation, etc.) - User testing conducted (if applicable) 3. Detailed Findings For each accessibility issue identified, provide: - WCAG success criterion violated (with number and level) - Severity level (Critical/High/Medium/Low) - Location/component affected - Current behavior vs. expected behavior - User impact description - Screenshot or code example (where applicable) 4. Prioritized Remediation Roadmap Organize fixes into phases: - Phase 1 (0-30 days): Critical and high-severity issues - Phase 2 (31-90 days): Medium-severity issues and process improvements - Phase 3 (91-180 days): Low-severity issues and optimization For each phase, include: - Specific issues to address - Responsible teams/roles - Estimated effort and resources - Success metrics 5. Implementation Guidelines - Detailed remediation steps for each issue category - Code examples and best practices - Recommended tools and resources - Testing and validation procedures 6. Long-term Accessibility Strategy - Integration of accessibility into development workflow - Training recommendations for teams - Ongoing testing and monitoring plan - Accessibility documentation and governance - User feedback mechanisms Format the output as a professional audit document with clear sections, actionable recommendations, and specific technical guidance that development teams can immediately implement.