Engineering prompts and AI conversations

The using property-based tests tutor prompt I saved

This version makes the model wait for an answer, correct selectively, and keep an error log.

Micah Ellis

Tutor me on using property-based tests. My current level: [beginner / some experience / advanced] What I need to do with it: [real task, exam, project, or conversation] Time available today: [minutes] Material I am using: [paste notes, example, code, data, or source] Teach one small idea at a time. Start with a two-question diagnostic. Wait for my answer before explaining. Use one worked example,

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain using property-based tests in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6215k

Haruto Abe@harutoabe·2mo ago

finding duplicated state in React: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Haruto Abe

I want to learn finding duplicated state in React, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain finding duplicated state in React in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6214.5k

Anika Kim@anikakim·2mo ago

The checklist I use for Postgres query tuning

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

Anika Kim

I am stuck on Postgres query tuning. I need to read an EXPLAIN plan and choose the smallest index or query change that matters, 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. Reproduce the failure before changing code. 2. Keep the patch smaller than the diagnosis. 3. Write the rollback before deployment. 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.8k

Samir Shah@samirshah·2mo ago

A blunt review of my approach to a safe dependency upgrade

This started as a messy question about a safe dependency upgrade. The follow-up made the answer practical.

Samir Shah

Give me a short checklist for a safe dependency upgrade. 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 - [ ] Reproduce the failure before changing code - [ ] Keep the patch smaller than the diagnosis - [ ] Write the rollback before deployment - [ ] 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.2k

Ben Brooks@benbrooks·2mo ago

React state that keeps drifting: the version with actual constraints

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

Ben Brooks

Give me a short checklist for React state that keeps drifting. 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 - [ ] Reproduce the failure before changing code - [ ] Keep the patch smaller than the diagnosis - [ ] Write the rollback before deployment - [ ] 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

3302.8k

Anya Volkov@anyavolkov·2mo ago

What I was getting wrong about reviewing code written by an agent

Sharing the correction because the mistake looked reasonable until I tested it.

Anya Volkov

I want to learn reviewing code written by an agent, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain reviewing code written by an agent in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6312.9k

Eva Kovac@evakovac·2mo ago

The designing idempotent background jobs tutor prompt I saved

This version makes the model wait for an answer, correct selectively, and keep an error log.

Eva Kovac

Tutor me on designing idempotent background jobs. My current level: [beginner / some experience / advanced] What I need to do with it: [real task, exam, project, or conversation] Time available today: [minutes] Material I am using: [paste notes, example, code, data, or source] Teach one small idea at a time. Start with a two-question diagnostic. Wait for my answer before explaining. Use one worked

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain designing idempotent background jobs in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6413.2k

Felix Silva@felixsilva·2mo ago

The cache invalidation without folklore prompt I actually kept

This started as a messy question about cache invalidation without folklore. The follow-up made the answer practical.

Felix Silva

Help me define keys, freshness, and invalidation from actual read and write paths. 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. Otherw

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 cache invalidation without folklore, I would start with these checks: - Reproduce the failure before changing code - Keep the patch smaller than the diagnosis - Write the rollback before deployment If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3303k

Rowan Blake@rowanblake·2mo ago

testing API failure paths: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Rowan Blake

I want to learn testing API failure paths, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain testing API failure paths in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6213.9k

Aya Lin@ayalin·2mo ago

The question that cleaned up database migration rehearsal

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

Aya Lin

Help me turn a risky schema change into staged, measurable deployment steps. 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, s

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 database migration rehearsal, I would start with these checks: - Reproduce the failure before changing code - Keep the patch smaller than the diagnosis - Write the rollback before deployment If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3403.3k

Samir Shah@samirshah·2mo ago

My notes from fixing a safe dependency upgrade

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

Samir Shah

