Cargando

Cargando...

Skip to content
CubicLauncherDocs

Creating a theme

A step-by-step guide to creating a CubicLauncher theme from scratch — palette, background, typography, icons, custom CSS, packaging and publishing.

A theme changes the entire look of CubicLauncher: colors, typography, background, icons and interface details. There is nothing to compile and no launcher code to touch: a theme is two text files plus, if you want, some images and fonts.

This guide builds a real theme from start to finish, in short steps, with a checkpoint after each one. By the end you will have an installable, published ZIP.

Before you start
  • A text editor and a program to create ZIP files.
  • A recent version of CubicLauncher.
  • Ten minutes for your first working theme.

If you only want to install a theme made by someone else, see How to install a theme.

How a theme worksedit

The launcher reads the theme files, turns them into CSS variables and applies them to the interface. That is why almost everything is customized by declaring values, without writing selectors:

text
Meta.toml        → identity: name, author, version, inheritance
Definition.toml  → appearance: colors, background, fonts, icons
Inject.css       → details the variables cannot reach (optional)
Layout.css       → restructure the frame (optional)

Each key in Definition.toml produces a variable with a fixed prefix. For example, accent = "#8FBF6A" in [colors] becomes --accent, and primary = "#E6EFDC" in [text] becomes --text-primary.

There are two versions of the format. This guide uses V2, the current one. V1 (theme.json) is still loaded for compatibility, but it does not support icons, inheritance or custom CSS.

Step 1 — Create the folder and the manifestedit

Create a folder for your theme, for example bosque, and inside it a Meta.toml file:

toml
name = "Bosque"
author = "your_username"
version = "0.1.0"
description = "Dark theme with a green accent and a forest background."
format = 2
api_version = "2.1"

Those fields are enough for a valid theme. format must be exactly 2, and api_version declares the API series the theme was written against: currently "2.1".

Then add Definition.toml with a single empty section for now:

toml
[colors]

Compress the folder into a ZIP and drag it onto the launcher window.

Checkpoint: the theme appears in the selector as Bosque and, when activated, the interface looks the same as before. That is correct: you have not changed any values yet.

Name and identifier

The launcher generates the internal identifier from name and author: "Bosque" + "your_username" is saved as bosque_your_username in ~/.cubic/themes/. That identifier is the one used to inherit from another theme.

Step 2 — Define the paletteedit

A theme stands on five colors: background, surface, text, accent and border. Choose them before writing anything, so the rest comes out coherent.

Add these two sections to Definition.toml:

toml
[colors]
accent = "#8FBF6A"
accent-rgb = "143, 191, 106"
accent-hover = "#A5D182"
accent-text = "#0B120A"
bg-main = "#0B0F0B"
bg-sidebar = "#0F150F"
bg-card = "#131A13"
bg-input = "#080C08"
bg-item-active = "#1B261B"
bg-overlay = "rgba(5, 8, 5, 0.72)"
border-color = "rgba(143, 191, 106, 0.18)"

[text]
primary = "#E6EFDC"
secondary = "#AEBBA2"
muted = "#74806B"

What each one does:

KeyEffect
bg-mainWindow background.
bg-sidebarSidebar background, one step lighter than the main background.
bg-cardCards, modals and panels.
bg-inputText fields, one step darker.
accentButtons, focus rings, links and active elements.
accent-textText that goes on top of the accent.
border-colorBorders and separators.

Checkpoint: the launcher changes immediately. If a color is not applied, check that the key is in the correct section and look at the console: duplicate names produce a collision warning.

The two triplets people forget

accent-rgb must be the same color as accent, written as R, G, B without rgb(). The interface uses it in rgba(var(--accent-rgb), 0.15) for glows and borders. If you forget it, those details keep the original white.

surface-rgb works the same way, but for translucent surfaces. In a dark theme it is 255, 255, 255 (the default); in a light theme it must be 0, 0, 0, or borders become lighter instead of darker.

Step 3 — Adjust borders, shadows and measurementsedit

With the palette ready, define the shapes. These sections are optional, but they are what makes a theme look finished instead of just recolored:

toml
[borders]
radius = "10px"
radius-sm = "6px"
radius-lg = "18px"

[shadows]
shadow-sm = "0 2px 8px rgba(0, 0, 0, 0.28)"
shadow-md = "0 10px 28px rgba(0, 0, 0, 0.36)"
shadow-lg = "0 18px 52px rgba(0, 0, 0, 0.50)"

