DEV Community

Cover image for Edit a Claude Code site visually without spending tokens on padding
Xodia AI
Xodia AI

Posted on AI-assisted

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/
Enter fullscreen mode Exit fullscreen mode

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

<!-- before -->
<h1 class="text-6xl font-bold">

<!-- after: smaller on phones, same on desktop -->
<h1 class="text-4xl md:text-6xl font-bold">
Enter fullscreen mode Exit fullscreen mode

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 git@github.com:you/your-site.git
git push -u origin main
Enter fullscreen mode Exit fullscreen mode

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
Enter fullscreen mode Exit fullscreen mode

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 Code. It picks up the request knowing exactly which element you meant, so you skip the "the second card in the pricing section, no, the other one" part.

5. Push like normal

Your edits and Claude Code's land side by side. When you're happy, push them as a commit to your branch, open a PR if you review changes, and your host deploys as it does today. Pushing to your own GitHub is on the paid plans; on the free plan your edits stay saved in Xodia until you upgrade.

What we'd still ask the agent for

To be fair to the agent: anything that needs a decision. A new section that has to match the rest of the site, a form that sends somewhere, a page that pulls from a CMS. Those are worth the tokens, and the agent is good at them.

The win is not paying for "4px less padding" at the same rate.

If you want the longer version with every step, we wrote a guide: Edit a site built with Claude Code, visually.

What's the smallest change you asked an agent for this month?

Top comments (0)