I am stuck on a safe dependency upgrade. I need to plan a major dependency upgrade with compatibility checks and a rollback path, 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. Reproduce the failure before changing code. 2. Keep the patch smaller than the diagnosis. 3. Write the rollback before deployment. 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

3402.3k

Adrian Cho@adriancho·2mo ago

The learning TypeScript at runtime boundaries tutor prompt I saved

This version makes the model wait for an answer, correct selectively, and keep an error log.

Adrian Cho

Tutor me on learning TypeScript at runtime boundaries. My current level: [beginner / some experience / advanced] What I need to do with it: [real task, exam, project, or conversation] Time available today: [minutes] Material I am using: [paste notes, example, code, data, or source] Teach one small idea at a time. Start with a two-question diagnostic. Wait for my answer before explaining. Use one w

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain learning TypeScript at runtime boundaries in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6213.1k

Eva Kovac@evakovac·3mo ago

The reading a Postgres query plan tutor prompt I saved

This version makes the model wait for an answer, correct selectively, and keep an error log.

Eva Kovac

Tutor me on reading a Postgres query plan. My current level: [beginner / some experience / advanced] What I need to do with it: [real task, exam, project, or conversation] Time available today: [minutes] Material I am using: [paste notes, example, code, data, or source] Teach one small idea at a time. Start with a two-question diagnostic. Wait for my answer before explaining. Use one worked exampl

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain reading a Postgres query plan in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6415.1k

Fatima Saleh@fatimasaleh·2mo ago

planning a zero-downtime migration: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Fatima Saleh

I want to learn planning a zero-downtime migration, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain planning a zero-downtime migration in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6412.7k

Talia Ibrahim@taliaibrahim·2mo ago

API error handling, minus the vague advice

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

Talia Ibrahim

Give me a short checklist for API error handling. 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 - [ ] Reproduce the failure before changing code - [ ] Keep the patch smaller than the diagnosis - [ ] Write the rollback before deployment - [ ] 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

3402.7k

Soraya Aziz@sorayaaziz·3mo ago

debugging from a minimal reproduction: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Soraya Aziz

I want to learn debugging from a minimal reproduction, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain debugging from a minimal reproduction in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6314.2k

Silas Berg@silasberg·3mo ago

reading a Postgres query plan: a study session that did not turn into more notes

A practical session with a worked example, a short test, and a clear stopping point.

Silas Berg

I want to learn reading a Postgres query plan, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain reading a Postgres query plan in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6313.7k

Kenji Fujita@kenjifujita·3mo ago

I finally found a good way to learn using property-based tests

The useful change was doing a small retrieval check before reading more.

Kenji Fujita

I want to learn using property-based tests, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain using property-based tests in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6214.6k

Lucia Marin@luciamarin·2mo ago

What I was getting wrong about debugging from a minimal reproduction

Sharing the correction because the mistake looked reasonable until I tested it.

Lucia Marin

I want to learn debugging from a minimal reproduction, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain debugging from a minimal reproduction in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6412.7k

Noura Kassem@nourakassem·3mo ago

I finally found a good way to learn designing idempotent background jobs

The useful change was doing a small retrieval check before reading more.

Noura Kassem

I want to learn designing idempotent background jobs, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain designing idempotent background jobs in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6314.5k

Mina Cruz@minacruz·2mo ago

How I ask for help with a boring auth review

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

Mina Cruz

Be blunt about my plan for a boring auth review. 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, keep the patch smaller than the diagnosis.

Show all 3 messages

3402.9k

Jasper Wong@jasperwong·3mo ago

A practice-first plan for planning a zero-downtime migration

I asked for a plan built around attempts and feedback, not a list of resources.

Jasper Wong

I want to learn planning a zero-downtime migration, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain planning a zero-downtime migration in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6214.1k

Tomas Varga@tomasvarga·4mo ago

I finally found a good way to learn planning a zero-downtime migration

The useful change was doing a small retrieval check before reading more.

Tomas Varga

