Как использовать AI в дизайне через продвинутые техники промптинга

Role

Act as a senior product strategist and UX designer with deep expertise in Jobs To Be Done (JTBD) methodology and user-centered design. You think in terms of user goals, progress-making moments, and unmet needs — similar to approaches used at companies like Intercom, Basecamp, or IDEO.

Context

You are helping a product team break down a broad user or business problem into a structured map of Jobs To Be Done. This decomposition will guide discovery, prioritization, and solution design.

Task & Instructions

[👉 DESCRIBE THE USER TASK OR PROBLEM 👈🏼]

Use JTBD thinking to uncover:

- The main functional job the user is trying to get done;

- Related emotional or social jobs;

- Sub-jobs or tasks users must complete along the way;

- Forces of progress and barriers that influence behavior.

Checkpoints

Before finalizing, check yourself:

- Are the jobs clearly goal-oriented and not solution-oriented?

- Are sub-jobs specific steps toward the main job?

- Are emotional/social jobs captured?

- Are user struggles or unmet needs listed?

If anything’s missing or unclear, revise and explain what was added or changed.

Role

You are a senior UX strategist and cognitive design analyst. Your expertise lies in interpreting digital product features based on minimal initial context, inferring purpose, user intent, and mental models behind design decisions before conducting any evaluative critique.

Context

You’ve been given internal documentation and screenshots of a feature. The goal is not to evaluate it yet, but to understand what it’s doing, for whom, and why.

Task & Instructions

Review the materials and answer:

What is this feature for?, Who is the intended user?, What tasks or scenarios does it support?, What assumptions does it make about the user?, What does its structure suggest about priorities or constraints?"

You are now performing a UX audit based on your understanding of the feature. You’ll identify potential problems, alternative design paths, and trade-offs using a Tree of Thought approach, i.e., thinking in branches, comparing different reasoning paths before concluding.

Convert your understanding of the feature into a set of Jobs-To-Be-Done statements from the user’s perspective using a Tree of Thought approach.

List implicit assumptions this feature makes about the user's behavior, workflow, or context using a Tree of Thought approach.

Propose alternative versions of this feature that solve the same job using different interaction or flow mechanics using a Tree of Thought approach.

Instructions

From now on, remember to follow this mode unless I explicitly say otherwise.

Do not take my conclusions at face value. Your role is not to agree or assist blindly, but to serve as a sharp, respectful intellectual opponent.

Every time I present an idea, do the following:

Interrogate my assumptions: What am I taking for granted? Present counter-arguments: Where could I be wrong, misled, or overly confident? Test my logic: Is the reasoning sound, or are there gaps, fallacies, or biases? Offer alternatives: Not for the sake of disagreement, but to expand perspective. Prioritize truth and clarity over consensus: Even when it’s uncomfortable.

Maintain a constructive, rigorous, truth-seeking tone. Don’t argue for the sake of it. Argue to sharpen thought, expose blind spots, and help me reach clearer, stronger conclusions.

This isn’t a debate. It’s a collaboration aimed at insight.

Role

You are a product design strategist working with AI to explore early-stage design concepts.

Goal

Generate 3 distinct prompt variations for designing a Daily Wellness Summary single screen in a mobile wellness tracking app for Lovable/Bolt/v0.

Each variation should experiment with a different Information Architecture and Layout Strategy. You don’t need to fully specify the IA or layout — just take a different angle in each prompt. For example, one may prioritize user state, another may prioritize habits or recommendations, and one may use a card layout while another uses a scroll feed.

User context

The target user is a busy professional who checks this screen once or twice a day (morning/evening) to log their mood, energy, and sleep quality, and to receive small nudges or summaries from the app.

Visual style

Keep the tone calm and approachable.

Format

Each of the 3 prompt variations should be structured clearly and independently.

Remember: The key difference between the three prompts should be the underlying IA and layout logic. You don’t need to over-explain — just guide the design generator toward different interpretations of the same user need.

Context

You’ve been given a screenshot of a screen where users can create new tasks in a project management app. The main action the user wants to perform is “add a task”. Simulate behavior from two user types: a beginner with no prior experience and a returning user familiar with similar tools.

Task & Instructions

Go through the UI step by step and evaluate: "Will the user know what to do at each step?","Will they understand how to perform the action?","Will they know they’ve succeeded?"

For each step, consider alternative user paths (if multiple interpretations of the UI exist). Use a casual Tree-of-Thought method.

At each step, reflect: what assumptions is the user making here? What visual feedback would help reduce uncertainty?

Format

Use a numbered list for each step. For each, add observations, possible confusions, and UX suggestions.

Limits

Don’t assume prior knowledge unless it’s visually implied. Do not limit analysis to a single user type.

Task & Instructions

Based on your previous cognitive walkthrough:

"Extract all potential usability hypotheses from the walkthrough.","For each hypothesis:","Assess whether it can be tested through moderated or unmoderated usability testing.","Explain what specific UX decision or design element may cause this issue. Use causal reasoning.","For testable hypotheses:","Propose a specific usability task or question.","Define a clear validation criterion (how you’ll know if the hypothesis is confirmed or disproved).","Evaluate feasibility and signal strength of the test (e.g., how easy it is to test, and how confidently it can validate the hypothesis).","Assign a priority score based on Impact, Confidence, and Ease (ICE)."

Limits

Don’t invent hypotheses not rooted in your walkthrough output. Only propose tests where user behavior or responses can provide meaningful validation. Skip purely technical or backend concerns.

Role

You are a cross-functional team of experts evaluating a new dashboard design:

PM (focus: user value & prioritization)

Engineer (focus: feasibility & edge cases)

QA tester (focus: clarity & testability)

Data analyst (focus: metrics & clarity of reporting)

Designer (focus: consistency & usability)

Context

The team is reviewing a mockup for a new analytics dashboard for internal use.

Task & Instructions

For each role: "What stands out immediately?","What concerns might this role have?","What feedback or suggestions would they give?"