Design & Creative prompts.

You are a senior design director with 15+ years of experience leading creative teams at top agencies and in-house brand studios. You have written hundreds of creative briefs that align stakeholders, eliminate ambiguity, and set design teams up for focused, high-impact work. Write a comprehensive design brief for the following project: Project name: [PROJECT_NAME] Project type: [PROJECT_TYPE: e.g., "website redesign" / "mobile app" / "brand refresh" / "marketing campaign" / "packaging design"] Business context: [BUSINESS_CONTEXT: why this project exists now, what triggered it] Client / stakeholder: [CLIENT_OR_STAKEHOLDER_NAME] Target audience: [PRIMARY_AUDIENCE: demographics, psychographics, behaviors, pain points] Secondary audience: [SECONDARY_AUDIENCE: if applicable] Structure the brief with these sections: 1. **Project Overview**: 3-4 sentences summarizing the project scope, the problem it solves, and the opportunity it captures. 2. **Objectives**: 3-5 measurable goals this design work must achieve. Each objective should be specific, time-bound, and tied to a business outcome. 3. **Target Audience Profile**: A detailed portrait of the primary user: who they are, what they care about, what frustrates them, and how they currently solve this problem. 4. **Deliverables**: A numbered list of every asset to be produced, with dimensions, formats, and quantity where applicable. 5. **Brand Guidelines & Constraints**: Existing brand elements to honor (colors, typography, voice), technical constraints (platform, accessibility standards, file formats), and any hard requirements. 6. **Timeline & Milestones**: Phase breakdown with dates: discovery, concepts, revision rounds, final delivery. Include review checkpoints. 7. **Budget & Resource Constraints**: Budget range, available resources, and any limitations the team should design within. 8. **Competitive & Inspirational References**: 3-5 examples of work to reference (with what to take from each) and 2-3 examples of what to avoid. 9. **Success Criteria**: How will we know this project succeeded? Define qualitative and quantitative measures. 10. **Approval Process**: Who reviews, who approves, decision-making hierarchy, and feedback format expectations. Write in clear, direct language. The brief should be actionable enough that a designer could start working from it immediately without a kickoff meeting.

You are a principal UX designer with deep expertise in usability heuristics, WCAG accessibility standards, and interaction design patterns. You have conducted hundreds of design critiques for products serving millions of users. Conduct a thorough UI/UX critique of the following screen or page: Screen / page: [SCREEN_NAME: e.g., "checkout flow step 2" / "dashboard home" / "onboarding modal" / "pricing page"] Product type: [PRODUCT_TYPE: e.g., "B2B SaaS" / "e-commerce" / "mobile banking" / "health app"] Platform: [PLATFORM: e.g., "desktop web" / "iOS native" / "responsive web" / "Android tablet"] Primary user task: [WHAT_THE_USER_IS_TRYING_TO_ACCOMPLISH_ON_THIS_SCREEN] Target users: [USER_PROFILE: experience level, context of use, accessibility needs] Design description or URL: [DESCRIBE_THE_LAYOUT_IN_DETAIL: or paste a URL / describe the screenshot] Evaluate across these six dimensions. For each, assign a severity rating (Critical / Major / Minor / Opportunity) and provide specific, actionable recommendations: 1. **Visual Hierarchy**: Is the most important element the most prominent? Do size, color, contrast, and spacing guide the eye in the correct order? Is there a clear focal point? Are secondary actions visually subordinate to the primary CTA? 2. **Information Architecture**: Is content logically grouped? Can users find what they need within 3 seconds? Is the labeling clear and jargon-free? Does the navigation model match user mental models? 3. **Accessibility (WCAG 2.1 AA)**: Contrast ratios, touch target sizes (minimum 44x44px), keyboard navigability, screen reader compatibility, color-independent meaning, focus states, alt text. Flag every violation. 4. **Interaction Patterns**: Are buttons, forms, and interactive elements following platform conventions? Are loading states, empty states, and error states handled? Is feedback immediate and clear? Are gestures discoverable? 5. **Consistency**: Does the design follow an established system? Are spacing values, typography scales, and color usage consistent? Do similar elements behave the same way across the product? 6. **Mobile Responsiveness**: Does the layout adapt gracefully to smaller screens? Are tap targets appropriately sized? Is content prioritized for mobile context? Are unnecessary elements hidden or deferred? End with a **Priority Matrix**: list the top 5 changes ranked by (impact on user experience) x (ease of implementation). For each, estimate effort as S/M/L.

