Add color palette

[skewb1k]

Goal

Introduce a standardized color palette for the Vague theme.
This simplifies theme porting, enables easier creation of variants, and helps ensure consistency.

• Define and document color naming conventions.
• Add palette.json as a single source of truth for tooling and automation.
• Generate SVG color assets.
• Add a Markdown table documenting the palette in README.md. Preview

[skewb1k]

On color naming

Since the theme originated as a Neovim plugin, the current reference for all other ports is the Lua table in https://github.com/vague-theme/vague.nvim/blob/dba28050887c2810b5ebf9e0143b4e919bd55757/lua/vague/config/internal.lua#L102.

That table names colors based on their semantic usage in Neovim (e.g. warning, visual, keyword). This works well within the Neovim context, but it may not be ideal for a standalone palette, as those names become less meaningful outside of text editing or Neovim-specific use cases.

I think a better long-term convention is to name colors primarily by their appearance rather than their usage. The main challenge is dealing with very similar shades and the limited set of intuitive color names. For example, we currently have three yellows. I don't think introducing numbers or "bright-" / "dark-" prefixes is a great solution, but coming up with more descriptive names (e.g. "gold", or something) might be possible.

This likely needs more thought, but for now this is the best approach I've come up with.

{
  "background": "#141415",
  "text": "#cdcdcd",
  "surface": "#1c1c24",
  "overlay": "#252530",
  "highlight": "#333738",
  "muted": "#606079",
  "gray": "#878787",
  "yellow": "#f3be7c",
  "yellow1": "#e8b589",
  "yellow2": "#e0a363",
  "peach": "#c48282",
  "red": "#d8647e",
  "cerulean": "#405065",
  "lavender": "#c3c3d5",
  "cyan": "#aeaed1",
  "pink": "#bb9dbd",
  "aqua": "#b4d4cf",
  "aqua1": "#90a0b5",
  "aqua2": "#9bb4bc",
  "teal": "#6e94b2",
  "blue": "#7e98e8",
  "green": "#7fa563"
}

@vague2k I'd really appreciate your thoughts on this, especially if you have ideas or preferences around naming convention.

[skewb1k]

I think I managed to pick somewhat unique and reasonable names.

@vague2k, open to any objections.