Santi020k Themes
Santi020k Themes

One violet. Every surface.

Your workspace.
In one palette.

For the way you work

A familiar palette. In every buffer.

Quiet surfaces and clear syntax for your terminal editor. Follow a thought through code, diagnostics, and diffs without losing the thread.

Native colorschemeNeovim 0.10+Dark + light
luainit.lua
local workspace = {
  theme = "santi020k",
  appearance = "dark",
}

-- A little less noise.
vim.cmd.colorscheme(workspace.theme)
Code color preview · Neovim uses your own terminal and font

One file to get started

Keep your configuration. Add the palette.

  1. Find your configuration directory

    In Neovim, run :echo stdpath('config'). This locates the correct directory on macOS, Linux, and Windows.

  2. Copy the colorscheme

    Extract the ZIP. Copy colors/santi020k.lua into the colors directory inside your configuration directory, creating it if needed. Keep your other files.

  3. Activate it

    Add the configuration shown here after your plugin setup, then restart Neovim. Use :set background=light or :set background=dark to change appearance.

Choose your configuration format

lua
vim.opt.termguicolors = true
vim.opt.background = "dark" -- or "light"
vim.cmd.colorscheme("santi020k")

True-color terminal support is recommended. Appearance follows Neovim’s background setting.

Download the Lua file only

Beyond the main buffer

The details belong together.

Code and editor intelligence

Native syntax, Tree-sitter captures, LSP semantic tokens, diagnostic underlines, inlay hints, and references. Tree-sitter and LSP colors apply when those features are configured.

Everyday navigation

Selections, search, floating windows, completion menus, tabs, diffs, and 16 terminal colors. No runtime plugin dependency.

Update or restore

Replace the single Lua file to update. To remove it, choose another colorscheme, remove the Santi020k activation line, and delete the file.

The first version covers native Neovim groups. Third-party plugins may need their own integrations. Use the ZIP installation; this monorepo’s root is not a plugin-manager entry point.