Edit Claude Code Sites Visually Without Extra Tokens

Zusammenfassung

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::

That's the whole trick, and it works fine for a handful of edits. It gets slow when you're making twenty of them while someone looks over your shoulder. Option 2: edit it visually, on the same code This is the part we build. Xodia opens your repo as it is, shows the site, and lets you click things and change them. The edits are written back into your files as normal code: Tailwind classes stay Tailwind classes, plain CSS stays plain CSS. 1. Put the code on GitHub If Claude Code built the site in a local folder, push it to a repo first: git init git add . git commit -m "Site built with Claude Code" git branch -M main git remote add origin [email protected]:you/your-site.git git push -u origin main 2. Import the repo In Xodia, connect GitHub under Connections, then New project, Import from GitHub, and pick the repo. Xodia detects the framework and styling and opens the site. It works with React or plain JavaScript on Vite (with or without React Router) and plain HTML sites, styled with Tailwind 4, plain CSS, CSS Modules or Sass. Next.js and Astro sites are refused at import, with the reason, rather than half working. 3. Click and change Click any element on the page. Double-click text to type. The Style panel on the right has spacing, size, colour and layout, and it changes the classes on that element only. For "only on phones", pick a phone width in the top bar and make the change there. It's written as a class for that screen size, so the desktop layout stays as it was. None of this uses AI credits. It's just editing. 4. Keep Claude Code on the same site Here's the part that makes the split work. Connect Claude Code to Xodia and it edits the same project you're looking at: claude plugin marketplace add https://app.xodia.ai/plugin/marketplace.json claude plugin install xodia@xodia Restart Claude Code, type /mcp, pick xodia and sign in. Now when something is too big to do by hand, select the element, type the request in the ask box, and run /xodia:work in Claude Cod... ![Embed Image](https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqxm7uz1kp1rwcqedw633.png) *Powered by Readybot.io*

Das Neueste von Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …