How to Deploy Each Target#

This assumes you’ve already run through Irix on Your Terminal in Ten Minutes and have artifacts sitting in out/ (or a packaged install). It’s organized by the same four families irix targets groups its 24 targets into: terminals, shell, editors, portable/web. Every filename below has a -light (or otherwise mode-marked) sibling; see How to Switch Between Dark and Light for how each application actually switches between them.

irix deploy <name> only does something for a target with a real deploy_dest — copying straight from the packaged out/ tree to a live config path. For a generate-only target, irix deploy <name> is a harmless no-op (exit 0, nothing copied); you place the file yourself, as described per-target below.

Terminals#

Target	Deploys to	Clobbers app config?
`kitty`	`$XDG_CONFIG_HOME/kitty/kitty.conf` (+ `kitty-light.conf` alongside)	Yes — kitty’s primary config file, colors only
`alacritty`	`$XDG_CONFIG_HOME/alacritty/alacritty.toml` (+ `-light.toml`)	Yes — primary config, and bakes in a font/window/keyboard template (`Monoid Nerd Font` by default)
`ghostty`	`$XDG_CONFIG_HOME/ghostty/themes/irix-dark` / `irix-light` (extension-free)	No — a named theme file, not ghostty’s main config
`warp`	`$XDG_DATA_HOME/warp-terminal/themes/irix-dark.yaml` / `irix-light.yaml`	No — a named theme file
`tmux`	generate-only	n/a
`xterm256`	generate-only	n/a

Warning

kitty and alacritty deploy straight over each application’s primary config file — see the tutorial’s deploy warning for the kitty case. Back up an existing config before a real (non---dry) deploy of either.

Because ghostty and warp land as named theme files rather than overwriting anything, selecting one is a one-line edit in the app’s own config instead of a full file replacement:

ghostty: add theme = irix-dark (or irix-light) to $XDG_CONFIG_HOME/ghostty/config.
warp: pick “Irix Dark” / “Irix Light” from Warp’s own Settings → Appearance → Themes picker — Warp discovers anything dropped into its themes directory automatically.

The two generate-only terminal targets have no fixed destination:

