Tutor me on testing prompts across ChatGPT, Claude, and Gemini. 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.

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,

Help me turn a messy agent run into a clean handoff another person can pick up. 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

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

I want to learn tool approval gates for AI agents, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

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?

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.

Give me a short checklist for prompting from examples. I want something I can run before I call the work done.

Give me a short checklist for React state that keeps drifting. I want something I can run before I call the work done.

I want to learn prompt injection basics for tool users, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

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?

I want to learn writing eval cases before changing a prompt, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

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.

For meeting notes into decisions, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

I am stuck on a tiny business forecast. I need to build a transparent cash forecast with assumptions that can be updated monthly, but my current attempt is getting vague and too big. What would you check first?

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

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

Be blunt about my plan for a dashboard that answers one question. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

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?

I want to learn using examples to teach output quality, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

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

I want to learn context engineering for reliable agents, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

I am stuck on long-document context. I need to work through a long document without losing definitions, exceptions, or open questions, but my current attempt is getting vague and too big. What would you check first?

Going freelance as a policy analyst. 9 years in-house, last salary £68k. I'm thinking £450/day. Sanity check me.

I want to learn tracking prompt versions and results, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

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?

For metrics with fuzzy definitions, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

I want to learn separating model mistakes from missing context, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

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

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.