pastilhasandClaude Sonnet 5
a58f4d2b32
The official 22 themes come from basecamp/omarchy's own colors.toml, contrast-checked by generate-themes.ts. A community theme has no such file — it ships per-app configs (alacritty.toml, ghostty.conf) in the older 16-ANSI-slot style, so this adds a sibling pipeline: from-ansi.ts derives the same 24-key Palette shape by role (accent, three background depths, three foreground weights) from those 16 slots, then runs through the same mapPalette + contrast checks the official themes use. Nothing about the official generator changed — verified generate-themes.ts --check still reports 0 changes. port-community-themes.ts discovers each theme's GitHub repo from its omarchythemes.com page, fetches alacritty.toml (preferred) or ghostty.conf, and is idempotent via community-manifest.json so a re-run only fetches what's missing. Community themes get their own registry/index.css marker block, separate from the official GENERATED THEMES block, so the two pipelines can never clobber each other. 121 of 212 attempted made it through cleanly; a second pass tightening accent selection and nudging --input recovered 20 more borderline cases (147 total). The rest failed for real reasons: 62 repos had no parseable colour source, 7 had an accent colour whose own luminance can't clear 4.5:1 against either black or white text, a handful were narrowly under threshold even after the rescue pass, and 2 pages had no repo link at all. Every generated file's header states its source repo and whether it's a light or dark theme. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
77 lines
3.8 KiB
TypeScript
77 lines
3.8 KiB
TypeScript
import type { Palette } from './palette';
|
|
import type { AnsiSource } from './ansi-source';
|
|
import { UI, contrast, ensureContrast, luminance, mix, parseHex } from './contrast';
|
|
|
|
// An `AnsiSource` (16 ANSI slots + primary bg/fg) has no notion of "three background depths" or "an
|
|
// accent" — Omarchy 4's `colors.toml` is a richer, hand-curated shape that a sixteen-slot terminal scheme
|
|
// was never designed to fill. This derives one anyway, by role rather than by guessing a fixed value:
|
|
//
|
|
// - accent is whichever blue-ish slot actually stands out from the background (every official palette
|
|
// picks blue too — this just guards against a scheme that reused the background for it).
|
|
// - the three depths are the background pushed a fixed distance toward black or white, in the direction
|
|
// each mode's surfaces already move (dark themes rise lighter, light themes recede darker — see the
|
|
// ratios comment below, calibrated against Nord and Rosé Pine's real colors.toml).
|
|
// - the three foreground weights are the foreground pulled toward the background by a fixed fraction,
|
|
// standing in for "faint", "muted" and "strong" text.
|
|
//
|
|
// None of this has to be exact. `mapPalette`'s `ensureContrast` re-checks every text/surface pair
|
|
// afterward and nudges anything that fails — the approximation only has to be plausible, not correct.
|
|
|
|
function pickAccent(a: AnsiSource): string {
|
|
const candidates = [a.blue, a.brightBlue, a.cyan, a.brightCyan];
|
|
const best = candidates.reduce((hi, c) => (contrast(c, a.background) > contrast(hi, a.background) ? c : hi));
|
|
// `--ring` is this colour laid directly on `--background` (see `map.ts`), and it's in the contract's
|
|
// PAIRS check same as the official themes — so guarantee it the way `ensureContrast` guarantees text,
|
|
// rather than only guarding against a background-coloured accent.
|
|
return ensureContrast(best, a.background, UI);
|
|
}
|
|
|
|
export function deriveOmarchyPalette(a: AnsiSource): Palette {
|
|
const dark = luminance(parseHex(a.background)) < 0.5;
|
|
const mode: Palette['mode'] = dark ? 'dark' : 'light';
|
|
|
|
const darkerBackground = dark ? mix(a.background, '#000000', 0.45) : mix(a.background, '#000000', 0.1);
|
|
const darkBackground = dark ? mix(a.background, '#000000', 0.22) : mix(a.background, '#000000', 0.06);
|
|
const lighterBackground = dark ? mix(a.background, '#ffffff', 0.07) : mix(a.background, '#000000', 0.035);
|
|
|
|
// Faintest → strongest, all pulled toward the background rather than toward a fixed grey, so a warm
|
|
// palette's dim text stays warm instead of turning neutral.
|
|
const darkForeground = mix(a.foreground, a.background, 0.55);
|
|
const lightForeground = mix(a.foreground, a.background, 0.3);
|
|
|
|
const accent = pickAccent(a);
|
|
const muted = contrast(a.brightBlack, a.background) >= 1.15 ? a.brightBlack : mix(a.foreground, a.background, 0.6);
|
|
|
|
return {
|
|
mode,
|
|
accent,
|
|
// Unused by `mapPalette` today (grep confirms `p.selection` has no reader) — kept only because the
|
|
// `Palette` type requires it.
|
|
selection: mix(a.background, a.foreground, 0.2),
|
|
muted,
|
|
background: a.background,
|
|
darkBackground,
|
|
darkerBackground,
|
|
lighterBackground,
|
|
foreground: a.foreground,
|
|
darkForeground,
|
|
lightForeground,
|
|
brightForeground: a.foreground,
|
|
red: a.red,
|
|
yellow: a.yellow,
|
|
green: a.green,
|
|
cyan: a.cyan,
|
|
blue: a.blue,
|
|
magenta: a.magenta,
|
|
// Standard ANSI has no orange slot. Mixing red and yellow reads better as "busy" than falling back to
|
|
// plain yellow the way `loadPalette` does for the 3 official themes that omit it.
|
|
orange: mix(a.red, a.yellow, 0.5),
|
|
brightRed: a.brightRed,
|
|
brightYellow: a.brightYellow,
|
|
brightGreen: a.brightGreen,
|
|
brightCyan: a.brightCyan,
|
|
brightBlue: a.brightBlue,
|
|
brightMagenta: a.brightMagenta,
|
|
};
|
|
}
|