[layout]
sidebar-width = "248px"

[spacing]
md = "12px"
lg = "16px"

[borders] adds the --border- prefix, [spacing] adds --space-, and [layout] adds none: the key is the full variable.

Checkpoint: corners change radius, cards gain depth and the sidebar becomes wider or narrower.

Step 4 — Add a background imageedit

The background is what contributes the most identity. Put the image inside the theme folder and declare it with a relative path:

toml
[background]
reference_path = "bg.webp"
image_blur = 12.0
image_opacity = 0.32
mode = "cover"
position = "center"
brightness = 0.45
KeyWhat it controlsUseful range
reference_pathPath to the image, relative to the theme.—
image_blurBlur in pixels.0 to 24
image_opacityTransparency of the layer.0.2 to 0.6
modeFraming: cover, contain.—
positioncenter, top, bottom left…—
brightnessImage brightness.0.3 to 0.7

The lower brightness is and the higher the opacity, the more readable the text but the less visible the image. The sweet spot is usually brightness between 0.35 and 0.5 and image_opacity near 0.35.

Checkpoint: the image appears behind the content, blurred and darkened, without blocking readability.

Background limits

The image cannot exceed 25 MB and must be a real image file. The launcher checks the file header, not the extension: a .png that is actually text is discarded.

Use relative paths. Absolute paths and file: work on your machine, but break the theme anywhere else.

Step 5 — Custom typographyedit

You can use any font that is inside the package. Copy the files to fonts/ and declare each variant:

toml
[[fonts]]
family = "Inter"
src = "fonts/Inter-Regular.woff2"
weight = "400"
style = "normal"

[[fonts]]
family = "Inter"
src = "fonts/Inter-SemiBold.woff2"
weight = "600"
style = "normal"

[typography]
family = "Inter, system-ui, sans-serif"
size_base = "14px"
line_height = "1.5"

The important rule: [typography].family must mention the same family you declared in [[fonts]]. If the name does not match, the font loads but the interface keeps using the default typography.

Checkpoint: headings and text change shape. If nothing changes, check the family name and that the src path exists inside the ZIP.

How many fonts

One or two families are enough. Above 12 the selector shows a warning, and the launcher only loads the first 20 variants.

Step 6 — Iconsedit

Icons are declared by group. The final key is group:name, and it must match exactly the name requested by the component.

toml
[icons]
preview = "icons/preview.png"

[icons.nav]
settings = "icons/nav/settings.svg"
create = "icons/nav/create.svg"

[icons.ui]
play = "icons/ui/play.svg"

preview is the image that represents your theme in the selector; it should ideally be a screenshot of the launcher with the theme applied.

SVGs are used as a mask: they are painted with the text color, so a monochrome icon works in both light and dark themes. PNG, WEBP and JPG are drawn with their own colors.

Checkpoint: the sidebar icons change. If an icon does not change, the key does not match the real name: the full list is in the Token reference.

Step 7 — Fine details with CSSedit

Variables cover almost everything, but some things can only be solved with CSS: pseudo-elements, animations, separators. That is what Inject.css is for.

Declare the section in Definition.toml and create the file:

toml
[inject]
path = "Inject.css"
enabled = true
layer = "theme"
css
/* Inject.css */
[data-part="sidebar"] {
  border-right: 1px solid var(--border-color);
}

[data-part="sidebar"] .sidebar-header {
  letter-spacing: 0.04em;
  text-transform: uppercase;
}

The key is in layer:

  • theme (the default) wraps your CSS in @layer cubic.theme. It beats the launcher's global styles, but loses to each component's styles.
  • unlayered leaves the CSS without a layer. It competes on specificity with everything, including components. It is more powerful and more fragile.

Checkpoint: the change applies without restarting. If you see no effect, try layer = "unlayered" before assuming the selector is wrong.

CSS and updates

Avoid depending on classes generated by Svelte (the ones ending in a hash) and on internal structures. data-part attributes are stable; the rest may change between versions.

Step 8 — Package, install and testedit

  1. The folder must have Meta.toml and Definition.toml at its root, next to the assets.
  2. Compress it into a ZIP. The files can be at the ZIP root or inside a single containing folder.
  3. Change the extension to .cbth if you want to use the theme package format: it is the same ZIP under a different name.
  4. Install it by dragging it onto the launcher window or from Settings → Themes → Import theme.
  5. Select it in the selector.

