https://github.com/web-dev-codi/cybersynth.nvim
Plugin-agnostic Neovim colorscheme made for the synthwave addics
https://github.com/web-dev-codi/cybersynth.nvim
agnostic lua neon neovim neovim-colorscheme neovim-lua-plugin neovim-plugin synthwave vaporwave wcag
Last synced: 7 days ago
JSON representation
Plugin-agnostic Neovim colorscheme made for the synthwave addics
- Host: GitHub
- URL: https://github.com/web-dev-codi/cybersynth.nvim
- Owner: Web-Dev-Codi
- License: mit
- Created: 2026-05-11T08:51:51.000Z (about 1 month ago)
- Default Branch: main
- Last Pushed: 2026-05-11T12:29:07.000Z (about 1 month ago)
- Last Synced: 2026-05-11T13:29:08.673Z (about 1 month ago)
- Topics: agnostic, lua, neon, neovim, neovim-colorscheme, neovim-lua-plugin, neovim-plugin, synthwave, vaporwave, wcag
- Language: Lua
- Homepage:
- Size: 55.7 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
cybersynth.nvim
Outrun for Neovim. Plugin-agnostic neon, AAA-accessible, on both dark and light.
---
## Why cybersynth?
Synthwave colorschemes are usually one of two things: gorgeous and unreadable, or readable and not actually synthwave. Cybersynth is built around three convictions.
**First, contrast is non-negotiable.** Every accent in the dark palette clears WCAG AAA (7:1) against the background. Every accent in the light palette clears AA (4.5:1). The neons are real. The neons are also legible at 4am on a 13" laptop.
**Second, themes should style ideas, not plugins.** Modern Neovim plugins link their highlights to semantic hub groups (`DiagnosticError`, `@variable`, `Added`, `FloatBorder`, and ~40 more) using `default = true`. Cybersynth carefully colors every one of those hub groups. The result: a plugin you install tomorrow — one we've literally never seen — looks correct the first time you load it. No integration table. No `enable = true` switches. No PRs every week to "please add support for X."
**Third, both modes deserve the same love.** The light variant isn't a desaturated afterthought. It uses the same hue families as the dark variant — magenta becomes mulberry, cyan becomes deep teal, violet becomes eggplant — recalibrated for paper. The violet hour, just slightly later in the day.
---
## Features
- 🔌 **Plugin-agnostic by design** — styles hub groups, not plugin names; works on plugins we've never seen
- ♿ **WCAG AAA on dark, AA on light** — every accent verified against its background
- 🌗 **First-class light mode** — same hue families, recalibrated lightness
- ⚡ **Zero required config** — `colorscheme cybersynth` and done
- 🎛 **Override anything** — palette, single highlights, per-variant, via `overrides`
- 🖥 **Terminal colors** — 16 ANSI colors set for both variants
---
📸 Gallery — dark, light, transparent (click to expand)
| Variant | Preview |
|---------|---------|
| **Dark** — the canonical sunset | 
|
| **Light** — the violet hour | 
|
| **Transparent** — float on your wallpaper | 
|
---
## Installation
### lazy.nvim
```lua
{
"Web-Dev-Codi/cybersynth.nvim",
lazy = false,
priority = 1000,
config = function()
require("cybersynth").setup({})
vim.cmd.colorscheme("cybersynth")
end,
}
```
Other package managers
**packer.nvim:**
```lua
use {
"Web-Dev-Codi/cybersynth.nvim",
config = function()
require("cybersynth").setup({})
vim.cmd.colorscheme("cybersynth")
end,
}
```
**vim-plug:**
```vim
Plug 'Web-Dev-Codi/cybersynth.nvim'
lua require('cybersynth').setup({})
colorscheme cybersynth
```
**dein.vim:**
```vim
call dein#add('Web-Dev-Codi/cybersynth.nvim')
```
**rocks.nvim:**
```lua
require('rocks').install('cybersynth.nvim')
```
**pathogen:**
```sh
cd ~/.vim/bundle && git clone https://github.com/Web-Dev-Codi/cybersynth.nvim
```
**Manual (runtimepath):**
```vim
set runtimepath^=/path/to/cybersynth.nvim
colorscheme cybersynth
```
---
## Usage
```vim
" Vimscript
colorscheme cybersynth
```
```lua
-- Lua
vim.cmd.colorscheme("cybersynth")
```
No need to call `setup()` unless you want to change something.
---
## Configuration
Full default config with inline docs:
```lua
require("cybersynth").setup({
variant = "auto", -- "dark" | "light" | "auto" (follows vim.o.background)
transparent = false, -- make Normal/NormalFloat/etc backgrounds NONE
italic = {
comments = true, -- comments in italic
keywords = false,
functions = false,
variables = false,
strings = false,
},
bold = {
functions = false, -- function names in bold
},
-- Per-group overrides applied after all highlights
overrides = {},
})
```
---
## Plugin Support
🔌 Plugin showcase — works out of the box, no config required
Cybersynth styles hub groups, not plugin names. Well-behaved Neovim plugins link to core highlight groups with `default = true`, so they inherit cybersynth's colors automatically. No `enable = true` switches needed.
Visually verified with:
- telescope.nvim, fzf-lua, snacks.picker
- nvim-cmp, blink.cmp
- neo-tree.nvim, oil.nvim, mini.files
- lualine.nvim (with `theme = 'auto'`)
- gitsigns.nvim, diffview.nvim
- nvim-treesitter, treesitter-context
- noice.nvim, nvim-notify, fidget.nvim
- which-key.nvim, flash.nvim
- indent-blankline.nvim
- trouble.nvim, todo-comments.nvim
- ...and ~40 more that use the same inheritance pattern.
---
## Overrides & Recipes
**Get the active palette:**
```lua
local colors = require("cybersynth").get_colors()
local palette = require("cybersynth").get_palette()
```
**Transparent background:**
```lua
require("cybersynth").setup({
transparent = true,
})
vim.cmd.colorscheme("cybersynth")
```
**Single highlight override:**
```lua
require("cybersynth").setup({
overrides = {
Comment = { fg = "#ff0000", italic = true },
["@keyword"] = { fg = "#ff7edb" },
},
})
vim.cmd.colorscheme("cybersynth")
```
**Lualine attach:**
```lua
require("lualine").setup({
options = {
theme = "auto", -- picks up StatusLine/StatusLineNC colors
},
})
```
---
## Palette
| Name | Dark hex | Light hex | Role |
|------|----------|-----------|------|
| Magenta |  `#ff7edb` |  `#b3007a` | variables, properties |
| Pink |  `#ff2d78` |  `#c2185b` | builtin variables |
| Cyan |  `#36f9f6` |  `#0e7c86` | functions |
| Sky |  `#89ddff` |  `#1976a8` | parameters |
| Mint |  `#72f1b8` |  `#1f7a5a` | strings, additions |
| Yellow |  `#fede5d` |  `#8a5a00` | keywords |
| Amber |  `#ffb86c` |  `#a64a00` | numbers alt |
| Coral |  `#f97e72` |  `#c43e5a` | numbers, constants |
| Red |  `#fe4450` |  `#a3001f` | errors |
| Violet |  `#c792ea` |  `#5b2a86` | types, classes |
| Lavender |  `#b893ce` |  `#7a4b9e` | git modified |
### Backgrounds
| Role | Dark | Light |
|------|------|-------|
| Deep (void) |  `#0d0d1a` |  `#e8e2f5` |
| Base (editor) |  `#1a1a2e` |  `#fbf6ff` |
| Alt (sidebar) |  `#241b2f` |  `#f4eef9` |
| Float (popup) |  `#2a2139` |  `#ede5f4` |
| Highlight (selection) |  `#34294f` |  `#e0d4ee` |
### Foregrounds
| Role | Dark | Light |
|------|------|-------|
| Base text |  `#f4f0ff` |  `#1a0e2e` |
| Dim text |  `#b6b1cc` |  `#3d2952` |
| Subtle (comments) |  `#848bbd` |  `#6b5b85` |
| Invisible |  `#4b4761` |  `#c8bcd9` |
---
## Comparison
| | cybersynth.nvim | Theme with 80 integrations |
|---|---|---|
| Works on plugins released *after* the theme | ✅ via hub-group inheritance | ❌ requires PR |
| New-plugin support PRs needed | Rare (only for polish) | Constant |
| Config table size | ~10 lines | ~80 toggles |
| User override always wins | ✅ via `overrides` | ⚠️ depends on integration |
| Light + dark mode parity | ✅ identical group surface | ⚠️ often partial |
---
## FAQ
**Neovim version?** >= 0.10 required.
**Truecolor terminal?** Yes. Set `set termguicolors` (the theme does this automatically).
**tmux italics/undercurls?** Add to your tmux.conf:
```tmux
set -g default-terminal "tmux-256color"
set -g terminal-overrides ',xterm-256color:smcur,rmcur'
```
**Plugin still looks wrong?** The plugin may be hardcoding colors instead of linking to hub groups. File an issue with that plugin's repo.
---
## License
MIT
---
If cybersynth made your editor a little more electric, drop a ⭐. If a plugin still looks off, that's a bug we want to know about — open an issue.
