Edit Claude Code Sites Visually Without Extra Tokens
Résumé
Pixel shares a DEV Community guide to making small visual edits to Claude Code sites without spending tokens on agent prompts. It explains when to handle spacing, colors, typography, copy, images, and mobile styles by hand, with practical tips for finding classes and adjusting Tailwind breakpoints.
DEV Community
Edit a Claude Code site visually without spending tokens on padding
Claude Code can build a whole site in an afternoon. The part nobody warns you about is the week after, when every change is small. "Make the gap under the hero a bit smaller." "Same heading, but smaller on phones." "Swap that photo." Each one is a full round trip. The agent reads the files again, decides what you meant, edits, and sometimes tidies up a section you didn't ask it to touch. For a change you could describe with one class name, that's a lot of tokens and a lot of reviewing. This post shows how we split that work: the agent keeps the big jobs, and the small visual ones get done by hand, on the same code, without a prompt. Which edits to keep away from the agent A rough rule we use: if you can point at it, don't describe it. Send to the agent Do it by hand A new page or section Spacing, padding, gaps New behaviour (a form, a filter, a search) One colour or font size Refactors and data changes A line of copy, a typo "Make this page work like that one" A different photo or link The same thing, but only on phones The right column is where prompts get expensive for what they are. The change is tiny, but explaining it precisely takes longer than doing it. Option 1: stay in your editor You don't need a tool for this. Two habits make hand edits on agent-written code a lot faster. Find the element by its classes, not its file. Open the page in the browser, inspect the element, copy a class that looks unique, and search for it: grep -rn "py-24" src/
Agents tend to repeat the same class strings, so if you get several hits, add a second class from the same element to the search. Change one breakpoint at a time. Tailwind is mobile first: an unprefixed class applies everywhere, and md: and up only kick in on wider screens. So "smaller on phones only" means changing the unprefixed class and putting the old value back on md::