Give AI the context.
Keep the judgment.

Name: UI/UX Prompt Execution Library
Brand: GoodScool
Price: 499 INR

Find the right prompt for your design task, prepare it with real project context, and judge the answer with practical quality checks.

Get the Library for ₹499

100 prompts · 12 workflows · 10 starting points

Try a sample prompt

UI/UX Prompt Execution Library

Prompts100How to use

Understand the Brief · UB-1 Start here · 1 of 10

Decode a Vague Brief

1Prepare

Fill in your details

Each field replaces one bracket in the prompt. You can leave any blank.

Paste brief[paste brief]

We need a modern dashboard for our customers

Product / app[product/app]

Target user[target user]

Business goal[business goal]

2Copy and run

Ready to copy

Everything is filled. Review it before you paste it into an AI assistant.

Act as a senior product designer helping me interpret a vague brief before I start designing. Here is the brief I was given: We need a modern dashboard for our customers. The product is Orbit, a B2B analytics app for operations managers at mid-size retailers, and the business wants fewer support tickets about reporting. Do not start designing. Instead: (1) restate the brief in clear, literal terms, (2) list the assumptions hidden inside it, (3) list what is dangerously undefined, (4) write 8 clarifying questions I should ask the stakeholder before any design work, ranked by how much each one reduces project risk, and (5) propose a one-paragraph problem statement I can confirm with them. Flag anything that sounds like a solution disguised as a requirement.

3Judge the answer. Make the decision.

Quality checklist

Did it separate the real goal from the requested solution?

Are the clarifying questions specific to this product, not generic?

Did it surface assumptions I hadn't noticed myself?

Is the problem statement something a stakeholder could confirm or correct?

Are unverified goals and constraints marked for stakeholder confirmation?

UI/UX Prompt Execution Library

Prompts100How to use

UB-1 · Understand the Brief Start here

Decode a Vague Brief

Your context

Product / app

Orbit, a B2B analytics app

Target user

operations managers at mid-size retailers

Business goal

fewer support tickets about reporting

2Copy and run

Ready to copy

Everything is filled. Review it before you paste it into an AI assistant.

Quality checklist

Did it separate the real goal from the requested solution?

Are the clarifying questions specific to this product, not generic?

Did it surface assumptions I hadn't noticed myself?

1
Your real context.Four labelled fields replace the brackets in the prompt. Leave any blank.
2
A prepared instruction.Your details are placed into the authored prompt, ready to copy into your AI assistant.
3
Quality checks included.Every prompt comes with a checklist for judging the answer, and a note on what to verify.

The real library at the prompt page, rebuilt natively. Illustrative sample project. The library prepares prompts for your own AI assistant; it does not run an AI model.

Generic prompts
get generic answers.

The brief was “Make our app more user-friendly.” Here is what goes into the AI assistant next.

The generic request

“Act as a UX expert and improve this app.”

What the AI does not know

Who the users are

What the business wants

What is currently failing

What constraints exist

What evidence has been collected

Which assumptions need confirming

With context

From the library · Decode a Vague Brief

Act as a senior product designer helping me interpret a vague brief before I start designing. Here is the brief I was given: Make our app more user-friendly. The product is Orbit, a B2B analytics app for operations managers at mid-size retailers, and the business wants fewer support tickets about reporting. Do not start designing. Instead: (1) restate the brief in clear, literal terms, (2) list the assumptions hidden inside it, (3) list what is dangerously undefined, (4) write 8 clarifying questions I should ask the stakeholder before any design work, ranked by how much each one reduces project risk, and (5) propose a one-paragraph problem statement I can confirm with them. Flag anything that sounds like a solution disguised as a requirement.

Illustrative sample project. The prepared prompt gives the AI a more specific task and clearer context. It does not guarantee a better answer.

A better prompt isn’t longer. It’s better informed.

Bring the brief.
Build the prompt.

See how one unclear design task becomes a more structured instruction using your project context.

UI/UX Prompt Execution Library

Prompts100How to use

Understand the Brief · UB-1 Start here · 1 of 10

Decode a Vague Brief

Turn a one-line or buzzword-filled brief into a structured design problem before you open Figma.

Prepare

Best used when

A client, founder, or PM hands you something like 'make it modern' or 'we need a dashboard' with no detail.

What you need

The exact brief text, the product type, and anything you know about the business and users.

Fill in your details

