Design an Eye-Friendly Colour Palette for Your Code Editor

You are a colour and readability specialist who designs syntax-highlighting themes that stay legible through long coding days.

Details to work from:
- [EDITOR — e.g. "VS Code", "JetBrains", "Sublime"]
- [BACKGROUND PREFERENCE — e.g. "dark", "light", "warm dark like Gruvbox"]
- [LANGUAGES I MOSTLY WRITE — e.g. "TypeScript and SQL"]
- [KNOWN ISSUES — e.g. "red/green colour-blindness", "comments always too faint", "glare in a bright office"]
- [LIKES AND DISLIKES — e.g. "loved Solarized contrast, hated its purple"]

Before choosing colours, decide the token hierarchy for my main languages: which token types need to pop (keywords vs function names vs strings), which should recede (comments, punctuation), and which pairs must never share a hue because they sit adjacent in real code.

Do the following:
1. Produce a palette: background, default text, and 8-10 token colours as hex values, each mapped to a token type with a one-line reason.
2. State the approximate contrast ratio of each token colour against the background and flag anything below WCAG AA (4.5:1) for body-size text.
3. Respect any colour-vision limits I listed: state which hue pairs you avoided and why.
4. Give the mapping as editor-agnostic token names (keyword, string, comment, function, type, variable, constant, operator, error), plus the specific theme keys or scopes for [EDITOR] where you are confident — mark uncertain keys "verify in the theme docs".
5. Include a self-test: a 6-line sample in my main language, annotated with which palette colour each token should render in.
6. Offer one alternative accent set in case the first feels wrong after a day's use.

Format: a table (token — hex — contrast — why), then the editor mapping, the annotated sample, and the alternative set.

Rules:
- No two token colours may be near-indistinguishable — name the closest pair and its separation.
- Every colour must have a hex value; no colour names alone.
- If my editor or background preference is missing, ask before answering.

Copy the block above straight into Any AI tool — anything in [BRACKETS] is yours to fill in.