MCP serverSave straight from your agent

About us How it works FAQ Blog Contact us

Home Explore Create Sign in

Explore

Loading…

Explore

Tagged #design

Active New Most used Recommended

All AI & Prompt Engineering324 Engineering176 Data & Analytics89 Product4

Browse by tag

#ai314#chatgpt211#claude208#gemini208#prompting182#agents174#context-engineering172#coding160

Customer Success3

People & Recruiting4

Security & Compliance8

Other Professional1

#designClear filters

MIMiles Kim@mileskim·2w ago

ChatGPT was overcomplicating a design critique that stays specific, so I reset the question

The useful bit was asking for trade-offs and a smallest test before committing to a full plan.

Miles Kim

Be blunt about my plan for a design critique that stays specific. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

ChatGPTgpt-5

Three things. - “Everything” has no boundary, so weak inputs and strong inputs will be treated alike. - A polished answer can hide missing evidence. Ask for gaps and assumptions before prose. - “Fix details later” means there is no acceptance test now. A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, check the keyboard path.

Show all 3 messages

3304.2k

LELeila Lane@leilalane·3w ago

How I ask for help with accessibility review for a form

Not magic wording, just enough context and a clear definition of done. Easy to adapt.

Leila Lane

Be blunt about my plan for accessibility review for a form. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Claudeclaude-opus-4.5

Three things. - “Everything” has no boundary, so weak inputs and strong inputs will be treated alike. - A polished answer can hide missing evidence. Ask for gaps and assumptions before prose. - “Fix details later” means there is no acceptance test now. A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, check the keyboard path.

Show all 3 messages

3404k

YUYuna Rivera@yunarivera·2w ago

an onboarding screen with too many choices, minus the vague advice

I wanted help with an onboarding screen with too many choices without pretending the model knew facts I had not provided.

Yuna Rivera

Give me a short checklist for an onboarding screen with too many choices. I want something I can run before I call the work done.

Geminigemini-2.5-pro

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Name the user decision first - [ ] Check the keyboard path - [ ] Remove one competing action - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.

Show all 3 messages

3401.4k

ZAZara Shah@zarashah·4w ago

The mobile navigation under pressure prompt I actually kept

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

Zara Shah

Help me choose a mobile navigation pattern for frequent and infrequent actions. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation. Otherwise

ChatGPTgpt-5

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For mobile navigation under pressure, I would start with these checks: - Name the user decision first - Check the keyboard path - Remove one competing action If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3402.7k

MIMiles Kim@mileskim·1mo ago

The question that cleaned up a design critique that stays specific

Sharing the wording because it gave me something I could check instead of a confident wall of text.

Miles Kim

Help me critique hierarchy, spacing, flow, and content without falling back to taste. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation. Oth

Claudeclaude-opus-4.5

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For a design critique that stays specific, I would start with these checks: - Name the user decision first - Check the keyboard path - Remove one competing action If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3302.8k

OWOwen Ito@owenito·4w ago

I asked Gemini for a second opinion on a usable empty state

This started as a messy question about a usable empty state. The follow-up made the answer practical.

Owen Ito

Be blunt about my plan for a usable empty state. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Geminigemini-2.5-pro

Three things. - “Everything” has no boundary, so weak inputs and strong inputs will be treated alike. - A polished answer can hide missing evidence. Ask for gaps and assumptions before prose. - “Fix details later” means there is no acceptance test now. A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, check the keyboard path.

Show all 3 messages

3301.3k

OWOwen Ito@owenito·2mo ago

The a usable empty state prompt I actually kept

A compact prompt and the response it produced. Replace the bracketed parts with your own details.

Owen Ito

Help me design an empty state that explains value and gives one obvious next action. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation. Othe

ChatGPTgpt-5

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For a usable empty state, I would start with these checks: - Name the user decision first - Check the keyboard path - Remove one competing action If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3302.7k

YUYuna Rivera@yunarivera·2mo ago

I stopped guessing about an onboarding screen with too many choices

Not magic wording, just enough context and a clear definition of done. Easy to adapt.