Each field replaces one bracket in the prompt. You can leave any blank.

Paste brief[paste brief]

Product / app[product/app]

Target user[target user]

Business goal[business goal]

Sample data is illustrative. Nothing you type here leaves this page.

What you type stays in this browser tab. Before pasting into an external AI assistant, remove confidential, personal or proprietary material you are not authorized to share.

Copy and run

4 blanks left

Blanks stay in the prompt as [brackets]. Fill them here or in your AI assistant.

Act as a senior product designer helping me interpret a vague brief before I start designing. Here is the brief I was given: [paste brief]. The product is [product/app] for [target user], and the business wants [business goal]. Do not start designing. Instead: (1) restate the brief in clear, literal terms, (2) list the assumptions hidden inside it, (3) list what is dangerously undefined, (4) write 8 clarifying questions I should ask the stakeholder before any design work, ranked by how much each one reduces project risk, and (5) propose a one-paragraph problem statement I can confirm with them. Flag anything that sounds like a solution disguised as a requirement.

Expected output

A restated brief, hidden assumptions, undefined gaps, 8 risk-ranked clarifying questions, and a draft problem statement.

Apply in real work

Send the ranked questions to your stakeholder before estimating timelines. Use their answers to rewrite the real brief.

Quality checklist

Watch for

Accepting the brief at face value and designing the literal request instead of the underlying need.

Your callTreat missing stakeholder facts as open questions. Confirm the problem, constraints and success criteria with the people who own the brief.

The real library’s prompt page, rebuilt natively and wired to its actual placeholder rules. This prepares a prompt. It does not run an AI model.

That was one prompt of one hundred.

Get the Library for ₹499

More than a prompt.
A complete way to use it.

Every prompt opens into the same three steps, so you always know what to prepare and what to check.

UI/UX Prompt Execution Library

Prompts100How to use

User Research · UR-2 Start here · 2 of 10

Plan a User Interview Script1

Build a structured, non-leading interview guide that gets you real stories, not validation.

1Prepare

Best used when2

You're about to interview users and want a guide that surfaces behaviour and motivation.

What you need3

Your research questions, who you're interviewing, and the topic.

Fill in your details

Product / app[product/app]

Target user[target user]

Topic[topic]

Research questions[research questions]

What do they do when two reports disagree? Who do they ask for help?

Time[time]

Supporting evidence or source notesOptional

2Copy and run4

Ready to copy

Act as a UX researcher writing a semi-structured interview guide. Product: Orbit, a B2B analytics app, participant: operations managers at mid-size retailers. I want to learn about how they decide which report to trust to answer these questions: What do they do when two reports disagree? Who do they ask for help?. Interview length: 45 minutes. Produce: (1) a warm-up that builds rapport without priming, (2) 8-12 open, non-leading questions ordered from broad to specific, focused on past behaviour and real examples ('tell me about the last time...'), (3) follow-up probes for each main question, and (4) a list of leading phrasings to avoid. Do not include questions that ask users to predict the future or design the solution. Evidence rule: use only the material I provide or sources you can directly inspect and cite. Distinguish observed facts from inference. If evidence is partial, mark gaps; if absent, ask for the minimum missing material or give an inspection plan. Never invent participants, quotes, metrics, interface details or outcomes.

3Judge the answer. Make the decision.

Expected output5

A warm-up, ordered open questions with probes, and a list of phrasings to avoid.

Apply in real work6

Run a pilot interview with the guide, cut what doesn't land, then use it for the rest.

Quality checklist

Are questions about real past behaviour, not hypotheticals?

Are they genuinely non-leading?

Do the probes dig for the 'why' behind answers?

Does the order move naturally from broad to specific?

Can each claimed finding be traced to supplied participant or study evidence?

The real library, rebuilt natively, shown with illustrative sample context. Prompt: Plan a User Interview Script.

01The taskWhat the prompt helps you accomplish, in one line.
02When to use itThe professional situation where it becomes relevant.
03What to prepareThe real project information to bring, and fields to put it in.
04The complete instructionYour context placed into the authored prompt, ready for your AI assistant.
05What good output looks likeThe expected output, plus a checklist for judging the answer.
06What to do nextHow to apply the useful parts, and where your judgment still decides.

Whatever stage you’re in,
start with the task.

Twelve workflows, grouped the way a project unfolds. Pick one to see the real prompts inside.