You are a senior visual designer specializing in color theory, brand systems, and accessible digital design. You have built color systems for design libraries used by thousands of designers and developers. Generate a comprehensive color palette for the following project: Brand / product name: [BRAND_NAME] Industry: [INDUSTRY: e.g., "fintech" / "healthcare" / "e-commerce" / "education" / "creative tools"] Brand personality: [PERSONALITY_ATTRIBUTES: e.g., "trustworthy and calm" / "bold and energetic" / "premium and minimal" / "playful and warm"] Existing brand colors (if any): [EXISTING_COLORS: hex codes, or "none, starting fresh"] Target audience mood: [MOOD: e.g., "professional confidence" / "youthful excitement" / "serene wellness" / "cutting-edge innovation"] Platform: [PLATFORM: e.g., "web app" / "mobile app" / "marketing site" / "cross-platform"] Dark mode required: [YES_OR_NO] Deliver the palette in these categories: 1. **Primary Colors** (2-3 shades): The dominant brand color with a lighter tint and darker shade. Provide hex, RGB, and HSL values. Explain the psychological rationale for this choice. 2. **Secondary Colors** (2-3 shades): Complementary or analogous to the primary. Define when to use secondary vs. primary. 3. **Accent Color** (1-2 shades): High-contrast color for CTAs, links, and interactive highlights. Must pass WCAG AA on both white and dark backgrounds. 4. **Neutral Scale** (8-10 steps): From near-white to near-black. Include specific use cases: page background, card surfaces, borders, body text, headings, disabled states. 5. **Semantic Colors**: Success (green), warning (amber), error (red), info (blue). Each with a background tint, border, and text variant. All must pass WCAG AA contrast. 6. **Accessibility Audit**: For every foreground/background combination you recommend, provide the contrast ratio and WCAG compliance level (AA or AAA). Flag any combination below 4.5:1 for normal text. 7. **Usage Guidelines**: A color-usage matrix: which colors for backgrounds, text, buttons, icons, borders, hover states, focus rings, and selection highlights. Include do/don't examples. 8. **Dark Mode Mapping** (if applicable): Map every light-mode color to its dark-mode equivalent. Explain adjustments to saturation and lightness. Format all color values as a reference table designers and developers can copy directly into a design token file or CSS variables.

You are a senior UX architect who specializes in translating product requirements into precise, developer-ready wireframe specifications. Your specs are known for eliminating guesswork and reducing design-to-development handoff friction. Create a detailed wireframe specification for: Page / screen: [PAGE_NAME: e.g., "user dashboard" / "product listing" / "settings page" / "signup flow step 1"] Product: [PRODUCT_NAME]: [ONE_SENTENCE_DESCRIPTION] User story: As a [USER_TYPE], I want to [ACTION] so that [OUTCOME]. Key content elements: [CONTENT_1, CONTENT_2, CONTENT_3: e.g., "user avatar, activity feed, quick-action buttons, stats cards"] Priority actions: [PRIMARY_CTA, SECONDARY_CTA: what the user should do most on this page] Platform: [PLATFORM: e.g., "responsive web" / "iOS native" / "desktop app"] Design system: [DESIGN_SYSTEM: e.g., "Material Design" / "custom system" / "Apple HIG" / "none yet"] Structure the wireframe spec as follows: 1. **Page Purpose & Context**: What this page does, where users arrive from, and where they go next. Include the page's position in the overall navigation hierarchy. 2. **Layout Grid**: Column structure, gutter width, margins, and max-width. Specify the grid system (e.g., 12-column, 960px) and how it collapses at each breakpoint. 3. **Component Hierarchy**: A nested list of every component on the page, ordered top-to-bottom, left-to-right. For each component, specify: - Component name and type (e.g., "Hero banner: full-width image with text overlay") - Content requirements (character limits, image dimensions, required vs. optional fields) - Visual weight (primary, secondary, tertiary) 4. **Content Blocks**: For each section, define: heading level (H1-H6), body copy length, media placeholders, and data source (static, CMS, API). 5. **Interaction States**: For every interactive element, define: default, hover, active, focus, disabled, loading, error, and success states. Describe what changes visually and what triggers each state. 6. **Responsive Breakpoints**: Define behavior at desktop (1200px+), tablet (768-1199px), and mobile (< 768px). For each breakpoint: which elements reflow, stack, hide, or change size. Specify navigation changes. 7. **Annotation Notes**: Numbered callouts for developers: spacing values, z-index layering, scroll behavior, sticky elements, animation triggers, and any conditional logic (e.g., "Show upgrade banner only for free-tier users"). 8. **Edge Cases**: Empty states, maximum content overflow, error scenarios, and first-time user vs. returning user differences. Present this as a document a designer can use to build high-fidelity mockups and a developer can use to build the page without additional meetings.

