Debugging and Troubleshooting
troubleshooting-bugs
Standard protocol for debugging and fixing issues across the stack. Use when encountering errors or unexpected behavior.
SKILL.md
Full skill instructions
Debugging and Troubleshooting
When to use this skill
- UI is not rendering as expected.
- Appwrite API calls are failing.
- Next.js build errors or hydration mismatches.
Protocol
- Check Browser Console: Look for hydration errors or JavaScript crashes.
- Check Network Tab: Inspect the request/response payload for Appwrite calls.
- Check Appwrite Console: View "Logs" and "Permissions" for the failing collection.
- Check Terminal: Look for
use serveror promise-related errors in the Next.js dev server.
Common Fixes
- Auth Error (401): User is not logged in or doesn't have permissions.
- Hydration Error: Ensure
useStateor browser-only APIs are wrapped inuseEffect. - Forbidden (403): Check Appwrite "Document Security" settings.
Instructions
- Log specifically: Use
console.error('[Appwrite Error]:', error)for clarity.
