Every tests Opus 5.5 for a week and shares six tips
After a week of projects with Opus 5.5, the Every team shares six lessons, including setting a budget, asking for the deliverable first, letting it self-critique, and pointing it at visual work.
We tested Claude Opus 5.5 for a week. Some tips: 1. Set a budget and a stopping point. It won't stop on its own, and it'll eat your weekly limit. Tell it what "done" looks like. 2. Ask for the deliverable first. Given 10 minutes for a run of show, it built a data generator and handouts, then ran out of time before making the schedule. 3. Let it critique itself, then check. It caught things our designer missed, and also rejected 90 percent of its own work for reasons he couldn't trace. 4. Give it notes. Opus 5.5 is a personality fix: It builds on your feedback now instead of arguing with it. 5. Move the point up yourself. Its prose is the most readable we've measured, but it still buries the lede. 6. Point it at visual work. Game UI, 3D, animations, and prototypes were its best one-shot results. Full Vibe Check: https://every.to/vibe-check/vibe-check-opus-5-5-is-pulling-our-codex-converts-back-to-claude?utm_source=x&utm_campaign=vibecheck-opus-5-5-is-pulling-our-codex-converts-back-to-claude&utm_content=every-260922-6tips