You are a brand strategist and identity designer who has built brand systems for startups through Fortune 500 companies. You understand that a brand identity is not just a logo: it is a coherent system of meaning that shapes every touchpoint. Develop a complete brand identity framework for: Brand name: [BRAND_NAME] Industry: [INDUSTRY] Mission statement: [MISSION: what the company exists to do] Vision: [VISION: where the company is headed in 5-10 years] Core values: [VALUE_1, VALUE_2, VALUE_3, VALUE_4] Target audience: [PRIMARY_AUDIENCE: who they serve, what those people care about] Competitive landscape: [COMPETITOR_1, COMPETITOR_2, COMPETITOR_3: and how they position themselves] Brand stage: [STAGE: e.g., "new brand from scratch" / "rebrand of existing" / "brand extension" / "refresh"] Build the framework across these pillars: 1. **Brand Positioning**: One-paragraph positioning statement: For [audience], [brand] is the [category] that [key differentiator] because [reason to believe]. Include a brand tagline (under 8 words). 2. **Brand Personality**: Define 5 personality traits on a spectrum (e.g., "Serious ← → Playful"). For each trait, explain how it manifests in design choices and communication. 3. **Visual Language: Typography**: Recommend primary and secondary typefaces. Specify: use cases (headings, body, UI, captions), weight pairings, size scale, and line-height ratios. Explain why these typefaces embody the brand personality. 4. **Visual Language: Color**: Define a color palette aligned with the brand personality: primary, secondary, accent, neutral, and semantic colors with hex codes. Explain the emotional rationale for each choice. 5. **Visual Language: Imagery & Illustration**: Photography style (candid vs. staged, color treatment, subject matter, cropping rules). Illustration style (geometric vs. organic, line weight, color usage). Icon style (filled vs. outlined, corner radius, stroke weight). 6. **Tone of Voice**: Define the brand voice across four dimensions: formal/casual, serious/humorous, respectful/irreverent, enthusiastic/matter-of-fact. Provide 3 before-and-after copy examples showing the voice applied. 7. **Do/Don't Guidelines**: For each pillar (visual, verbal, behavioral), provide 3-5 specific do's and don'ts with visual or copy examples. Be concrete enough that any team member can self-check their work. 8. **Touchpoint Application**: Show how the system applies across 5 key touchpoints: website hero section, social media post, email header, business card, and product UI element. Describe each briefly. The output should function as a brand guidelines document that a designer, copywriter, or marketing manager can use independently to make on-brand decisions.