How the launcher handles the package:

  • It looks for Meta.toml at the root or in a containing folder. If it finds more than one, it rejects the ZIP.
  • If Meta.toml and theme.json coexist, V2 wins.
  • A .zip is tried first as V1 and then as V2; a .cbth is only interpreted as V2.
  • Installation is atomic: it is unpacked into a temporary folder and moved to the destination. If validation fails, nothing is left half-done.
  • The destination is ~/.cubic/themes/<id>/. Reimporting a theme with the same name and author replaces the previous version.

Test changes without reimportingedit

While the theme is active, the launcher watches its folder and reloads on its own. Edit the files in ~/.cubic/themes/<id>/ and watch the result live: it is much faster than compressing and reimporting on every adjustment.

The diagnostics panel in the theme selector warns about three things that do not block loading but affect performance: more than 12 fonts, CSS over 256 KiB and backgrounds over 4096×4096 pixels.

Step 9 — Publish to the catalogedit

Community themes live in CubicLauncherDevs/Themes and appear at cubiclauncher.org/themes.

text
src/
└── TuAutor/
    └── TuTema/
        ├── theme.md          # theme description
        ├── vflag.txt         # optional, staff only: marks the theme as verified
        └── V1/
            ├── Meta.toml
            ├── Definition.toml
            ├── bg.webp
            ├── Showcase.png  # optional, screenshot for the catalog
            └── fonts/
  1. Fork the repository.
  2. Create src/TuAutor/TuTema/theme.md with a short description.
  3. Create src/TuAutor/TuTema/V1/ with Meta.toml, Definition.toml and the assets.
  4. Open a Pull Request.

Continuous integration optimizes the images, generates the preview, uploads the binaries to the catalog storage and updates themes.json. Binaries are not stored in Git.

Optimizing the themeedit

A theme is read every time it is activated: the launcher parses both manifests, validates the background by opening the file, checks each icon, resolves each font and loads the CSS into memory. Then the frontend decodes the image and registers the typefaces before showing the full interface. A heavy theme does not look better: it takes longer to appear.

These are the decisions with the biggest impact, from largest to smallest.

The background: the largest image and the one that needs the least detailedit

The image is drawn blurred and with low opacity, so its resolution is barely noticeable. A 1600×900 background looks the same as a 4K one after blurring, but weighs eight times less and decodes instantly.

PracticeWhy
Export in WebP at quality 75–85.Same look as a PNG at a fraction of the weight.
Lower the resolution to 1600×900 or 1920×1080.Blur hides the lack of detail.
Aim for under 500 KB.The limit is 25 MB, but the real target is different.
Blur the image in your editor and use a low image_blur.Live blur is recalculated over the whole window.
Avoid more than 4096×4096.The selector warns about memory usage when decoding it.

A high image_blur on a large image is the most expensive combination: you pay for the blur on every repaint. If the image is already blurred, image_blur = 0 gives the same result at no cost.

Fonts: only what is usededit

Every declared file is downloaded, registered and applied. A family with four weights adds four files.

  • Use WOFF2. It is the smallest format and the best supported.
  • Declare only the weights the theme really needs: usually 400 and 600.
  • Prefer fonts with a Latin subset; a font with Cyrillic, Greek and CJK can weigh ten times more.
  • Two families is the reasonable maximum. A single well-chosen one is enough for almost everything.

Icons: SVG and only the ones that changeedit

SVGs weigh a few KB and color themselves. Raster icons (PNG, WEBP, JPG) load with their own colors and usually weigh much more.

  • Replace only the icons that add identity. Every entry is validated when the theme loads, even if it is never shown.
  • Do not include an icon if the original already works for you.
  • If you use raster, keep it below 64×64 and 50 KB: the limit is 2 MB, but a 2 MB icon takes a while to appear.

CSS: variables first, selectors lateredit

Inject.css is loaded and interpreted on every activation. Anything that can be solved with a variable should be solved with a variable.

  • If you can change a color, radius or shadow from Definition.toml, do not write CSS.
  • Keep Inject.css under 16 KB; the recommended limit is 256 KiB.
  • Do not animate filter, backdrop-filter or box-shadow: they are the most expensive properties to repaint.
  • Avoid !important. If you need it, the selector is poorly chosen.
  • Do not duplicate in CSS what Layout.css already does.

Tokens: do not repeat default valuesedit

