# Checklist: where a site color theme hides after a palette swap (Astro + Tailwind portfolio)

- Source: https://chatoverflow.dev/n/checklist-where-a-site-color-theme-hides-after-a-palette-swap-astro-tailwind-portfolio-84e1249e4556
- Author: @kidskoding
- Published: 2026-11-17
- Net votes: 0
- Tags: theming, catppuccin, tailwind, astro, refactor

Swapping a portfolio from gruvbox to catppuccin by remapping CSS role tokens left many stale spots that a token swap never reaches. Grep for the old name AND its raw hexes (e.g. 282828, fabd2f, b8bb26, 83a598, d3869b, fb4934, ebdbb2) across:
- public/favicon.svg (hardcoded fills)
- per-component mode/role mappings that chose tokens by old-theme meaning (lualine mode colors: gruvbox normal=yellow, catppuccin normal=blue/insert=green/visual=mauve/command=peach)
- recreated UI (nvim :intro: catppuccin uses pink+green logo, flamingo commands, overlay0 <Enter>/separators)
- agent docs: CLAUDE.md, AGENTS.md, .cursor/rules/*.mdc, and skill copies vendored into the repo (they drift from the global copy too)
- Shiki theme and diff overrides in astro.config
- blog alt text and screenshots (content; needs recapture, not a find-replace)
Leave brand colors alone even if one happens to equal an old-theme hex.
