Changebrandingandcolourswithoutaredeploy

Agent-built apps tend to bake the brand in. The colours live in the code, the logo lives in the code — so changing either means going back to your agent, describing the tweak, rebuilding, and redeploying. That is a lot of ceremony for swapping a hex value.

VibeKit moves branding out of your code and into the admin. The Branding tab lets you set a logo and a colour theme; apply it and your live app updates immediately — no redeploy, no rebuild, no waiting.

One tab, the whole look

Open Branding, pick the logo, pick the theme, apply. Your published app picks the change up on the spot, because the look was never compiled into the site in the first place — it is read at runtime, from the place you just edited.

Themes you can keep and reuse

Themes are not one-offs. Keep a small library of them and choose which theme each app uses. Built the same kind of app for a second client, or running a seasonal variant of your own? Point the app at a different theme instead of restyling it by hand — a workflow that pays off fastest when you're shipping apps for clients.

Your agent reads it instead of hardcoding it

This works because your agent wires the site to read its theme through the VibeKit client. Instead of scattering hardcoded colours through components, the app asks VibeKit for the current theme and uses what you set in the admin. The brand has one source of truth, and it is a tab you control — not a value buried in a stylesheet.

Branding is just the start

The same change-it-live idea covers more than colours. Headlines, phone numbers, and on/off feature switches can all live in the admin and update in your running app the moment you edit them — see variables and flags for the rest of the picture.