santi020k Theme

A pair of VS Code color themes built around a deep indigo-black palette with muted violet accents — inspired by the Antigravity wallpaper. Available in dark and light variants, both sharing the same purple-forward color language.

→ theme.santi020k.com

Preview

Variants

santi020k dark

Deep indigo-black (#120c1e) backgrounds with a layered surface hierarchy. Accent colors are muted violets pulled directly from the wallpaper geometry — nothing neon, nothing loud. Keywords and storage modifiers are italic; comments recede into near-invisible purple. The cursor and active tab indicator glow in #c090ff.

santi020k light

Purple-tinted whites (#f8f6fd) with a rich violet brand (#6319be) driving all interactive elements. The status bar flips to solid brand purple, making workspace context immediately readable. Syntax uses a single-hue violet ramp so the light variant feels like a natural counterpart to the dark one.

Installation

From the VS Code Marketplace

1. Open VS Code (or any compatible fork)
2. Go to Extensions (Cmd+Shift+X)
3. Search for santi020k Theme
4. Click Install
5. Open Preferences: Color Theme (Cmd+K Cmd+T) and select santi020k dark or santi020k light

From Open VSX

Install from Open VSX in editors that use the Open VSX registry, then select santi020k dark or santi020k light from the color theme picker.

Manual install (.vsix)

1. Download the latest .vsix from the Releases page
2. Open VS Code → Cmd+Shift+P → Extensions: Install from VSIX…
3. Select the downloaded file

Development

Requirements

• Node.js 20+
• VS Code or a compatible fork (Antigravity, Cursor, etc.)

Setup

git clone https://github.com/santi020k/santi020k-theme
cd santi020k-theme
npm install

Running the extension locally

Press F5 (or run Debug: Start Debugging from the Command Palette) to open an Extension Development Host window with the theme loaded. Any changes you make to the theme JSON files are picked up after reloading that window (Cmd+R).

Alternatively, open the project in VS Code and use the Run & Debug panel — the Extension Development Host launch config is already included.

Editing the themes

All colors live in two files:

The JSON structure follows the standard VS Code Color Theme format:

• colors — workbench UI (editor, sidebar, tabs, status bar, terminal…)
• tokenColors — TextMate grammar tokens (syntax highlighting)

Useful references

• VS Code Theme Color Reference
• VS Code TextMate Token Reference
• Scope Inspector — open with Cmd+Shift+P → Developer: Inspect Editor Tokens and Scopes to identify the exact scope of any token

Testing

Visual inspection checklist

Open files in common languages and verify:

• [ ] Comments are readable but clearly de-emphasized
• [ ] Strings, keywords, types, and functions are visually distinct
• [ ] Active tab and cursor are clearly highlighted
• [ ] Sidebar and activity bar contrast is sufficient
• [ ] Terminal ANSI colors look correct (echo -e a color test)
• [ ] Git decorations (added / modified / deleted) are visible in the Explorer
• [ ] Error and warning squiggles are clearly visible

Contrast check

Use the VS Code Accessibility: Color Contrast Ratio Checker or paste hex values into Colour Contrast Analyser to verify WCAG AA (4.5:1) for primary text against editor background.

Packaging for local testing

npm run package
# → generates santi020k-theme-x.y.z.vsix

# Install in VS Code
code --install-extension santi020k-theme-x.y.z.vsix

Publishing to Production

One-time setup

1. Create a Microsoft account if you don't have one
2. Go to marketplace.visualstudio.com/manage and create a publisher with ID santi020k
3. In Azure DevOps → User Settings → Personal Access Tokens, generate a token with Marketplace → Manage scope
4. Add the token as a secret named VSCE_PAT in your GitHub repository settings
5. Create an Open VSX access token and add it as a GitHub Actions secret named OVSX_PAT
6. Make sure the santi020k namespace exists in Open VSX before the first publish

Changeset releases

npm run changeset

Merge feature branches with changesets into main. GitHub Actions will create a release PR that bumps the package version and changelog. Merge that release PR to publish the new version to the VS Code Marketplace and Open VSX.

The publish workflow uses the VSCE_PAT and OVSX_PAT repository secrets.

Release checklist

• [ ] Changeset added for user-visible changes
• [ ] icon.png present (128×128 PNG, required by the Marketplace)
• [ ] Tested locally with npm run validate
• [ ] Release PR merged after feature branches land on main

License

Released under the MIT License.