Click on the image and quickly read the text before it gets deleted. 👇👇👇 Pick the model that fits the task. Specs beat vibes. 🪛 Haiku is a sprinter. It'll absolutely take a swing at your distributed system architecture—the answer just won't be one you can ship. Your job is to match the model to the work. If the problem is well-defined—clear specs, acceptance criteria, edge cases enumerated—Sonnet handles it fine. You'll spend more time in review, but you'll save real money. You'll also catch your own bad specs faster, which is its own gift. If the feature is a tangled mess and you can't (or won't) break it down, that's also fine. Hand the whole thing to Opus instead. You don't have to scope every subproblem, but you DO have to define the whole solution. "Make it work" is not a valid requirement—it's a desperate wish the agent will not understand. A cheap model with great specs beats an expensive model with vibes and feelings, every single time. Plan in chat. Touch the codebase last.…