Extras and Integrations
SilkCircuit is one palette wearing thirty-one different formats. The themes under extras/ are generated from lua/silkcircuit/variants.lua by make build, in all five variants, so the hex your terminal draws is the hex your editor draws and CI fails if the two drift apart. The Chrome themes come from make chrome, which reads the same palette as JSON, and each target's README.md is written by hand. The full pipeline, and why it works this way, is on How It's Built.
Dawn is the light variant. Neon, vibrant, soft, and glow are dark.
Install everything at once
The installer detects what you have, drops each theme where its tool looks for it, and prints the one line that turns it on.
git clone https://github.com/hyperb1iss/silkcircuit.git
cd silkcircuit
./install.sh --dry-run # see what it would touch
./install.sh # all five variants, side by side
./install.sh --variant glow.\install.ps1 -Variant neonAnything it overwrites is copied to *.silkcircuit.bak first, and it refuses to add untracked files to a dotfiles repo it does not own. Tools that read a single file rather than a directory of themes (lsd, procs, Starship, fastfetch, dircolors, dmesg) take neon unless --variant says otherwise.
Editors
| Extra | What it covers |
|---|---|
| VS Code | Five themes in one extension |
| Helix | Syntax, markup, diffs, diagnostics, interface |
| AstroNvim | A complete AstroNvim configuration |
| Neovim Plugins | The flagship theme's plugin integrations |
Terminals
The terminal guide has the install path and enable line for all eight in one table, plus the ANSI contract they share.
Kitty · Alacritty · Ghostty · WezTerm · Warp · foot · iTerm2 · Windows Terminal
Multiplexers
| Extra | Turn it on |
|---|---|
| tmux | source-file ~/.config/tmux/silkcircuit-neon.conf |
| Zellij | theme "silkcircuit-neon" |
Shell and CLI
| Extra | Turn it on |
|---|---|
| Starship | Copy to ~/.config/starship.toml |
| fzf | source ~/.config/fzf/silkcircuit-neon.sh |
| bat | --theme=silkcircuit-neon, then bat cache --build |
| lsd | color: theme: custom |
| procs | Copy to ~/.config/procs/config.toml |
| fastfetch | Copy to ~/.config/fastfetch/config.jsonc |
| GNU dircolors | Copy to ~/.dircolors, then evaluate dircolors -b |
| Atuin | [theme] name = "silkcircuit-neon" |
Git
| Extra | Turn it on |
|---|---|
| Git | git config --global --add include.path <file> |
| lazygit | Merge the gui.theme block into your config |
System and desktop
| Extra | Turn it on |
|---|---|
| btop | Esc, Options, Color theme |
| k9s | k9s.ui.skin: silkcircuit-neon |
| dmesg | ~/.config/terminal-colors.d/dmesg.scheme |
| COSMIC Desktop | Settings, Desktop, Appearance, Import |
Apps
| Extra | Turn it on |
|---|---|
| Chrome | Load unpacked from extras/chrome-theme/silkcircuit-neon/ |
| Slack | Paste the line into a custom theme |
Every generated file
Regenerate the lot with make build, and this table with make docs.
| Target | Format | Generated files |
|---|---|---|
| Alacritty | reference | extras/alacritty/silkcircuit-{neon,vibrant,soft,glow,dawn}.toml |
| Atuin | reference | extras/atuin/silkcircuit-{neon,vibrant,soft,glow,dawn}.toml |
| bat | reference | extras/bat/silkcircuit-{neon,vibrant,soft,glow,dawn}.tmTheme |
| btop | reference | extras/btop/silkcircuit-{neon,vibrant,soft,glow,dawn}.theme |
| COSMIC Desktop | reference | extras/cosmic/silkcircuit-{neon,vibrant,soft,glow,dawn}.ron |
| GNU dircolors | reference | extras/dircolors/silkcircuit-{neon,vibrant,soft,glow,dawn}.dircolors |
| dmesg | reference | extras/dmesg/silkcircuit-{neon,vibrant,soft,glow,dawn}.scheme |
| fastfetch | reference | extras/fastfetch/silkcircuit-{neon,vibrant,soft,glow,dawn}.jsonc |
| foot | reference | extras/foot/silkcircuit-{neon,vibrant,soft,glow,dawn}.ini |
| fzf | reference | extras/fzf/silkcircuit-{neon,vibrant,soft,glow,dawn}.sh |
| fzf (PowerShell) | reference | extras/fzf/silkcircuit-{neon,vibrant,soft,glow,dawn}.ps1 |
| Ghostty | reference | extras/ghostty/silkcircuit-{neon,vibrant,soft,glow,dawn} |
| Ghostty GTK chrome | reference | extras/ghostty/silkcircuit-{neon,vibrant,soft,glow,dawn}.css |
| Git | reference | extras/git/silkcircuit-{neon,vibrant,soft,glow,dawn}.gitconfig |
| Helix | reference | extras/helix/silkcircuit-{neon,vibrant,soft,glow,dawn}.toml |
| iTerm2 | reference | extras/iterm2/silkcircuit-{neon,vibrant,soft,glow,dawn}.itermcolors |
| k9s | reference | extras/k9s/silkcircuit-{neon,vibrant,soft,glow,dawn}.yaml |
| Kitty | reference | extras/kitty/silkcircuit-{neon,vibrant,soft,glow,dawn}.conf |
| lazygit | reference | extras/lazygit/silkcircuit-{neon,vibrant,soft,glow,dawn}.yml |
| lsd | reference | extras/lsd/silkcircuit-{neon,vibrant,soft,glow,dawn}.yaml |
| procs | reference | extras/procs/silkcircuit-{neon,vibrant,soft,glow,dawn}.toml |
| Slack | reference | extras/slack/silkcircuit-{neon,vibrant,soft,glow,dawn}.txt |
| Starship | reference | extras/starship/silkcircuit-{neon,vibrant,soft,glow,dawn}.toml |
| tmux | reference | extras/tmux/silkcircuit-{neon,vibrant,soft,glow,dawn}.conf |
| VS Code | reference | extras/vscode/themes/silkcircuit-{neon,vibrant,soft,glow,dawn}.json |
| Warp | reference | extras/warp/silkcircuit-{neon,vibrant,soft,glow,dawn}.yaml |
| WezTerm | reference | extras/wezterm/silkcircuit-{neon,vibrant,soft,glow,dawn}.toml |
| Windows Terminal | reference | extras/windows-terminal/silkcircuit-{neon,vibrant,soft,glow,dawn}.json |
| Windows Terminal (every scheme) | reference | extras/windows-terminal/silkcircuit.json |
| Zellij | reference | extras/zellij/silkcircuit-{neon,vibrant,soft,glow,dawn}.kdl |
| Zellij (every theme) | reference | extras/zellij/silkcircuit.kdl |
Color consistency
The palette files (palette/silkcircuit-<variant>.json) are the authoritative list: every color as hex, RGB, and HSL, with the sixteen ANSI slots under the terminal key. The same directory carries base16 and base24 scheme files for tinted-theming builders such as tinty and stylix, which covers targets SilkCircuit does not generate directly.
Nothing is retuned per tool. A color that reads as purple in Neovim reads as the same purple in btop, and changing it in one place changes it everywhere on the next make build.