Yuna Rivera

For an onboarding screen with too many choices, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

Claudeclaude-opus-4.5

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For an onboarding screen with too many choices, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3304.2k

OWOwen Ito@owenito·2mo ago

A smaller way to tackle a usable empty state

The useful bit was asking for trade-offs and a smallest test before committing to a full plan.

Owen Ito

For a usable empty state, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

ChatGPTgpt-5

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For a usable empty state, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3402.7k

YUYuna Rivera@yunarivera·2mo ago

The question that cleaned up an onboarding screen with too many choices

I wanted help with an onboarding screen with too many choices without pretending the model knew facts I had not provided.

Yuna Rivera

Help me reduce an onboarding flow while preserving the choices that change the experience. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation

Claudeclaude-opus-4.5

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For an onboarding screen with too many choices, I would start with these checks: - Name the user decision first - Check the keyboard path - Remove one competing action If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3402.2k

LELeila Lane@leilalane·1mo ago

Forked from@remycole/How I ask for help with an essay with a weak middle

What finally made accessibility review for a form click for me

The first answers were broad enough to be useless. This version asks for assumptions, evidence, and a next step.

Leila Lane

Help me check labels, focus order, errors, contrast, and keyboard behavior for a form. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation. Ot

Geminigemini-2.5-pro

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For accessibility review for a form, I would start with these checks: - Name the user decision first - Check the keyboard path - Remove one competing action If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3401.2k

MIMiles Kim@mileskim·3mo ago

a design critique that stays specific, minus the vague advice

Sharing the wording because it gave me something I could check instead of a confident wall of text.

Miles Kim

Give me a short checklist for a design critique that stays specific. I want something I can run before I call the work done.

Geminigemini-2.5-pro

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Name the user decision first - [ ] Check the keyboard path - [ ] Remove one competing action - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.

Show all 3 messages

3304.1k

OWOwen Ito@owenito·3mo ago

The checklist I use for a usable empty state

Sharing the wording because it gave me something I could check instead of a confident wall of text.

Owen Ito

I am stuck on a usable empty state. I need to design an empty state that explains value and gives one obvious next action, but my current attempt is getting vague and too big. What would you check first?

Claudeclaude-opus-4.5

First, shrink the decision. Do not solve the whole subject at once. 1. Name the user decision first. 2. Check the keyboard path. 3. Remove one competing action. Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.

Show all 3 messages

3404.1k

YUYuna Rivera@yunarivera·1mo ago

ChatGPT was overcomplicating an onboarding screen with too many choices, so I reset the question

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

Yuna Rivera

Be blunt about my plan for an onboarding screen with too many choices. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

ChatGPTgpt-5

Three things. - “Everything” has no boundary, so weak inputs and strong inputs will be treated alike. - A polished answer can hide missing evidence. Ask for gaps and assumptions before prose. - “Fix details later” means there is no acceptance test now. A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, check the keyboard path.

Show all 3 messages

340792

LELeila Lane@leilalane·3mo ago

A blunt review of my approach to accessibility review for a form

The first answers were broad enough to be useless. This version asks for assumptions, evidence, and a next step.

Leila Lane

Give me a short checklist for accessibility review for a form. I want something I can run before I call the work done.

ChatGPTgpt-5

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Name the user decision first - [ ] Check the keyboard path - [ ] Remove one competing action - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.

Show all 3 messages

3404.2k

ZAZara Shah@zarashah·2mo ago

A smaller way to tackle mobile navigation under pressure

The first answers were broad enough to be useless. This version asks for assumptions, evidence, and a next step.

Zara Shah

For mobile navigation under pressure, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

ChatGPTgpt-5

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For mobile navigation under pressure, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3301.2k

MIMiles Kim@mileskim·2mo ago

I stopped guessing about a design critique that stays specific

A compact prompt and the response it produced. Replace the bracketed parts with your own details.

Miles Kim

For a design critique that stays specific, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

Claudeclaude-opus-4.5

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For a design critique that stays specific, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3401.3k

