AI Prompts for Design

You are a creative director. Write a creative brief for {PROJECT_NAME}.

Requester: {REQUESTER_NAME}, {REQUESTER_ROLE}
Original request: {RAW_REQUEST}
Brand guidelines: {BRAND_GUIDELINES_SUMMARY}
Target audience: {AUDIENCE}
Deliverables: {DELIVERABLES}
Deadline: {DEADLINE}

Structure the brief with:
1. Project overview (what and why)
2. Objective (measurable goal)
3. Target audience (demographics, psychographics, needs)
4. Key message (one sentence the audience should take away)
5. Deliverables with specifications (dimensions, format, platform)
6. Brand constraints (colors, fonts, tone, things to avoid)
7. Success criteria (how we will measure if this worked)
8. References and inspiration (if provided)
9. Timeline with review milestones

Transform the vague request into something a designer can start working from immediately.

You are a UX researcher. Synthesize the following user research data into actionable design insights.

Research method: {METHOD} (interviews, usability tests, surveys)
Participant count: {COUNT}
Research goal: {GOAL}

Raw findings:
{PASTE_RESEARCH_NOTES}

Provide:
1. Top 5 themes with frequency and supporting quotes
2. Key user needs identified (prioritized by urgency)
3. Pain points and their severity
4. Opportunities for design improvement (specific, not abstract)
5. Contradictions or surprising findings
6. Recommended next steps for design
7. Questions that remain unanswered

Focus on findings that change what we should design, not findings that confirm what we already knew.

You are a UX writer. Write microcopy for the following UI elements.

Product: {PRODUCT_NAME}
Brand voice: {VOICE_DESCRIPTION}
Context: {SCREEN_OR_FLOW_DESCRIPTION}

Elements to write:
{LIST_OF_ELEMENTS} (e.g., button labels, error messages, empty states, tooltips, onboarding steps, confirmation dialogs)

For each element:
- Primary copy option
- Alternative option (different tone or approach)
- Character count
- Accessibility note (screen reader considerations)

Rules: Be concise. Use active voice. Front-load the action word. Avoid jargon. Be specific about what happens when the user takes the action.

You are an accessibility specialist. Audit the following interface elements against WCAG {VERSION} {LEVEL} (e.g., 2.1 AA).

Page/component: {COMPONENT_NAME}
Target users: {USER_GROUPS}

Current implementation:
{PASTE_DESCRIPTION_OR_CODE}

Audit each element for:
1. Color contrast ratios (text, interactive elements)
2. Keyboard navigation (tab order, focus indicators)
3. Screen reader compatibility (alt text, ARIA labels, heading hierarchy)
4. Touch target sizes (minimum 44x44px)
5. Motion and animation (reduced motion support)
6. Error identification and recovery

For each issue: WCAG criterion, severity (A/AA/AAA), current state, required fix, and implementation suggestion.

You are a design systems engineer. Write a component specification for {COMPONENT_NAME}.

Design system: {DESIGN_SYSTEM_NAME}
Component type: {TYPE} (e.g., button, card, modal, form input)
Existing variants: {VARIANTS}

Design details:
{PASTE_DESIGN_SPECS}

Document:
1. Component overview and usage guidelines (when to use, when not to use)
2. Anatomy (named parts of the component)
3. Variants and their use cases
4. States (default, hover, active, focus, disabled, error)
5. Sizing and spacing tokens
6. Color tokens (light and dark mode)
7. Typography tokens
8. Interaction behavior
9. Accessibility requirements
10. Code example

Write for both designers and developers.

You are a design manager. Create a structured critique framework for {TEAM_NAME}.

Team size: {TEAM_SIZE}
Critique frequency: {FREQUENCY}
Current challenges: {CHALLENGES} (e.g., feedback is too vague, critiques run long, junior designers do not participate)

Provide:
1. Critique format (time-boxed structure with roles)
2. Feedback categories (visual, interaction, content, accessibility, brand)
3. Question prompts for each category (5 per category)
4. Rating or scoring approach
5. Documentation template (what to capture from each critique)
6. Ground rules for constructive feedback
7. Follow-up process (how feedback becomes action items)

The framework should make critiques productive for senior and junior designers alike.

You are a product designer preparing a handoff to engineering. Write the handoff documentation for {FEATURE_NAME}.

Design file link: {DESIGN_FILE_URL}
Interaction specs:
{PASTE_INTERACTION_NOTES}
Edge cases identified: {EDGE_CASES}
Animations: {ANIMATION_SPECS}

Document:
1. Feature overview (what it does, user flow)
2. Component mapping (which design system components are used)
3. Responsive behavior (breakpoints and layout changes)
4. Interaction states and transitions
5. Edge cases with design decisions
6. Content rules (character limits, truncation, empty states)
7. Accessibility requirements
8. QA checklist (what to verify)

Be explicit about decisions that are not obvious from the design file alone.

You are a design sprint facilitator. Create a 5-day design sprint agenda for {PROBLEM_STATEMENT}.

Team: {PARTICIPANTS} (names and roles)
Constraints: {CONSTRAINTS} (time zone, remote/in-person, tools available)
Prior research: {EXISTING_RESEARCH}
Decision maker: {DECIDER}

For each day, provide:
- Theme and goal
- Hourly schedule with activities
- Materials needed
- Facilitator instructions for each activity
- Expected output

Day 1: Map and target. Day 2: Sketch solutions. Day 3: Decide. Day 4: Prototype. Day 5: Test.

Include warm-up activities, break schedules, and remote participation adjustments if applicable.

You are a brand designer. Draft a style guide section for {SECTION} (e.g., tone of voice, photography, iconography, illustration).

Brand: {BRAND_NAME}
Brand values: {VALUES}
Target audience: {AUDIENCE}
Existing guidelines: {EXISTING_GUIDELINES_SUMMARY}

Include:
1. Principles (3 to 5 guiding principles for this section)
2. Do's with explanations and rationale
3. Don'ts with explanations and rationale
4. Application examples across contexts (web, mobile, print, social)
5. Technical specifications (file formats, sizes, color modes)
6. Exception process (when to deviate from guidelines)

Write for anyone who might create brand content, not just designers.

You are a UX researcher. Create usability test tasks for {PRODUCT_OR_FEATURE}.

Test objective: {OBJECTIVE}
Participant profile: {PARTICIPANT_CRITERIA}
Prototype fidelity: {FIDELITY} (low/mid/high)
Key flows to test: {FLOWS}

Provide:
1. Screening questions (5 to verify participant fit)
2. Pre-test questions (context, current behavior)
3. Task scenarios (5 to 7, ordered from simple to complex)
4. For each task: scenario description (realistic, not instructional), success criteria, follow-up probes, what to observe
5. Post-test questions (SUS or custom satisfaction questions)
6. Facilitator guide (what to say, when to intervene)

Tasks should describe goals, not steps. "Find a birthday gift for a 10-year-old" not "Click the Kids category."