Applying a Brand to a Replo Site

Re-skin a Replo site with a brand. This is almost entirely a token edit: Replo sites are built token-first, so every color/font/radius flows from the semantic token layer in app/globals.css. Applying a brand means rewriting those token values (plus the font and logo) — not repainting page components.

You still use judgment to map the brand palette onto the semantic roles and to choose readable foregrounds, but a site-wide application should not require hand-editing section JSX. Keep literal colors in the token layer.

Working on a Replo site from your own machine

A Replo site is a Next.js repo you can clone and edit directly:

1. Resolve the site: list_projects → list_sites (use the default site unless the user names one). Each site returns a clone_url.
2. Follow the local-development skill to mint a key, clone, and prepare any requested push. Include repo.write only when the user asks you to push.
3. pnpm install && pnpm dev gives a local preview. The Replo agent is a second writer of the same repo — pull before editing and push only when the user asks; never force-push.
4. Publish with the publish_site tool only when the user explicitly asks.

Getting the brand

The project's brand kit lives in Branding, outside the site repo.