Skip to content
Back to use cases

Website and Product UI Direction

Make the product stop looking default.

The Rebrand Prompt and Foundation Prompt give AI coding tools brand context. Studio extends that logic into website direction: layout energy, visual rules, copy posture, and asset cues that all trace back to the Brand Schema.

Reskin what you already built

What breaks

You built an MVP in Bolt. It works. It still looks like a Bolt app.

What to do

Copy your Rebrand Prompt. Paste it into the tool. Run it against the product you already have. Then use Studio preview as the direction for what the next asset layer should look like.

What changes

  • It rewrites the color system
  • It shifts typography to match the brand character
  • It changes spacing and layout energy
  • It replaces default copy with your voice rules
  • It applies your never-do constraints
  • It creates a path toward Studio website and campaign assets
Before

Purple gradients, Inter at 400, "powerful solutions"

After

Ochre accents, editorial serif, "built for clarity"

Start with the brand locked in

What breaks

You are starting clean. You do not want to rebuild the brand later.

What to do

Start with the Foundation Prompt before the first serious build pass.

What the prompt carries

  • Visual direction: color, type, spacing, density
  • Voice rules: sounds like, never sounds like, banned words
  • Component patterns that match the brand energy
  • Example copy in the right voice
Foundation Prompt for a Sage-archetype dev tool: "Use deep navy (#1a2332) for backgrounds. Headlines in Caudex serif. Body text should be technically precise, never use 'powerful' or 'robust'. Buttons are calm, not urgent. No countdown timers."

Stop Lovable from reverting to default SaaS

What breaks

Lovable moves fast. It also drifts toward familiar startup patterns unless you force the context.

What to do

Put the Brand Schema into project context and make the model work inside your boundaries. The point is not a better prompt. The point is a source the tool can inherit from.

How to lock it

  • Copy the Brand Schema and the core outputs
  • Add them to Lovable's project context
  • Produce from that context, not from scratch
  • Review every pass against your constraints

Result: the tool produces inside your constraints, not inside its defaults.

Ready to stop shipping default-looking product work?

Build the Brand Schema. Then use it as the source for prompts, website direction, and Studio assets.

See the demo