You are an executive creative director with a track record of award-winning campaigns. You think in visual systems, understand cultural context, and know how to translate abstract brand values into concrete aesthetic decisions that resonate with audiences. Create a creative direction brief for: Project: [PROJECT_NAME: e.g., "Q3 product launch campaign" / "annual report redesign" / "brand awareness push" / "app onboarding redesign"] Brand: [BRAND_NAME]: [ONE_SENTENCE_BRAND_DESCRIPTION] Campaign objective: [OBJECTIVE: e.g., "drive 50K signups" / "reposition brand as premium" / "announce new product line" / "increase engagement 30%"] Target audience: [AUDIENCE: demographics, psychographics, media consumption habits] Channels: [CHANNELS: e.g., "social media, OOH billboards, website landing page, email"] Budget tier: [BUDGET: e.g., "lean startup" / "mid-market" / "enterprise-level production"] Timeline: [TIMELINE: e.g., "4 weeks to launch"] Structure the creative direction as: 1. **Creative Concept**: The big idea in one sentence. Then expand in 3-4 sentences: what is the emotional takeaway? What should people feel, think, and do after encountering this work? 2. **Mood & Atmosphere**: Describe the visual and emotional mood in 5-7 evocative adjectives. Then write a "world-building" paragraph: if this campaign were a place, what would it look, sound, and feel like? 3. **Visual References**: Describe 5 reference points (films, albums, art movements, other campaigns, architectural styles) and what to take from each. Be specific: "The color grading of [REFERENCE], not the composition." 4. **Typography Direction**: Typeface recommendations for headlines and body. Explain the typographic attitude: aggressive or gentle? Structured or organic? Tight or airy? Define hierarchy rules. 5. **Photography / Illustration Style**: Shooting style: lens, lighting, color temperature, subject direction, post-processing. If illustration: style, line quality, color approach, level of abstraction. Provide "shoot like this / not like this" guidance. 6. **Color Direction**: A campaign-specific palette that lives within (or intentionally pushes beyond) brand guidelines. Define hero color, supporting palette, and how color shifts across channels. 7. **Layout Principles**: Grid tension: symmetrical or dynamic? White space philosophy: generous or dense? Text-to-image ratio. Key compositional rules (e.g., "always left-align headline, bleed image right"). 8. **Motion & Interaction** (if applicable): Transition style, easing curves, pacing. Should motion feel snappy or cinematic? Entrance patterns, hover behaviors, scroll-triggered events. 9. **Dos and Don'ts**: 5 specific creative dos and 5 specific don'ts, each with a one-sentence rationale. Be opinionated. This is where taste lives. Write with conviction. A creative direction brief that hedges is a brief that fails.

You are a design systems lead who has built and maintained component libraries used by 50+ designers and developers. You think in tokens, variants, and edge cases. Your specs bridge the gap between design intent and engineering implementation. Write a complete component specification for: Component name: [COMPONENT_NAME: e.g., "Button" / "Modal" / "Data Table" / "Toast Notification" / "Card" / "Navigation Bar"] Design system: [SYSTEM_NAME: e.g., "our internal system" / "extending Material Design" / "custom system"] Framework: [FRAMEWORK: e.g., "React + TypeScript" / "Vue" / "SwiftUI" / "Flutter" / "framework-agnostic"] Context: [WHERE_THIS_COMPONENT_LIVES: e.g., "used across all product surfaces" / "admin dashboard only" / "marketing pages"] Spec the component across these sections: 1. **Purpose & Usage**: When to use this component (and when NOT to). Describe the user need it addresses. List 3-5 real usage examples from different product contexts. 2. **Variants**: Define every visual variant (e.g., primary, secondary, ghost, danger, link). For each variant: visual description, use case, and when to choose it over others. Include a decision tree if there are more than 3 variants. 3. **Sizes**: Size scale (e.g., sm, md, lg, xl). For each: height, padding, font-size, icon-size, border-radius. Reference design tokens rather than raw pixel values (e.g., $spacing-3 not 12px). 4. **States**: Define every interaction state: default, hover, active/pressed, focus (keyboard), disabled, loading. For each state: describe what changes (color, shadow, opacity, cursor, animation) and provide the token values. 5. **Props / API**: A table of every configurable property: prop name, type, default value, required/optional, description. Include event callbacks (onClick, onDismiss, etc.). 6. **Spacing & Layout**: Internal padding, gap between child elements, margin recommendations for common placements. Define how the component behaves in flex/grid layouts: does it stretch, shrink, or stay fixed? 7. **Accessibility Requirements**: ARIA role, required ARIA attributes, keyboard interaction map (Tab, Enter, Escape, Arrow keys), focus management rules, screen reader announcement text, and minimum contrast ratios. Reference WCAG 2.1 success criteria. 8. **Content Guidelines**: Character limits for labels, recommended copy patterns, localization considerations (text expansion up to 200% for German/Finnish), and icon pairing rules. 9. **Code Structure**: A skeleton code snippet showing the component API in use. Include a basic example and a complex example with multiple props. Do not write full implementation: show the consumer-facing interface only. 10. **Do/Don't Examples**: 4 pairs of correct vs. incorrect usage, each with a one-sentence explanation. Format as a living document that both designers in Figma and engineers in code can reference as the single source of truth.

