Repository navigation
feat(registry): gibson-theme — dark-led theme item for the Gibson admin portal - #10
Merged
Merged
Conversation
…in portal New registry:style item "gibson-theme" serving gibson-hackers.com. Structurally a 1:1 swap for the corp `theme` globals.css (same var inventory, same [data-theme]/.dark selectors, same @font-face + @theme inline blocks); only the dark values differ — deep near-black indigo surfaces (hue 274), phosphor-lime primary, hairline borders, 0.375rem radius. Chart vars and the entire light block are copied verbatim from the corp theme so the in-app toggle stays on the proven corp light. Shares the corp theme's tokens.css (brand-core layer) rather than duplicating it. The corp `theme` item is untouched. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Mark declared the Gibson home-page prompt canonical (2026-06-12). The gibson-theme registry item is the brand carrier for internal apps, so the spec lives here too: dark-led lime-primary tokens, mono status chrome, real-data-only surfaces, reduced-motion parity. Implementation of record: crashappsec/digital-marketing PR #1767. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…anonical values - registry.json item description, globals.css header, README item list and the brand spec now all state explicitly: gibson-theme is for internal apps only (gibson-hackers.com), never for crashoverride.com or any public/customer-facing property — public sites use the theme item. - docs/gibson-home-spec.md gains the approved canonical value table (the Mission Control playground render of record, dark + light) and documents the known deltas vs the gibson-theme global surface tokens (background/card/muted-foreground), explicitly gated on Mark before any global alignment. New internal surfaces take values from the table. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…als as-is for now (Mark, 2026-06-12) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a new named theme registry item
gibson-theme(registry:style) for the Gibson admin portal (gibson-hackers.com). It is a 1:1 structural swap for the corpthemeglobals.css — same variable inventory, same:root/[data-theme]/.dark/.lightselectors, same@custom-variant,@font-face,@theme inline, andbodyblocks — with only the dark-mode values changed to the Gibson look. It reuses the sharedsrc/registry/crashoverride/theme/tokens.css(the brand-core layer, identical for both themes) rather than duplicating it.The corp
themeitem is completely untouched (git diff origin/main -- src/registry/crashoverride/theme/is empty; the CI tokens.css staleness gate passes).Value summary (dark block)
themegibson-theme--radius0.25rem0.375rem--backgroundoklch(0.20 0 0)oklch(0.145 0.02 274)— near-black indigo--cardoklch(0.30 0.02 274)oklch(0.185 0.022 274)--popoveroklch(0.33 0.02 274)oklch(0.22 0.022 274)--primaryoklch(0.93 0.25 124)oklch(0.93 0.25 124)— same phosphor lime--primary-foregroundoklch(0.20 0 0)oklch(0.13 0.02 274)--secondary/--muted/--accentoklch(0.27 0.035 274)oklch(0.24 0.03 274)--muted-foregroundoklch(0.68 0.02 274)oklch(0.66 0.018 274)--borderoklch(1 0 0 / 8%)oklch(1 0 0 / 9%)— hairline--sidebaroklch(0.20 0 0)oklch(0.125 0.018 274)--sidebar-accentoklch(0.27 0.035 274)oklch(0.22 0.025 274)--chart-1..5Verification
npm run registry:build— emitspublic/r/gibson-theme.jsonandpublic/r/v1/gibson-theme.json;tokens.csscontent in the built item is byte-identical to the corpthemeitem'sgit diff --exit-code src/registry/crashoverride/theme/tokens.css— staleness gate cleannpx vitest run— 205/205 pass (incl. newsrc/test/gibson-theme.test.ts+ aregistry-build.test.tscase for the new item)npm run lint+npm run build(tsc + vite) — cleanNotes
.storybook/preview.tsximports the corp theme'sglobals.cssglobally; both themes define the same:rootvariables, so importing the second file would silently override the first (last-import wins). A safe preview needs a scoped/toolbar mechanism — out of scope here.npx shadcn add @crashoverride/gibson-theme/registry-refresh.ymlwithitems: gibson-theme).pages.yml) before consumers canshadcn addthe new item —public/r/is gitignored and regenerated by CI.🤖 Generated with Claude Code