Bug reproduction and likely root-cause trace
Turns scattered console output and symptom notes into a debugging plan with ranked hypotheses.
Workflow
Engineering
Model fit
Claude 3.7 Sonnet
Author
PromptJoy Editorial
Author role
Editorial curation
Origin
PromptJoy curated launch library
Published
Apr 8, 2026
Copies the full prompt body so you can use it immediately in your model of choice.
Visible copy count on this device: 539
Current vote signal: +165
Sign in to save or vote on this curated prompt. Your state will stay on this device for your signed-in account while the shared library fills in.
What happens here
Copy keeps the prompt body exact and updates the visible count on this device. Save and vote also work on this curated prompt for signed-in users until the shared public library is live.
Live trust breakdown
Task clarity
+18 names the role the model should play
Input contract
+24 tells the user what inputs to provide
Output contract
+18 defines what the model should return
Guardrails
+22 includes explicit constraints
Safety
+12 does not request secrets or sensitive identifiers
Reusability
+18 has enough detail without becoming bloated
Community signal
+24 strong positive vote ratio
Trust score
70
Vote signal
+165
Saves
146
Copies
539
Task clarity
Checks whether the prompt clearly names the role, task, and workflow it is meant to support.
Evidence
- +18 names the role the model should play
- +18 states the job the prompt is meant to do
- +10 has task-oriented tags
Improve
- Make the title describe the task and context.
Input contract
Checks whether the prompt tells the user what context, data, or materials to provide.
Evidence
- +24 tells the user what inputs to provide
- +12 uses bullets to separate input fields or context
- +14 asks for task-specific context, not just raw text
Improve
- No obvious improvement flagged.
You are a senior full-stack engineer helping debug a production issue. I will give you the symptom, expected behavior, recent changes, console errors, and any relevant code or logs. Return: 1. the most likely root causes ranked from most to least likely 2. the fastest way to prove or disprove each cause 3. the minimum safe patch to try first 4. the regression risks to watch after the fix Rules: - do not suggest broad rewrites - prefer the smallest reversible debugging step first - call out when the issue is probably config, auth, caching, or data related