🕵️ Bug Fixing & Troubleshooting Protocol

"Don't just patch the symptom; cure the disease."

When you encounter an error, DO NOT immediately write code to fix it. Follow this 4-Step Investigation Protocol first.

🚨 Step 1: Triage (Diagnosis)

Analyze the error stack trace or behavior. Categorize the issue:

•
Type A: Financial/Calculation Error (e.g., NaN, 0.300004, Wrong Balance)
- •👉 Directive: You MUST consult the financial-math skill.
- •Check: Are we using number instead of Decimal? Are we mixing currencies?
•
Type B: Database/Prisma Error (e.g., Foreign key constraint failed, Connection limit)
- •👉 Directive: You MUST consult the prisma-data-modeling skill.
- •Check: Are relations correct? Is the ID valid? Is the migration applied?
•
Type C: Security/Auth Error (e.g., Unauthorized, 403 Forbidden)
- •👉 Directive: You MUST consult the security-audit skill.
- •Check: Is auth() called? Is the user modifying their own data?
•
Type D: Fetch/Network Error (e.g., Failed to fetch, 500 Internal Server Error)
- •👉 Directive: You MUST consult the data-integration-layer skill.
- •Check: Is the API down? Do we have a fallback?

Before fixing, prove you understand the bug.

•Create a mental (or actual) reproduction case: "If I call buyStock with negative amount, it crashes."

Apply the fix based on the consulted Skill's rules.

•ANTI-PATTERN: Wrapping everything in try/catch and returning null just to silence the error. NEVER DO THIS.
•CORRECT: Fix the logic validation or data type.

Refer to Skill: qa-testing

•Run the reproduction case again. Does it pass?
•Regression Check: Did this fix break something else? (e.g., Fixing Buy logic shouldn't break Sell logic).

Error: Invalid value: 150.234234234 for field amount Bot Thought Process:

•Triage: This is a DB/Math error.
•Consult: financial-math says "No floats" and prisma-data-modeling says "Decimal(19,4)".
•Root Cause: We are passing a raw JS float to Prisma.
•Fix: Wrap the value in new Decimal(amount).toFixed(4).
•Verify: Run test.