When your primary AI assistant gets stuck, export the conversation and feed it to a different model (e.g., GPT-4 or Gemini). This 'second opinion' can critique the original interaction and help you revise your prompt to get back on track, rather than trying to argue with the stuck AI.
For stubborn bugs, use an advanced prompting technique: instruct the AI to 'spin up specialized sub-agents,' such as a QA tester and a senior engineer. This forces the model to analyze the problem from multiple perspectives, leading to a more comprehensive diagnosis and solution.
When an AI coding assistant gets off track, Tim McLear asks it to generate a summary prompt for another AI to take over. This "resume work" prompt forces the AI to consolidate the context and goal. This summary often reveals where the AI misunderstood the request, allowing him to correct the course and restart with a cleaner prompt.
When an AI model gives nonsensical responses after a long conversation, its context window is likely full. Instead of trying to correct it, reset the context. For prototypes, fork the design to start a new session. For chats, ask the AI to summarize the conversation, then start a new chat with that summary.
Many AI tools expose the model's reasoning before generating an answer. Reading this internal monologue is a powerful debugging technique. It reveals how the AI is interpreting your instructions, allowing you to quickly identify misunderstandings and improve the clarity of your prompts for better results.
Instead of accepting an AI's first output, request multiple variations of the content. Then, ask the AI to identify the best option. This forces the model to re-evaluate its own work against the project's goals and target audience, leading to a more refined final product.
Getting a useful result from AI is a dialogue, not a single command. An initial prompt often yields an unusable output. Success requires analyzing the failure and providing a more specific, refined prompt, much like giving an employee clearer instructions to get the desired outcome.
When an AI tool fails, a common user mistake is to get stuck in a 'doom loop' by repeatedly using negative, low-context prompts like 'it's not working.' This is counterproductive. A better approach is to use a specific command or prompt that forces the AI to reflect and reset its approach.
When a prompt yields poor results, use a meta-prompting technique. Feed the failing prompt back to the AI, describe the incorrect output, specify the desired outcome, and explicitly grant it permission to rewrite, add, or delete. The AI will then debug and improve its own instructions.
When an agent fails, treat it like an intern. Scrutinize its log of actions to find the specific step where it went wrong (e.g., used the wrong link), then provide a targeted correction. This is far more effective than giving a generic, frustrated re-prompt.
Standard AI models are often overly supportive. To get genuine, valuable feedback, explicitly instruct your AI to act as a critical thought partner. Use prompts like "push back on things" and "feel free to challenge me" to break the AI's default agreeableness and turn it into a true sparring partner.