AI Prompts for Designers

Copy-paste AI prompts for graphic and UX designers, creative briefs, concept descriptions, client emails, naming and ideation, and presenting design work.

Who These Prompts Are For

Graphic designers, brand designers, UX/UI designers, creative directors, and freelance designers who want to spend more time designing and less time writing briefs, client emails, and proposals.

How to Use These Prompts

Copy any prompt and paste it into ChatGPT, Claude, or another AI tool. Replace the brackets [ ] with your specific details.

Brief and Strategy Prompts

Write a creative brief:

Write a creative brief for a [project type — brand identity / logo / packaging / website / campaign].

What the client told me: [paste your meeting notes or call summary]

Structure with:
- Project overview (2–3 sentences)
- Business context and objective
- Target audience (with what we know about them)
- Design objectives (what the design should accomplish)
- Tone and personality (3–5 descriptors)
- Visual direction (styles, references, feelings to aim for)
- What to avoid
- Deliverables
- Timeline

Where information is missing, mark as [TO CONFIRM WITH CLIENT].

Generate brand personality descriptors:

Generate brand personality descriptors for a [type of brand].

What they do: [describe]
Their target audience: [describe]
How they want to be perceived: [describe]
Brands they admire (if any): [list]
What they don't want to feel like: [list]

Produce:
- 5 tone-of-voice adjectives (e.g., bold, understated, playful)
- 3 "is / is not" brand contrasts (e.g., "Direct, not aggressive")
- A one-sentence brand voice statement

Concept and Pitch Prompts

Write concept descriptions for a pitch:

Write presentation descriptions for [number] design concepts.

Client goal: [brief summary]

Concept 1 name: [name]
Visual direction: [describe colors, feel, mood]

Concept 2 name: [name]  
Visual direction: [describe]

Concept 3 name (if applicable): [name]
Visual direction: [describe]

For each concept, write:
- A 2–3 sentence description of the direction and thinking
- How it connects to the client's goal
- Who in their audience it would resonate with most
Tone: confident and clear — not overly technical.

Describe a moodboard:

Write a brief moodboard description to accompany a design direction.

Direction name: [name you've given this concept]
What the moodboard references evoke: [materials, era, colors, feelings]
Strategic intent: [what this direction communicates about the brand]

Write 3–4 sentences that help a non-designer understand what they're looking at and why it's right for them.

Generate naming options:

Generate naming ideas for [brand / product / service / campaign].

What it is: [describe]
Who it's for: [target audience]
Tone / personality: [describe the feel]
Names to avoid or that are taken: [list if any]

Generate:
- 10 name ideas (mix real words, invented words, and combinations)
- 5 potential taglines
- For each name, one sentence on the thinking behind it

Note: all names require trademark search before recommendation to a client.

Client Communication Prompts

Respond to client feedback:

Write a professional response to this client feedback.

Their feedback: "[paste their message]"
My honest reaction: [do you agree / partially agree / think they've misunderstood?]
What I want to communicate: [what you actually want to say]

Tone: professional, confident, and solution-focused. Not defensive, but not capitulating on things I believe are right.
Under 200 words.

Present a price increase:

Write a message to a long-term client explaining a rate increase.

New rate: [amount]
Effective date: [date]
Reason (keep it simple): [e.g., annual adjustment, increased scope, market alignment]

Tone: direct and confident — not apologetic. Frame it as a normal business practice, not a big deal.
Under 150 words.

Write a project proposal:

Write a project proposal for [project type] for [type of client].

Scope: [what I'll design — deliverables]
Timeline: [rough dates]
Investment: [price]
My process: [brief description of how you work — rounds of feedback, how decisions get made]

Tone: professional but human. One page maximum. Should feel like a real conversation, not a legal document.

Process and Documentation Prompts

Write design system documentation:

Write documentation for a [component / design token / pattern] in our design system.

What it is: [describe]
When to use it: [use cases]
When not to use it: [anti-patterns]
Variations: [list if applicable]
Accessibility considerations: [if applicable]

Write it clearly enough that a developer or another designer can use it correctly without asking questions.

Write a UX research report summary:

Summarize these UX research findings into an executive summary for stakeholders.

Research method: [usability testing / interviews / surveys]
Number of participants: [number]
Key findings: [paste your raw notes or findings]

Create:
- Top 3 insights (what we learned that's most important)
- Key usability issues found (with severity)
- Recommended design changes based on the findings
- What to test next

Audience: non-UX stakeholders who need to make decisions, not read a full research report.