recovery-strategies

Troubleshooting TypeScript errors systematically means following a structured recovery path: review relevant documentation, study working examples, perform strategic investigation, reset your approach, and escalate to clarify requirements if needed. This prevents unproductive loops and identifies whether the issue is implementation, documentation, or a framework limitation.

When blocked during development, execute a five-step recovery sequence: consult documentation, examine similar working patterns, investigate strategically using plan mode and subagents, retry with a fresh approach, and ask for user clarification. This escalation path unblocks progress without endless trial-and-error.

Recovery strategies prescribe resetting after 1-2 failed attempts at the same fix. This stop criterion prevents wasted effort. If documentation review and pattern study don't reveal the solution, reset and retry with a fresh perspective before escalating further.

Yes, recovery strategies apply to framework confusion, unexpected behavior, and any blocked progress during development. The structured workflow guides you through documentation and examples to diagnose whether the issue stems from implementation, a documentation gap, or a framework limitation.

Recovery strategies provide explicit escalation criteria and a disciplined five-step workflow tailored to development stagnation. Unlike ad-hoc troubleshooting, they integrate documentation review, pattern study, strategic investigation via subagents, reset thresholds, and structured clarification, minimizing downtime and frustration.

Activate recovery strategies after 1-2 failed attempts at fixing an error without progress. The workflow saves time by systematically reviewing documentation and examples before investing more effort, ensuring you move to the next logical step rather than cycling through unsuccessful approaches.