debug-errorlisted

# Debug Error Skill Systematic approach to debugging errors and unexpected behavior. Works with any project. ## MANDATORY: Pre-Debug Checks **BEFORE debugging, you MUST:** ### 1. Read Relevant Documentation ``` README.md (project overview) src/[domain]/@_[domain]-README.md (domain-specific behavior) docs/ (system documentation) ``` ### 2. Check for Sentry Context (if production error) If the error is from production and Sentry is configured, fetch the full context: ```json CallMcpTool(server: "plugin-sentry-sentry", toolName: "search_issues", arguments: { "organizationSlug": "<ORG_SLUG>", "naturalLanguageQuery": "<error message or description>", "projectSlugOrId": "<PROJECT_SLUG>", "regionUrl": "<REGION_URL>", "limit": 5 }) ``` Then get details for the matching issue: ```json CallMcpTool(server: "plugin-sentry-sentry", toolName: "get_sentry_resource", arguments: { "organizationSlug": "<ORG_SLUG>", "resourceType": "issue", "resourceId": "<ISSUE_ID>" }) ``` Extract: stacktrace, breadcrumbs, tags (browser, OS, URL, release), event frequency. ### 3. Check Database State (if data-related) If data is involved, verify expectations against reality using Supabase MCP or direct queries. ### 4. Verification Statement (REQUIRED) Before diving into debug, state: ``` "Pre-debug check: - README/docs read: [list] - Sentry context: [YES with details / NO — not production / not configured] - Database state verified: [YES/NO — findings] - Backend API checked: [YES/NO — sta