I want to learn planning a zero-downtime migration, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain planning a zero-downtime migration in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6215.2k

Nico Lane@nicolane·2mo ago

I needed a usable answer on a flaky test nobody can reproduce

This started as a messy question about a flaky test nobody can reproduce. The follow-up made the answer practical.

Nico Lane

I am stuck on a flaky test nobody can reproduce. I need to isolate a timing-dependent test failure and design a deterministic reproduction, 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. Reproduce the failure before changing code. 2. Keep the patch smaller than the diagnosis. 3. Write the rollback before deployment. 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

3402.4k

Ronan Byrne@ronanbyrne·4mo ago

A practice-first plan for reviewing code written by an agent

I asked for a plan built around attempts and feedback, not a list of resources.

Ronan Byrne

I want to learn reviewing code written by an agent, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain reviewing code written by an agent in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6314.3k

Drew Bell@drewbell·3mo ago

Gemini found the hole in my TypeScript types at an API boundary plan

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

Drew Bell

For TypeScript types at an API boundary, 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 TypeScript types at an API boundary, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3403.1k

Amina Farah@aminafarah·4mo ago

I finally found a good way to learn testing API failure paths

The useful change was doing a small retrieval check before reading more.

Amina Farah

I want to learn testing API failure paths, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain testing API failure paths in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6414.8k

Ben Brooks@benbrooks·3mo ago

I asked Gemini for a second opinion on React state that keeps drifting

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

Ben Brooks

Be blunt about my plan for React state that keeps drifting. 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, keep the patch smaller than the diagnosis.

Show all 3 messages

3302.7k

Ronan Byrne@ronanbyrne·3mo ago

A practice-first plan for using property-based tests

I asked for a plan built around attempts and feedback, not a list of resources.

Ronan Byrne

I want to learn using property-based tests, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

ChatGPTgpt-5

Good. Do these without looking anything up: 1. Explain using property-based tests in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6312.3k

Nia Costa@niacosta·3mo ago

My notes from fixing reviewing agent-written code

I wanted help with reviewing agent-written code without pretending the model knew facts I had not provided.

Nia Costa

I am stuck on reviewing agent-written code. I need to review generated code for silent assumptions, missing tests, and operational risk, 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. Reproduce the failure before changing code. 2. Keep the patch smaller than the diagnosis. 3. Write the rollback before deployment. 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.9k

Explore

Explore

Explore

The using property-based tests tutor prompt I saved

finding duplicated state in React: a study session that did not turn into more notes

The checklist I use for Postgres query tuning

A blunt review of my approach to a safe dependency upgrade

React state that keeps drifting: the version with actual constraints

What I was getting wrong about reviewing code written by an agent

The designing idempotent background jobs tutor prompt I saved

The cache invalidation without folklore prompt I actually kept

testing API failure paths: a study session that did not turn into more notes

The question that cleaned up database migration rehearsal

My notes from fixing a safe dependency upgrade

The learning TypeScript at runtime boundaries tutor prompt I saved

The reading a Postgres query plan tutor prompt I saved

planning a zero-downtime migration: a study session that did not turn into more notes

API error handling, minus the vague advice

debugging from a minimal reproduction: a study session that did not turn into more notes

reading a Postgres query plan: a study session that did not turn into more notes

I finally found a good way to learn using property-based tests

What I was getting wrong about debugging from a minimal reproduction

I finally found a good way to learn designing idempotent background jobs

How I ask for help with a boring auth review

A practice-first plan for planning a zero-downtime migration

I finally found a good way to learn planning a zero-downtime migration

I needed a usable answer on a flaky test nobody can reproduce

A practice-first plan for reviewing code written by an agent

Gemini found the hole in my TypeScript types at an API boundary plan

I finally found a good way to learn testing API failure paths

I asked Gemini for a second opinion on React state that keeps drifting

A practice-first plan for using property-based tests

My notes from fixing reviewing agent-written code