DebuggingBeginner2 variants

Bug Reproduction Brief

Turn a vague bug report into a minimal reproduction plan, likely causes, and targeted files to inspect.

Placeholders

{{ACTUAL_BEHAVIOR}}{{BUG_SUMMARY}}{{EXPECTED_BEHAVIOR}}{{RELEVANT_STACK}}

Base template

You are helping me debug a production issue.

Bug summary: {{BUG_SUMMARY}}

Expected behavior: {{EXPECTED_BEHAVIOR}}

Actual behavior: {{ACTUAL_BEHAVIOR}}

Relevant stack: {{RELEVANT_STACK}}

Please produce:

A minimal reproduction checklist.
The most likely files or modules to inspect first.
Three hypotheses ranked by probability.
A focused test plan that can prove or disprove each hypothesis.

Stack Variants

Next.js + Firebase

Client/server auth or Firestore data bugs

Variant

Use this repo context as a Next.js App Router + Firebase app.

Issue: {{BUG_SUMMARY}}

Expected: {{EXPECTED_BEHAVIOR}}

Actual: {{ACTUAL_BEHAVIOR}}

Inspect likely boundaries across route handlers, Firebase client calls, server auth helpers, Firestore rules, and React state. Return a reproduction checklist, likely files, and the smallest Jest or Playwright test that should fail before the fix.

Notes

Call out whether the bug is likely client state, route-handler auth, or Firestore rule behavior.
Prefer focused Jest for route/data logic and Playwright only for browser-only flows.

Python + Django

View, form, and ORM behavior bugs

Variant

Use this as a Django debugging brief.

Bug: {{BUG_SUMMARY}}

Expected: {{EXPECTED_BEHAVIOR}}

Actual: {{ACTUAL_BEHAVIOR}}

Identify the smallest failing request or model operation, the view/form/model boundary most likely involved, and the focused pytest cases needed for the reproduction.

Notes

Ask Cursor to inspect migrations when the symptom involves missing fields or unexpected defaults.
Include permission and queryset hypotheses before changing view logic.