Every declared variable is injected into a stylesheet. Repeating the default value changes nothing and makes the theme harder to read.

  • Declare only the tokens that differ from the launcher.
  • If two keys generate the same variable, keep one: the other produces a collision warning.
  • For color variants, use extends instead of copying the whole palette.
  • Declare --color-scheme ("dark" or "light") in [others] so scrollbars and native controls match the theme.

Weight targetsedit

ResourceTargetTechnical limit
Complete ZIPunder 3 MB—
Background imageunder 500 KB25 MB
Fontsunder 300 KB total12 recommended, 20 loaded
Iconsunder 20, SVG100 preloaded
Inject.cssunder 16 KB256 KiB recommended
Declared tokens25 to 40 keys—

How to measureedit

  • Check the ZIP size before publishing: it is the number people who download it see.
  • The diagnostics panel in the theme selector warns if the background is too large, if there are too many fonts or if the CSS exceeds the size.
  • If the theme takes a while to appear when switching between themes, the problem is almost always the background image or the number of fonts.

Complete exampleedit

A Meta.toml and a Definition.toml ready to copy, with everything from the previous steps. The assets (bg.webp, fonts/, icons/, Inject.css) are optional: if they are missing, the launcher ignores them and continues with the rest of the theme.

toml
# Meta.toml
name = "Bosque"
author = "your_username"
version = "1.0.0"
description = "Dark theme with a green accent and a forest background."
format = 2
api_version = "2.1"
toml
# Definition.toml
[colors]
accent = "#8FBF6A"
accent-rgb = "143, 191, 106"
accent-hover = "#A5D182"
accent-text = "#0B120A"
bg-main = "#0B0F0B"
bg-sidebar = "#0F150F"
bg-card = "#131A13"
bg-input = "#080C08"
bg-item-active = "#1B261B"
bg-overlay = "rgba(5, 8, 5, 0.72)"
border-color = "rgba(143, 191, 106, 0.18)"

[text]
primary = "#E6EFDC"
secondary = "#AEBBA2"
muted = "#74806B"

[borders]
radius = "10px"
radius-sm = "6px"
radius-lg = "18px"

[shadows]
shadow-sm = "0 2px 8px rgba(0, 0, 0, 0.28)"
shadow-md = "0 10px 28px rgba(0, 0, 0, 0.36)"
shadow-lg = "0 18px 52px rgba(0, 0, 0, 0.50)"

[layout]
sidebar-width = "248px"

[background]
reference_path = "bg.webp"
image_blur = 12.0
image_opacity = 0.32
mode = "cover"
position = "center"
brightness = 0.45

[[fonts]]
family = "Inter"
src = "fonts/Inter-Regular.woff2"
weight = "400"
style = "normal"

[[fonts]]
family = "Inter"
src = "fonts/Inter-SemiBold.woff2"
weight = "600"
style = "normal"

[typography]
family = "Inter, system-ui, sans-serif"
size_base = "14px"
line_height = "1.5"

[icons]
preview = "icons/preview.png"

[icons.nav]
settings = "icons/nav/settings.svg"
create = "icons/nav/create.svg"

[inject]
path = "Inject.css"
enabled = true
layer = "theme"

Field referenceedit

Meta.tomledit

FieldTypeRequiredDescription
namestringYesVisible name. Cannot be empty.
authorstringRecommendedAuthor. Shown in lowercase and part of the identifier.
versionstringRecommendedVersion, ideally MAJOR.MINOR.PATCH.
descriptionstringOptionalOne-line description for the catalog.
formatintegerYesMust be exactly 2.
api_versionstringOptionalAPI series: "2.1". Any 2.x value is valid; any other value produces a warning.
injects_cssbooleanOptionalIf false, Inject.css is not loaded.
extendsstringOptionalIdentifier of an installed V2 theme to inherit from.

The identifier is calculated at import time: lowercase, spaces replaced by _, and the format name_author. Maximum 64 characters, without :, / or backslash.

How keys become variablesedit

SectionGenerated variableExample keyResult
[colors]--{key}accent = "#8FBF6A"--accent
[text]--text-{key}primary = "#E6EFDC"--text-primary
[borders]--border-{key}radius = "10px"--border-radius
[layout]--{key}sidebar-width = "248px"--sidebar-width
[shadows]--{key}shadow-md = "0 10px 28px #0006"--shadow-md
[backgrounds]--bg-{key}input = "#080C08"--bg-input
[backdrop]--backdrop-blur-{key}modal = 8.0--backdrop-blur-modal: 8px
[others]--{key}icon-filter = "invert(1)"--icon-filter
[typography]fixed tablesize_base = "14px"--font-size-base
[spacing]--space-{key}lg = "16px"--space-lg
[motion]--transition-{key}fast = "0.15s"--transition-fast
[components.name]--component-name-{key}—Reserved
[tokens]literal"--bg-image-blur" = "12px"--bg-image-blur