OWOwen Ito@owenito·3mo ago

a usable empty state: the version with actual constraints

A compact prompt and the response it produced. Replace the bracketed parts with your own details.

Owen Ito

Give me a short checklist for a usable empty state. I want something I can run before I call the work done.

Claudeclaude-opus-4.5

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Name the user decision first - [ ] Check the keyboard path - [ ] Remove one competing action - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.

Show all 3 messages

3304.1k

YUYuna Rivera@yunarivera·3mo ago

I needed a usable answer on an onboarding screen with too many choices

The first answers were broad enough to be useless. This version asks for assumptions, evidence, and a next step.

Yuna Rivera

I am stuck on an onboarding screen with too many choices. I need to reduce an onboarding flow while preserving the choices that change the experience, but my current attempt is getting vague and too big. What would you check first?

Geminigemini-2.5-pro

First, shrink the decision. Do not solve the whole subject at once. 1. Name the user decision first. 2. Check the keyboard path. 3. Remove one competing action. Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.

Show all 3 messages

3303.6k

LELeila Lane@leilalane·3mo ago

My notes from fixing accessibility review for a form

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

Leila Lane

I am stuck on accessibility review for a form. I need to check labels, focus order, errors, contrast, and keyboard behavior for a form, but my current attempt is getting vague and too big. What would you check first?

ChatGPTgpt-5

First, shrink the decision. Do not solve the whole subject at once. 1. Name the user decision first. 2. Check the keyboard path. 3. Remove one competing action. Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.

Show all 3 messages

3302.6k

LELeila Lane@leilalane·2mo ago

Gemini found the hole in my accessibility review for a form plan

I wanted help with accessibility review for a form without pretending the model knew facts I had not provided.

Leila Lane

For accessibility review for a form, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

Geminigemini-2.5-pro

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For accessibility review for a form, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3301.2k

ZAZara Shah@zarashah·2mo ago

The checklist I use for mobile navigation under pressure

Not magic wording, just enough context and a clear definition of done. Easy to adapt.

Zara Shah

I am stuck on mobile navigation under pressure. I need to choose a mobile navigation pattern for frequent and infrequent actions, but my current attempt is getting vague and too big. What would you check first?

Claudeclaude-opus-4.5

First, shrink the decision. Do not solve the whole subject at once. 1. Name the user decision first. 2. Check the keyboard path. 3. Remove one competing action. Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.

Show all 3 messages

3301.3k

MIMiles Kim@mileskim·2mo ago

I needed a usable answer on a design critique that stays specific

This started as a messy question about a design critique that stays specific. The follow-up made the answer practical.

Miles Kim

I am stuck on a design critique that stays specific. I need to critique hierarchy, spacing, flow, and content without falling back to taste, but my current attempt is getting vague and too big. What would you check first?

Geminigemini-2.5-pro

First, shrink the decision. Do not solve the whole subject at once. 1. Name the user decision first. 2. Check the keyboard path. 3. Remove one competing action. Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.

Show all 3 messages

3401.4k

ZAZara Shah@zarashah·3mo ago

I asked Gemini for a second opinion on mobile navigation under pressure

I wanted help with mobile navigation under pressure without pretending the model knew facts I had not provided.

Zara Shah

Be blunt about my plan for mobile navigation under pressure. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Geminigemini-2.5-pro

Three things. - “Everything” has no boundary, so weak inputs and strong inputs will be treated alike. - A polished answer can hide missing evidence. Ask for gaps and assumptions before prose. - “Fix details later” means there is no acceptance test now. A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, check the keyboard path.

Show all 3 messages

3402.6k

ZAZara Shah@zarashah·3mo ago

mobile navigation under pressure: the version with actual constraints

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

Zara Shah

Give me a short checklist for mobile navigation under pressure. I want something I can run before I call the work done.

Claudeclaude-opus-4.5

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Name the user decision first - [ ] Check the keyboard path - [ ] Remove one competing action - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.

Show all 3 messages

3401.5k

#software-learning100

#data-literacy50

#prompt-template50

#trending-questions50