Peachy Playground

Preview the palette against real language samples.

Use this page when you tweak Peachy tokens or syntax colors. It keeps the theme honest across different code styles instead of only one screenshot.

Home Docs Palette GitHub Review Checklist

Contrast

Check body text, comments, and sidebar-like surfaces first. A cute palette only works if it stays readable for long sessions.

Syntax balance

Make sure keywords, strings, functions, and types are distinct without turning every file into confetti.

UI parity

Compare editor colors with terminal, prompt, and docs surfaces so the collection still feels like one family.

Release readiness

Run npm run check, refresh generated assets, and review a few screenshots before tagging.

TypeScript

export async function sweetenTheme(
  themeName: string
) {
  const tokens = {
    background: "#202330",
    accent: "#ff928b"
  }

  return buildTheme(themeName, tokens)
}

JSON

{
  "name": "peachy-themes",
  "semanticHighlighting": true,
  "version": "0.1.0"
}

Markdown

## Peachy Notes

> Keep the theme soft, warm, and readable.

Use npm run check after changing colors.

Python

def peachy_report(items: list[str]) -> None:
    for item in items:
        print(f"theme: {item}")

HTML + CSS

<section class="peachy-card">
  <h2>Theme ports</h2>
</section>

.peachy-card {
  background: #202330;
  border: 1px solid #fec3d6;
}

Shell + Release

npm run check
git tag v0.1.0
git push origin main --tags

Ports to compare before release

VS Code package Publish flow LazyVim package Oh My Posh package

Palette