Claude Code tip: before you ship a vibe-coded site, have Opus 5.5 send out 𝟱 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 to check 𝘁𝗵𝗲𝘀𝗲 𝟮𝟬 𝘁𝗵𝗶𝗻𝗴𝘀, then fix them all in one pass: Consistent design → Write a DESIGN.md first, and make every color, font size, spacing and corner radius follow it → Keep the palette restrained and the type hierarchy clear → Make every button, card and input of the same kind look alike → Too flat? Add emphasis. Too crowded? Cut → Keep text readable on both dark and light backgrounds On mobile → No sideways scrolling, and nothing spilling off the screen → Add a mobile menu → Make buttons big enough to tap → Keep the layout intact when the text is enlarged Every state → Give loading, empty and error states a proper screen → Give every button feedback, with its own hover, pressed and disabled look → Show form errors right where they happen, plus submitting, success and failure messages → Add transitions to modals, dropdowns and tab switches Use it like a real user → Click through the core flows, like sign-up and checkout, from start to finish → Find buttons that do nothing and links that are broken → Make sure the whole thing works with just a keyboard Before launch → Say what you do in one line on the home page → Give each page one main button you want people to click → Give every page a title, a description and a favicon → Delete all placeholder text For effort, follow Anthropic's cost guide from yesterday: medium is for well-scoped daily work. The default medium is enough for these 20 fixes; raise it for the harder ones. Thariq tested it: turning effort up mostly buys more verification and edge-case testing. Send this whole post to Claude Code. If you need to, add this line at the end 👇 "Send one subagent per group to check it without editing anything. Then fix everything yourself from their lists, so no two agents edit the same file. If a group is more complex, raise that subagent's effort. Show me the list of issues first, don't change anything until I confirm, and when you're done, give me before-and-after screenshots."

Every time you let Opus 5.5 run a long task on its own, have it vibe-code a quick 𝗛𝗧𝗠𝗟 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 like this first. Then give it 𝗮 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁 𝘁𝗵𝗮𝘁 𝗼𝗻𝗹𝘆 𝗯𝘂𝗶𝗹𝗱𝘀 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱𝘀: → Name it dashboard-builder, set its effort to medium, and preload a design skill → The first time, it asks what style you like and saves it to memory. After that, every dashboard fits your taste and the task at hand → Call it before every long task. It builds the dashboard in the background in about two minutes, and the main session keeps coding on high without stopping → The dashboard shows four things: task progress, what's stuck, questions waiting on you, and what it'll do by default if you don't answer Send this prompt to Claude Code 👇 "Set up a subagent that only builds progress dashboards: 1. Create dashboard-builder in ~/.claude/agents: model: opus, effort: medium, memory: user. Preload the design skills I have installed (for example impeccable). It can only read and write the .dashboard/ folder and its own memory. 2. The first time, it asks me what style I like: dark or light, dense or airy, and one accent color. It saves my answer to memory and follows it every time. Pick the panels for the current task; don't use a template. 3. The dashboard is one HTML file showing tasks and their status, questions waiting for me with the default action, the latest deliverables, and anything stuck. Use the real clock for every time. It opens with a double-click and refreshes itself every 10 seconds. 4. Add a rule to ~/.claude/CLAUDE.md: for any task with more than 5 steps or that should take longer than 30 minutes, have dashboard-builder set up the dashboard before starting; update it after every step; when you need a decision from me, add it to the questions list and keep going with the default. Show me the contents of the files you'll create or change, then explain the whole flow in words a 10-year-old could follow. Don't write anything until I confirm."

Anthropic just published a guide to using Opus 5.5. It tells you to delete "think carefully" from your prompts. You can ask Opus 5.5 to use it to review the old rules in your project. It already thinks before every reply, and it decides how much. Delete that line and replies start sooner, with no drop in quality. If your CLAUDE.md still says "take a deep breath" or "IMPORTANT: think hard," delete those too. Send this prompt and the link below to Opus 5.5 👇 "Read this guide and review my project's CLAUDE.md, AGENTS.md, skills, and saved prompts. Find three kinds of problems: lines that push you to think more, like 'think carefully' or 'take a deep breath'; rules and prompts that hand out tasks one step at a time or don't define what done looks like; and rules that make you stop for confirmation when you don't need to. For each issue, quote the original instruction, explain its impact, and suggest the smallest change needed. List any approval rules involving safety, permissions, or destructive actions separately for me to decide. Also suggest adding one rule: at the end of every long run, report under three headings: Blocked on me, Changed, Found. Show me the recommendations first. Don't modify anything yet." claude.dev/blog/getting-the-…