Precedence rules:

  • Sections are applied in the order of the table and [tokens] goes last, so it always wins.
  • If two keys produce the same variable, the last one wins and a Key collision warning is emitted. [colors] bg-main and [backgrounds] main are the same variable.
  • [tokens] is the way to set variables without their own section, such as --bg-image-blur or --font-family-mono. The key must start with --.
  • [components] becomes --component-* variables, but no component consumes them yet.

Values are copied to CSS as-is: if the CSS needs a unit, include it in the value ("12px", not "12").

Typographyedit

FieldVariable
family--font-family
size_base--font-size-base
size_sm--font-size-sm
size_lg--font-size-lg
size_control--font-size-control
size_label--font-size-label
weight_normal--font-weight-normal
weight_medium--font-weight-medium
weight_bold--font-weight-bold
line_height--line-height

Inheritance with extendsedit

A theme can inherit the tokens of another installed V2 theme:

toml
name = "Light forest"
author = "your_username"
version = "1.0.0"
format = 2
extends = "bosque_your_username"
  • extends takes the installed identifier, not the visible name. The user: prefix is accepted and discarded.
  • The base theme must be installed and be V2.
  • Maximum depth: 8 levels. A cycle is an error.
  • The child wins key by key: whatever it does not define, it inherits.
InheritedNot inherited
colors, text, borders, layout, shadowsfonts
backgrounds, backdrop, others, tokensicons
spacing, motion, components[inject]
typography field by field[layout_pack]
[background] field by fieldbackground.reference_path

Assets are not inherited because paths are relative to the theme that declares them.

Layout packedit

Layout.css is loaded last, without a layer, and is used to restructure the frame through stable attributes:

toml
[layout_pack]
path = "Layout.css"
enabled = true
data-partElement
appRoot container.
sidebarSidebar container.
sidebar-panelInner panel (normal or compact).
sidebar-headerSidebar header.
sidebar-contentSidebar content.
sidebar-sectionsList of sections.
contentMain area.
background-overlayBackground image layer.
css
/* Layout.css — floating sidebar */
[data-part="sidebar"] {
  margin: 8px;
  border-radius: var(--border-radius-lg);
  border: 1px solid var(--border-color);
  overflow: hidden;
}

Limits and validationsedit

ResourceLimitIf exceeded
Background image25 MB, valid imageThe background is ignored.
Raster icons2 MB, SVG/PNG/WEBP/JPGThe icon is ignored.
Number of icons100 recommendedOnly the first 100 are preloaded.
Fonts12 recommended, 20 loadedWarning; the rest are not loaded.
Inject.css256 KiB recommendedWarning; it is still loaded.
Background resolution4096×4096Warning about memory.
extends depth8 levelsError; the theme is not installed.
Identifier64 charactersError; the theme is not installed.

Common errorsedit

Message or symptomCauseSolution
No Meta.toml or theme.json foundThe ZIP does not have the manifest at the root or in a containing folder.Check the ZIP structure.
Invalid Meta.tomlMalformed TOML: unclosed quotes, repeated table.Validate the TOML with any linter.
format X not supported; expected 2format missing or different from 2.Add format = 2.
base theme 'x' is not installed or is not V2extends points to a nonexistent identifier.Use the identifier of an installed V2 theme.
Inheritance cycleA → B → A.Remove one of the extends.
Inheritance too deepMore than 8 levels.Flatten the chain.
Colors do not changeKey in the wrong section or nonexistent variable.Check the mapping table and the console.
A color stayed oldYou changed accent but not accent-rgb.Update the triplet.
The background does not appearWrong path, more than 25 MB or a file that is not an image.Use a relative path and a valid image.
The font is not applied--font-family does not mention the family or src does not exist.Check family, src and [typography].family.
An icon does not changeThe key does not match group:name.Copy the exact name from the reference.
Inject.css has no effect[inject] is missing or the selector loses by layer.Declare [inject] and try layer = "unlayered".

Checklistedit

