How to set up your brand colours in MarketMee

Nothing gives away "this was auto-generated" faster than the wrong colours. A post can have a sharp headline and a clear screenshot, but if the accent colour is a generic blue that has nothing to do with your product, it reads as a template. The good news for developers is that your brand colours already live in your code—and MarketMee can pull them straight from there.

This guide walks through how MarketMee detects your brand colours, how to check and override them, and why getting this right once pays off on every image and video you ever generate.

Where MarketMee gets your colours from

When you connect a repository, MarketMee looks at your styling code to figure out what your brand actually looks like. It reads the places developers really keep their colours:

• Tailwind config — your theme.colors and custom palette
• CSS variables — the custom properties you define for theming
• Theme files — wherever your design tokens live

If it can't find colours in the code, it falls back to your website. On top of the palette, it also detects whether your app is light or dark, so generated artwork matches the mood of your product instead of fighting it.

The practical upshot: if your repo is connected and your styling is in one of those places, your marketing images show up in your real colours without you lifting a finger. That's the whole point—your brand lives in your codebase, so your marketing should too.

Check the detected colours during onboarding

The best moment to get this right is the first one. When you sign up, MarketMee's onboarding walks you through setup, and one of those steps is confirming your brand.

1. Enter your company name, what you do, and your website.
2. Pick the image and headline styles you like.
3. Check the brand colours MarketMee detected from your code—or set your own.

Take the extra minute on step three. Everything generated afterward—your free sample video, your three sample images, and every post you make later—leans on these colours. Setting them correctly on day one means you never have to think about it again, and it means the free sample you're about to generate actually looks like your product.

How to override colours per repository

Detection is a strong starting point, but you know your brand better than any parser. You can override the colours whenever you want.

MarketMee lets you set up to 6 brand colours per repository, plus a Light/Dark choice per repository. The per-repo part matters more than it sounds:

• If you run multiple products out of different repos, each one keeps its own palette. A post generated from your billing dashboard repo won't come out in your side project's colours.
• If a repo's styling code is messy or incomplete, you can correct just that repo without touching the others.
• The Light/Dark choice lets you match the actual feel of each app—a dark developer tool and a bright consumer app shouldn't share the same backdrop.

Six colours is usually plenty: a primary, a secondary or accent, and a few supporting tones for backgrounds and text. Pick the ones that make your product instantly recognisable.

Set colours globally in Settings

If you only have one brand—or you want a consistent look across everything regardless of repo—you don't have to repeat yourself. You can set your brand colours once in Settings for all repositories.

Use the global option when:

• You maintain a single product and every post should look the same.
• You want a house style across several repos that don't each need their own identity.

Use per-repository overrides when different repos represent genuinely different products or sub-brands. You can start global and add per-repo overrides later as your set of projects grows.

Why colours matter more in MarketMee than you'd expect

It helps to understand how MarketMee builds a Marketing Image, because your colours thread through the whole pipeline. Every image is made the same way:

• Claude writes the exact words from your commits—the headline and any supporting copy.
• An image model paints the finished image with those words baked in, in your brand colours.
• Claude proofreads the result, repainting once if any word came out wrong.

Your palette isn't layered on at the end—it's part of the brief the image is generated against. That's why setting it correctly up front changes every output, not just a background swatch. The same brand colours carry into Product Videos too, where you can fine-tune on-screen colours in the Narration beats panel using free Direct edits if a specific scene needs a tweak.

And because Autopilot rotates through your preferred image and headline styles automatically, your colours become the constant that keeps a week of hands-off posts looking coherent. You set the palette once; Autopilot keeps every generated post on-brand while you're heads-down building.

A quick setup checklist

To get your brand dialled in from the start:

1. Connect the repository so MarketMee can read your Tailwind config, CSS variables, or theme files.
2. Review the detected colours during onboarding—don't skip the confirmation step.
3. Override up to 6 colours per repository if the detection missed anything, and set the Light/Dark choice to match the app.
4. Set colours globally in Settings instead if you run a single brand everywhere.
5. Generate your free sample and look at the result with a critical eye—if a colour's off, fix it now, before you build a content calendar on top of it.

Getting brand colours right is one of those rare setup tasks that's genuinely done once and benefits forever. Spend five minutes on it when you first connect your repo, and every image and video MarketMee makes afterward will look like it came from your product—because, down to the hex code, it did.

Ready to see your own colours in action? Connect a repo and generate your free sample at marketmee.app.