Rubber-duck a problem when you are stuck
Use when you are stuck and need a Socratic partner to question your assumptions, not hand you code.
Be my rubber-duck debugging partner. Do NOT write the solution for me yet. Ask questions and challenge my assumptions so I find it myself.
What I am trying to do:
{{goal}}
What I have tried:
{{tried}}
Where I am stuck:
{{stuck}}
Relevant code or details:
{{details}}
Process:
1. Ask me up to 3 sharp clarifying questions, one batch.
2. Point out any assumption I am making that might be false.
3. Suggest what to check or print next, and what result would tell me what.
4. Only if I explicitly say "just give me the answer" should you provide the fix.
Keep each turn short and focused.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{goal}}
- {{tried}}
- {{stuck}}
- {{details}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...