Overview Version History Q & A Rating & Review
JD's Abyss Theme
A dark theme for Visual Studio Code inspired by Gerry's Abyss theme from JetBrains IDEs. This theme features deep blues and purples with orange accents, creating a comfortable and visually appealing coding environment.
Install from: VS Code Marketplace | Open VSX Registry
Features
Dark color palette with primary background #0c1018
for reduced eye strain
Purple and blue accents for syntax highlighting
Orange highlights for important elements
Carefully crafted colors for optimal readability
Complete UI theming including editor, sidebar, and terminal
Installation
From VS Code Marketplace
Open VS Code
Go to Extensions (Ctrl+Shift+X)
Search for "JD's Abyss"
Click Install
Go to File > Preferences > Color Theme
Select "JD's Abyss"
Manual Installation
Download the latest .vsix
file from Releases
Open VS Code
Run Extensions: Install from VSIX...
from the Command Palette (Ctrl+Shift+P)
Select the downloaded .vsix
file
Go to File > Preferences > Color Theme
Select "JD's Abyss"
Development
Local Testing
# Clone the repository
git clone https://github.com/starburst997/jd-abyss.git
cd jd-abyss
# Install dependencies
npm install
# Package the extension
npm run package
# Install locally for testing
code --install-extension jd-abyss-2025.1.0.vsix
Publishing
# Login to Visual Studio Marketplace
vsce login <publisher-name>
# Publish new version
npm run publish
Color Palette
Background : #0c1018
- Deep dark blue
Foreground : #d0d0d9
- Light gray
Accent : #55a5ff
- Bright blue
Highlight : #9b5528
- Orange
Selection : #173d59
- Dark blue
Contributing
Fork the repository
Create your feature branch (git checkout -b feature/amazing-feature
)
Commit your changes (git commit -m 'Add some amazing feature'
)
Push to the branch (git push origin feature/amazing-feature
)
Open a Pull Request
Credits
Inspired by Gerry's Abyss theme from JetBrains IDEs.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Support
If you encounter any issues or have suggestions, please open an issue on GitHub.