fix-error

Diagnoses and fixes errors from build or runtime.

What it does:

• Analyzes error messages pasted by user
• Finds the root cause in the codebase
• Proposes and implements a fix
• Suggests next steps (rebuild, retest)

Usage: /fix_error <paste error message or describe the issue>

Examples:

• /fix_error Cannot read property 'id' of undefined
• /fix_error The plugin crashes when I click the button
• /fix_error Build failed with "Type 'string' is not assignable to type 'number'"

Steps

1. Understand the error

   • Parse the error message for key information:
     • Error type (TypeError, SyntaxError, build error, etc.)
     • File and line number if provided
     • Stack trace if available
   • If error is vague, ask user for more context

2. Locate the cause

   • Search the codebase for the relevant code
   • Check recent changes that might have caused it
   • Look for common patterns that cause this error

3. Explain in plain language

   • Tell user what went wrong and why
   • Avoid jargon — explain like they're not an engineer

4. Implement the fix

   • Make the necessary code changes
   • Explain what you changed and why

5. Suggest next steps

   • "Run /build to recompile the plugin"
   • "Test in Figma to verify the fix"
   • If the fix might have side effects, mention them

Common Error Patterns

"Cannot read property 'X' of undefined"

• Something is null/undefined when it shouldn't be
• Usually a missing null check or wrong variable

"Type 'X' is not assignable to type 'Y'"

• TypeScript type mismatch
• Check the expected type and fix the value

"figma is not defined"

• Trying to use figma.* in UI code (not allowed)
• Move that code to src/plugin/ instead

"Cannot find module"

• Import path is wrong or file doesn't exist
• Check spelling and file location

"postMessage" errors

• Message type mismatch between plugin and UI
• Check src/shared/messages.ts for correct types