For complex, one-time tasks like a code migration, don't just ask AI to write a script. Instead, have it build a disposable tool—a "jig" or "command center”—that visualizes the process and guides you through each step. This provides more control and understanding than a black-box script.
Related Insights
Building complex, multi-step AI processes directly with code generators creates a black box that is difficult to debug. Instead, prototype and validate the workflow step-by-step using a visual tool like N8N first. This isolates failure points and makes the entire system more manageable.
A powerful workflow is to explicitly instruct your AI to act as a collaborative thinking partner—asking questions and organizing thoughts—while strictly forbidding it from creating final artifacts. This separates the crucial thinking phase from the generative phase, leading to better outcomes.
LLMs often get stuck or pursue incorrect paths on complex tasks. "Plan mode" forces Claude Code to present its step-by-step checklist for your approval before it starts editing files. This allows you to correct its logic and assumptions upfront, ensuring the final output aligns with your intent and saving time.
Before delegating a complex task, use a simple prompt to have a context-aware system generate a more detailed and effective prompt. This "prompt-for-a-prompt" workflow adds necessary detail and structure, significantly improving the agent's success rate and saving rework.
High productivity isn't about using AI for everything. It's a disciplined workflow: breaking a task into sub-problems, using an LLM for high-leverage parts like scaffolding and tests, and reserving human focus for the core implementation. This avoids the sunk cost of forcing AI on unsuitable tasks.
When building for AI-powered environments, design tools to be equally usable by humans and the AI model. An elegant, simple design for humans often translates directly into an effective tool for AI agents, simplifying development and promoting shared logic.
Vercel designer Pranati Perry advises viewing AI models as interns. This mindset shifts the focus from blindly accepting output to actively guiding the AI and reviewing its work. This collaborative approach helps designers build deeper technical understanding rather than just shipping code they don't comprehend.
Instead of asking an AI to directly build something, the more effective approach is to instruct it on *how* to solve the problem: gather references, identify best-in-class libraries, and create a framework before implementation. This means working one level of abstraction higher than the code itself.
To ensure comprehension of AI-generated code, developer Terry Lynn created a "rubber duck" rule in his AI tool. This prompts the AI to explain code sections and even create pop quizzes about specific functions. This turns the development process into an active learning tool, ensuring he deeply understands the code he's shipping.
A powerful but unintuitive AI development pattern is to give a model a vague goal and let it attempt a full implementation. This "throwaway" draft, with its mistakes and unexpected choices, provides crucial insights for writing a much more accurate plan for the final version.