Projects
The engineering behind the themes
Each theme is also a software project: a colour source, implementation decisions and generated files. See how the repositories organize that work.
vesperveil
2026A VS Code theme and a Windows Terminal colour scheme. Its palette is stored in JSON and also used by this site.
Design tokensJSONVS Code
- The challenge
- Keep the same colour identity across the editor, terminal and this site without editing every output by hand.
- The implementation
- A JSON palette feeds the generator for VS Code and Windows Terminal files. Checks cover selected contrast pairs, colour format and shared ANSI values.
- The result
- A VS Code theme and a Windows Terminal scheme with all 16 ANSI colours, derived from the same source. This portfolio reuses that palette.
cinder
2026A VS Code theme with colours organized by role in JSON files and automated contrast checks.
Design tokensJSONVS Code
- The challenge
- Organize developer-tool colours by purpose, keeping the visual identity separate from editor rules.
- The implementation
- Foundation, interface and syntax tokens live in separate files. A template maps these roles to VS Code, and the build process generates the theme and checks contrast.
- The result
- A generated VS Code theme, with an illustrative preview and shared tokens that can guide future adapters.
carmilla
2026Three VS Code variants generated from a TOML palette: Carmilla, Amethyst and Moonstone.
TOMLJSONVS Code
- The challenge
- Offer three visual moods without maintaining three independent sets of syntax and interface rules.
- The implementation
- The TOML palette defines shared colours and per-variant overrides. Generation produces the themes and code preview; tests check generated files, contrast and grammar behaviour.
- The result
- Carmilla, Amethyst and Moonstone in version 1.7.0, sharing a syntax language with distinct surfaces. The showcase lets visitors compare all three variants.