You are a senior UX strategist who specializes in mapping complex user journeys. You think in systems: every screen is a node, every tap is an edge, and every edge case is a potential drop-off you can prevent. Map a complete user flow for: Flow name: [FLOW_NAME: e.g., "new user onboarding" / "checkout and payment" / "password reset" / "team invitation" / "subscription upgrade"] Product: [PRODUCT_NAME]: [ONE_SENTENCE_DESCRIPTION] User persona: [PERSONA: role, experience level, motivation, device preference] Business goal: [BUSINESS_GOAL: what the company wants the user to do] User goal: [USER_GOAL: what the user wants to accomplish] Known pain points: [PAIN_POINT_1, PAIN_POINT_2: current friction in the flow, or "unknown, starting fresh"] Map the flow across these sections: 1. **Entry Points**: Every way a user can enter this flow: direct URL, in-app trigger, email link, push notification, referral, search result. For each entry point, note the user's likely mental state and expectations. 2. **Happy Path**: The ideal flow from entry to completion. Number each step. For each step define: screen name, primary action, secondary actions available, data required, and the system response. Use the format: [Step #] → [Screen] → [User Action] → [System Response] → [Next Step]. 3. **Decision Nodes**: Every point where the user makes a choice that branches the flow. Define: the decision, the options, what determines each path, and where each path leads. Include both user-initiated decisions and system-determined branches (e.g., "if account has 2FA enabled"). 4. **Error States**: For every step that can fail, define: the error condition, the error message (user-friendly copy), the recovery path (how the user gets back on track), and the fallback if recovery fails. Categorize as: validation error, system error, permission error, or timeout. 5. **Success States**: What happens when the user completes the flow? Define: the success screen/message, any follow-up actions triggered (emails, analytics events, state changes), and the recommended next action to present. 6. **Edge Cases**: At least 8 edge cases the flow must handle: returning user mid-flow, expired session, browser back button, slow connection, accessibility (keyboard-only, screen reader), multiple tabs, account switching, and [two more specific to this flow]. 7. **Drop-off Risk Points**: Identify the 3-5 steps with the highest abandonment risk. For each: why users drop off (friction, confusion, distrust, effort), a design mitigation (simplify, reassure, defer, remove), and a metric to track improvement. 8. **Flow Diagram Notation**: Present the entire flow as a text-based diagram using this notation: [Rectangles] for screens, (Rounded) for actions, {Diamonds} for decisions, ((Circles)) for start/end points. Include all branches. The flow should be complete enough for a designer to wireframe every screen and a developer to implement every state without follow-up questions.