tmux — out/terminals/tmux-irix.conf (and -light) is a sourceable snippet, not a full config. The rendered file even says so in its own header comment:
```
# Source from your own tmux.conf, e.g.: source-file ~/.config/tmux/tmux-irix.conf
```
Copy it wherever you like and add that source-file line to your real ~/.tmux.conf.
xterm256 — out/terminals/irix-xterm256.toml is a reference dump, not a config: all 256 indexed-color slots (0–15 curated ANSI, 16–255 the complete 240-entry Irix chamber set), each as an { index, color, name } row — the same shape Alacritty’s own colors.indexed_colors array expects. Paste the array under that key in an Alacritty config, or mine individual rows for an .Xresources file (XTerm*color18: #hex).

Shell#

Target	Deploys to
`lsd`	`$XDG_CONFIG_HOME/lsd/colors.yaml` (+ `colors-light.yaml`)
`btop`	`$XDG_CONFIG_HOME/btop/themes/irix-btop.theme` (+ `-light.theme`)
`zshcolors`	generate-only
`fzf`	generate-only
`dircolors`	generate-only
`starship`	generate-only
`delta`	generate-only

lsd and btop land automatically but still need one config line each to activate:

lsd: set color.theme: custom in lsd’s own $XDG_CONFIG_HOME/lsd/config.yaml — lsd then reads colors.yaml by default. There’s no lsd option to point at an alternate filename directly, so switching to the light sibling means swapping which file is named colors.yaml (see How to Switch Between Dark and Light).
btop: set color_theme = "irix-btop" in btop’s own config, or pick it live from btop’s in-app Options → color theme menu.

The five generate-only shell targets each want a line added to your own config:

# ~/.zshrc — zshcolors: sets bg_/fg_/sh_/hl_ vars for a prompt theme to consume
source ~/.config/shell/irix-colors.zsh

# ~/.zshrc — fzf: exports FZF_DEFAULT_OPTS
source ~/.config/shell/irix-fzf.zsh

# ~/.zshrc — dircolors: standard GNU dircolors usage
eval "$(dircolors ~/.config/shell/irix-dircolors)"

# ~/.config/starship.toml — paste the whole rendered [palettes.irix] /
# [palettes.irix-light] section in, then select one:
palette = "irix"

# ~/.gitconfig — either paste the rendered [delta] section directly, or:
[include]
    path = ~/.config/git/irix-delta.gitconfig

Editors#

Target	Deploys to
`sublime`	`~/.config/sublime-text/Packages/User/irix-dark.sublime-color-scheme` (+ `irix-light...`)
`vim`	generate-only
`vscode`	generate-only
`kimi`	generate-only

Note

sublime’s deploy_dest is XDG-independent by design: it always resolves ~/.config/sublime-text/Packages/User/... via Path.home(), ignoring $XDG_CONFIG_HOME even when it’s set to something else (verified — pointing XDG_CONFIG_HOME elsewhere and re-running irix deploy sublime --dry still targets ~/.config). Sublime Text itself doesn’t consult XDG on Linux, so the target doesn’t pretend it does.

Pick “Irix Dark” / “Irix Light” from Sublime’s Preferences → Color Scheme menu once deployed.

The three generate-only editor targets:

vim — out/editors/irix.vim is the sanctioned dual-mode-single-artifact exception (see How to Add a New Target): one file, both &background branches wired inside it. Copy it to ~/.vim/colors/irix.vim (or ~/.config/nvim/colors/irix.vim for Neovim), then colorscheme irix — :set background=dark / :set background=light picks the half, no second file needed.
vscode — out/editors/irix-dark-vscode.json (+ irix-light-vscode.json) is a standard VS Code color-theme JSON (colors, tokenColors), the same shape a real VS Code theme extension ships under its themes/ folder. Without publishing one, the practical path is a minimal local extension: a ~/.vscode/extensions/irix-theme/ folder holding a package.json with a contributes.themes entry pointing at a copy of the JSON, then reload VS Code and pick it from the theme picker.
kimi — out/editors/irix-dark-kimi.json (+ irix-light-kimi.json) targets kimi-code’s own design-token theme format (base, flat semantic colors like primary/accent/ border — not VS Code’s shape). This repo doesn’t pin kimi-code’s theme-file location; consult its own docs for where a custom theme JSON goes.

Portable / Web#

Target	Family	Generate-only?
`gpl`	`inkscape`	Yes
`pymodule`	`python`	Yes
`swatches`	`web`	Yes
`slack`	`web`	Yes
`gsheets`	`browsers`	Yes
`cssvars`	`web`	Yes

Every target in this family is generate-only — none of these applications have a config location irix deploy could own, so each gets copied or pasted by hand:

gpl — out/inkscape/irix-{mode}.gpl (the curated 20-hue Irix set) and radix-{mode}.gpl (the full 34-hue Radix superset) are standard GIMP palette files. Drop them into GIMP’s ~/.config/GIMP/<version>/palettes/ or Inkscape’s ~/.config/inkscape/palettes/, then pick “Irix Dark” (etc.) from that app’s palette dropdown.
pymodule — out/python/irix.py is dependency-free and meant to be copied straight into a project, not installed as a package. It’s the dual-mode-single-artifact case for Python: one file carries both IRIX (dark) and IRIX_LIGHT, plus a MODES = {'dark': IRIX, 'light': IRIX_LIGHT} convenience lookup.
swatches — the reference sheets from See the palette; no further deployment, just a viewer.

slack — out/web/irix-{mode}-slack.txt holds an 8-hex custom-theme string with its own paste instructions baked into the file:

# Slack custom theme string -- paste at slack.com: profile photo -> Preferences ->
# Themes -> scroll to "Add a new theme" -> "Enter a color string".

gsheets — out/browsers/irix-{mode}-gsheets.user.css is a Stylus userstyle. With the Stylus browser extension installed, open “Write new style”, paste the file’s contents in, and save.
cssvars — out/web/irix-vars.css is the other dual-mode-single-artifact case: a single stylesheet whose :root block holds the light values and a .dark class block overrides them for dark. Link the file, then toggle dark mode by adding/removing the dark class on <html> or <body> — no separate light file to swap in.