#UX.

Act as an Event Tech Product Manager. We are building a custom app for [Insert Event Name]. 1. Outline the 'Core Features' (Agenda, Speaker bios, Live Polling, Networking). 2. Design the 'Push Notification' schedule (Reminders, Sponsor ads, Change alerts). 3. Create a UX flow for the 'Networking Matchmaker' feature. 4. Propose how to gamify the app to ensure 90%+ download and usage rates. 5. Suggest an 'Accessibility Mode' for the app.

Act as a UX Researcher. Audit the registration flow for my event. 1. Identify common 'Drop-off Points' in the ticket-buying process. 2. Suggest 5 ways to simplify the form (e.g., social login, fewer fields). 3. Draft the 'Confirmation Email' and 'Ticket PDF' to be as clear as possible. 4. Propose an 'Abandon Cart' email sequence for people who started registration but didn't pay.

Act as a Concierge Director. Design an 'Ultra-Premium' experience for 50 VIP attendees at a larger conference. Include: 1. A dedicated 'VIP Lounge' design. 2. Exclusive 'Meet-and-Greet' sessions with speakers. 3. A high-end 'Gift Bag' (SWAG) list. 4. Priority check-in and seating logistics. 5. A post-event 'Thank You' gift strategy. The goal is to make these attendees feel like the event’s most important stakeholders.

Act as an Audience Engagement Expert. Propose 5 ways to keep attendees engaged and networking during [Insert Event Type]. 1. A gamification idea (e.g., scavenger hunt via the event app). 2. A 'Curated Networking' format (e.g., speed-dating style). 3. Interactive polling strategies for live sessions. 4. Design of a 'Networking Lounge' that encourages conversation. 5. Suggested prizes or incentives for active participants.

Act as a Level Designer. I will describe a level: [Describe Layout]. Audit it for 'Flow and Pacing.' 1. Identify 'Bottlenecks' where players might get stuck. 2. Suggest 'Visual Language' to guide the player (Lighting, leading lines). 3. Propose 'High/Low Tension' areas to manage the player's heart rate. 4. Suggest 'Shortcut' unlocks for backtracking. 5. Detail the 'Secret Area' placement strategy.

Act as a Horror Game Specialist. We are building a scene in [Insert Setting, e.g., an Abandoned Asylum]. 1. Describe the 'Atmospheric Layers' (Lighting, Soundscape, Particle effects). 2. Design a 'Tension Curve' leading up to a scare. 3. Suggest 3 'Psychological Tricks' to make the player feel vulnerable (e.g., resource scarcity). 4. Propose a 'Monster Behavior' that is unpredictable. 5. Draft the 'Environmental Storytelling' notes (what the player sees on walls/tables).

Act as an Audio Director. Design the 'Soundscape' for [Insert Game Genre/Environment]. 1. List the 'Core Foley' sounds (Footsteps, Cloth, Interaction). 2. Propose an 'Ambient Loop' (Nature, Mechanical, or Eerie). 3. Design the 'Combat Audio' (Weapon impacts, reloads). 4. Suggest 'Audio Feedback' for UI (Buttons, Success/Failure). 5. Provide technical notes for 'Dynamic Audio' (Sound changing based on room size).

Act as a VR/AR Specialist. Review our design for [Insert Game/App]. 1. Suggest 'Comfort Settings' (Teleport vs. Smooth move). 2. Optimize the 'HUD' for VR (Diegetic vs. Floating). 3. Propose 'Haptic Feedback' triggers. 4. Analyze 'Spatial Audio' placement for immersion. 5. Provide a checklist for 'Sim-Sickness' mitigation.

Act as a Conversion Rate Optimization (CRO) Expert. I will provide the URL or description of my product landing page: [Details]. Audit the page for: 1. Hero Section (Value prop and image). 2. Trust Signals (Reviews, badges, secure checkout). 3. Friction Points (Too much text, hidden shipping costs). 4. Mobile Responsiveness. 5. Checkout Flow. Provide 5 actionable 'Quick Wins' to increase the conversion rate by at least 10%.

You are a Design Systems Lead. Write a technical specification for a [component name, e.g., "Multi-select Dropdown with search"]. This spec will be used by both designers and engineers. Sections: 1) Anatomy — describe every visual part of the component, 2) Visual Properties — tokens for color, spacing, typography, borders, shadows (use placeholder tokens like $surface-default), 3) States — Default, Hover, Focused (with focus-ring spec), Active, Disabled, Loading, Empty, 4) Interactions — click/tap behavior, keyboard navigation (tabbing, arrow keys, Esc), 5) Responsive Behavior — how it scales on mobile vs desktop, 6) Accessibility (A11y) — ARIA roles, attributes, screen reader behavior, touch target sizes, 7) Usage Guidelines — where to use vs where to use an alternative, 8) Edge Cases — long text, no results, many results, error states. Output the spec clearly with headers.