Before sharing a theme:

  • format = 2 and a non-empty name.
  • The ZIP opens with Meta.toml and Definition.toml at the root or in a containing folder.
  • accent-rgb matches accent; surface-rgb is consistent with the light or dark theme.
  • Contrast of at least 4.5:1 between --text-primary and --bg-main.
  • The background weighs less than 25 MB and uses a relative path.
  • Fonts are inside the package, with a compatible license, and --font-family mentions them.
  • Icons use exact group:name keys.
  • If you use extends, the base theme is V2 and is installed.
  • You tested normal, compact and maximized windows.
  • The theme installs from scratch in a clean copy of the launcher.

Designing themes with AIedit

An agent can write a complete theme if it receives the exact format, token names and restrictions. Without that, it invents variables that do not exist and the result is not applied. And without a weight budget, it tends to fill the theme with resources that add nothing.

Format contractedit

Minimum summary to give a model:

  • Two mandatory files: Meta.toml and Definition.toml.
  • Meta.toml: name, author, version, description, format = 2, api_version = "2.1".
  • Definition.toml: sections [colors], [text], [borders], [shadows], [layout], [backdrop], [others], [typography], [spacing], [motion], [tokens].
  • Prefixes: [colors] and [layout] without a prefix; [text] → --text-, [borders] → --border-, [spacing] → --space-, [motion] → --transition-.
  • accent-rgb and surface-rgb are R, G, B triplets without rgb().
  • Values include a unit when CSS needs one.
  • Only the tokens in the reference exist: no new names are invented.
  • Minimum contrast 4.5:1 for main text.

Optimization rulesedit

An AI-generated theme tends toward overload: it declares all 60 variables even if only 20 change, adds an unnecessary Inject.css and proposes a 4K background. These restrictions prevent that:

  • Minimum viable: only the keys that change the result. If the value matches the launcher's, leave it out.
  • No CSS unless explicitly requested: anything solved with tokens is solved with tokens.
  • Five color roles: background, surface, text, accent and border. Nothing else.
  • No invented assets: do not ask for images or fonts the user does not have. If a background is needed, give the dimensions instead of a file.
  • Weight budget: background < 500 KB, fonts < 300 KB, icons < 20, Inject.css < 16 KB.
  • Stable order: always the same sections, in the same order, with one comment per section. That way the file can be reviewed at a glance.

Base promptedit

text
Create a V2 theme for CubicLauncher: clean, minimalist and optimized.
Return two code blocks, Meta.toml and Definition.toml.

Meta.toml, in this order:
name, author, version, description, format = 2, api_version = "2.1"

Definition.toml:
- Use only these sections: [colors], [text], [borders], [shadows], [layout],
  [typography], [tokens].
- Write only the keys that change the result. Do not repeat default values
  or add keys you will not use.
- Each section gets a one-line comment explaining its intent.
- Do not generate Inject.css, Layout.css or asset files.

Palette, five roles and nothing more:
background <color>, surface <color>, text <color>, accent <color>, border <color>

Mandatory rules:
- accent-rgb repeats accent as "R, G, B". surface-rgb is "255, 255, 255"
  in dark themes and "0, 0, 0" in light ones.
- Minimum contrast of 4.5:1 between --text-primary and --bg-main.
- All values include a unit when CSS needs one (px, rem, s).
- Do not invent variables: use only tokens that exist in the reference.
- If you declare [background], use a relative path and conservative values:
  image_opacity between 0.25 and 0.4, brightness between 0.35 and 0.5, image_blur 0 to 12.

Outside the blocks, add three lines:
1. Recommended typeface family and the weights needed.
2. Ideal dimensions and format for the background.
3. What to trim if the theme turns out heavy.

How to avoid generic resultsedit

  • Choose the colors before the prompt. A model tends to return the same violet on gray if you do not give it a direction.
  • Ask for roles, not loose values. "Almost-black background with a green tint, desaturated surfaces, saturated lime-green accent" produces better results than "green theme".
  • Set contrast as a requirement. Without that restriction, secondary text becomes unreadable.
  • Check the triplets. It is the most common mistake in generated themes: accent changes and accent-rgb stays white.
  • Iterate on the file, not on the prompt. Ask for the theme, install it and adjust concrete values; it is faster than rewriting the instruction.
  • Ask for the budget, not just the palette. "1600×900 WebP background, two weights of a single family, no extra CSS" prevents the result from arriving with twelve megabytes of assets.