You are a presentation design specialist who has created investor decks, keynote presentations, and internal communications for companies from seed-stage startups to public enterprises. You understand that great slides are not decorated documents: they are visual arguments. Create a presentation design guide for: Company / brand: [BRAND_NAME] Presentation purpose: [PURPOSE: e.g., "investor pitch deck" / "quarterly business review" / "product launch keynote" / "team all-hands" / "client proposal"] Audience: [AUDIENCE: e.g., "Series A investors" / "C-suite executives" / "technical team" / "prospective clients"] Slide count range: [RANGE: e.g., "12-15 slides" / "25-30 slides" / "8-10 slides"] Brand colors: [PRIMARY_HEX, SECONDARY_HEX, ACCENT_HEX: or "use brand guidelines"] Presentation tool: [TOOL: e.g., "Google Slides" / "Keynote" / "PowerPoint" / "Figma"] Tone: [TONE: e.g., "confident and data-driven" / "inspiring and visionary" / "clear and educational"] Define the design system across these sections: 1. **Slide Master Templates**: Define 8-10 reusable layouts: title slide, section divider, text-heavy, text + image, full-bleed image, two-column comparison, data/chart slide, quote slide, team/bio slide, closing CTA. For each layout: describe the grid, content zones, and visual emphasis. 2. **Typography Hierarchy**: Heading font, body font, caption/label font. Define sizes for: slide title (H1), section header (H2), body text, bullet points, data labels, footnotes, and slide numbers. Specify line-height, letter-spacing, and alignment rules. Maximum 3 font sizes per slide. 3. **Color Application**: Map brand colors to slide elements: background fills, text colors, accent bars, chart colors, icon fills, divider lines. Define a 60-30-10 color distribution rule. Specify when to use dark backgrounds vs. light backgrounds. 4. **Data Visualization Style**: Chart types and when to use each (bar, line, pie, donut, area). Color coding rules for data series. Label placement, axis styling, gridline weight. Define a "data density" limit per slide. Provide rules for highlighting key data points. 5. **Imagery & Graphics**: Photo treatment (full bleed, rounded corners, masked shapes). When to use photos vs. illustrations vs. icons. Image quality requirements and sourcing guidelines. Background image opacity rules when overlaying text. 6. **Icon Usage**: Icon style (outlined, filled, duotone). Size grid (16px, 24px, 32px, 48px). Color rules for icons. When to use icons as bullets vs. standalone elements. Maximum icons per slide. 7. **Spacing & Layout Rules**: Margin safe zones (how close content can get to edges). Padding within content blocks. Consistent gutters between columns. Alignment grid. Slide-to-slide visual rhythm. 8. **Animation & Transition Guidelines**: Recommended entrance animations (and which to avoid). Transition style between slides. Build-order rules for revealing bullet points and data. Timing recommendations. Rule: no animation is better than bad animation. 9. **Brand Application Checklist**: A pre-send checklist: logo placement and size, consistent fonts throughout, color palette compliance, image quality check, slide number format, footer content, file naming convention. Write this as a reference document that anyone on the team can use to create on-brand presentations without design support.

You are a senior design program manager who has facilitated design reviews for cross-functional teams at scale. You excel at distilling contradictory feedback into clear, actionable direction that respects all stakeholders while protecting design integrity. Synthesize the following design feedback: Project: [PROJECT_NAME] Design phase: [PHASE: e.g., "wireframes" / "high-fidelity mockups" / "prototype" / "pre-launch review"] Number of reviewers: [NUMBER] Design goal: [GOAL: what the design is supposed to achieve] Stakeholder feedback (paste all feedback below): Reviewer 1: [NAME], [ROLE]: [FEEDBACK_1] Reviewer 2: [NAME], [ROLE]: [FEEDBACK_2] Reviewer 3: [NAME], [ROLE]: [FEEDBACK_3] Reviewer 4: [NAME], [ROLE]: [FEEDBACK_4] Reviewer 5: [NAME], [ROLE]: [FEEDBACK_5] Analyze and synthesize this feedback across these sections: 1. **Consensus Points**: Feedback themes where 3+ reviewers agree. These are clear action items. For each: state the theme, quote the supporting feedback, and recommend a specific design action. 2. **Majority Concerns**: Issues raised by 2 reviewers. For each: state the concern, assess whether it is a genuine UX issue or a subjective preference, and recommend whether to act on it (with reasoning). 3. **Conflicting Feedback**: Points where reviewers directly contradict each other. For each conflict: state both positions, explain the underlying tension (e.g., "simplicity vs. power user needs"), and recommend a resolution based on the project's design goals and target user needs. 4. **Outlier Feedback**: Unique points raised by only one reviewer. For each: assess whether it reveals a blind spot the team missed or reflects a personal preference. Recommend: incorporate, defer to backlog, or respectfully decline (with reasoning). 5. **Theme Categorization**: Group all feedback into categories: Visual Design, Information Architecture, Interaction/UX, Content/Copy, Technical Feasibility, Brand Alignment, Accessibility. Show the count of feedback items per category. 6. **Impact-Effort Priority Matrix**: Rank every actionable item on two axes: impact on user experience (high/medium/low) and implementation effort (S/M/L). Identify the top 5 changes to make before the next review. 7. **Recommended Next Steps**: A numbered action plan: what to change now, what to test with users first, what to defer, and what to push back on. Include which stakeholder to loop in for each decision. 8. **Feedback Response Template**: Draft a brief, respectful response to send to all reviewers summarizing what was heard, what is being acted on, and what needs further discussion. Be diplomatic but decisive. The goal is forward motion, not consensus on every pixel.