UnderstandBrief, research, framing

ExploreCompetitors, ideas, structure

DesignScreens, polish, words

EvaluateCritique and iteration

CommunicatePortfolio and interviews

Understand

Understand the Brief

8 prompts

UB-1

Decode a Vague BriefStart hereTurn a one-line or buzzword-filled brief into a structured design problem before you open Figma.

UB-2

Separate the Problem from the SolutionCatch briefs that secretly prescribe a solution and recover the underlying problem.

UB-3

Extract Success Criteria from a BriefPin down how the project will be judged before you design, so you aren't surprised at review.

UB-4

Map Stakeholders and Hidden ExpectationsIdentify who will judge the work and what each person silently expects, before you present.

UB-5

Scope a Brief into MVP and Later PhasesCut an overloaded brief down to a defensible first version with clear later phases.

+ 3 more in this workflow

Search looks across titles, use cases, preparation notes, the prompt itself, expected output and checklist wording, so you can start from the words in your brief.

Don’t start by wondering what to ask AI. Start with the work you’re trying to do.

AI gives you an answer.
Good judgment decides what survives.

Use AI as a thinking partner. Keep the final decision yours.

UI/UX Prompt Execution Library

Prompts100How to use

Competitor Analysis · CA-1 Start here · 4 of 10

Competitor UX Teardown

What you need

The competitor, the flow you care about, and your own product's angle. Provide dated screenshots, a flow walkthrough, or directly accessible current source material; a competitor name alone is insufficient.

3Judge the answer. Make the decision.

Quality checklist

Watch for

Copying a competitor's UI wholesale without understanding why it works for their users.

Your callVerify the current interface directly. A plausible description of a competitor flow is not evidence that it exists today.

The real library’s after-use view for Competitor UX Teardown. Tick the checks as you evaluate an answer.

A plausible answer is not evidence.
This prompt tells you to supply dated screenshots or source material, and to mark what the AI is inferring.
The checklist is yours to use.
The library supplies the questions. You do the evaluating. It does not check the AI’s answer for you.
Then decide what to apply.
Borrow the validated patterns, avoid the anti-patterns, and design your differentiation around the gap.

Find the task.
Prepare the context.
Judge the answer.

UI/UX Prompt Execution Library. A browser-based library for working with AI on real design tasks.

100 structured prompts
12 UI/UX workflows
10 curated starting prompts
Context-preparation fields for every prompt
Copy-ready prepared prompts
Expected-output guidance
Task-specific quality checklists
Practical application notes
Common-mistake warnings
Human-judgment reminders
Search and workflow filtering
Related-prompt suggestions
Educational field guide to using AI in design

UI/UX Prompt Execution Library

₹499

100 prompts · 12 workflows
10 starting points

Get the Library for ₹499

Runs in your browserNo AI model includedNothing saved or sent

Questions designers ask first.

Is this just a PDF containing AI prompts?

No. It is a searchable library that runs in your browser. You search or browse by workflow, add your project details in labelled fields, copy the prepared prompt, and check the answer against the prompt’s own checklist.

Do I need to know prompt engineering?

No prior prompt engineering is assumed. Each prompt says when to use it and what to prepare. You will still need to judge the answers, which is the skill the library helps you practise.

Can I use these prompts with ChatGPT or Claude?

Yes. The library prepares text that you copy into the AI assistant of your choice. You need your own access to that assistant.

Does the product include an AI model?

No. The library does not call an AI model, sign you in or save what you type.

Will the library generate designs or research automatically?

No. It prepares instructions and gives you guidance. The work happens in your own AI assistant, and you review the result.

Can I customise the prompts for my own project?

Yes. Each prompt has labelled context fields. What you type replaces the matching brackets in the prompt, and you can leave any field blank.

Are all 100 prompts different?

Each prompt targets a distinct task across 12 workflows, from decoding a brief to preparing for a design interview. The answers your assistant gives will vary.

Does the library save my project information?

No. What you type stays in the page’s memory and is cleared when you leave the prompt.

Is my project information uploaded to GoodScool?

The library does not send what you type to a server. Before you paste it into an external AI assistant, remove anything confidential, personal or proprietary that you are not authorized to share.

Is the AI output verified by GoodScool?

No. Each prompt includes a quality checklist and guidance so you can evaluate the answer yourself. GoodScool does not check the responses your assistant gives.