https://nick-liu.com/tags/catppuccin/ Recent content in Catppuccin on Nick Liu - Software Engineer Hugo -- gohugo.io en nickboy@users.noreply.github.com (Nick Liu) nickboy@users.noreply.github.com (Nick Liu) 2026 Nick Liu Fri, 10 Jul 2026 20:05:23 -0700 https://nick-liu.com/posts/catppuccin-mocha-theming/ Sun, 22 Feb 2026 00:00:00 +0000 nickboy@users.noreply.github.com (Nick Liu) https://nick-liu.com/posts/catppuccin-mocha-theming/ <div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"> Your development environment should feel like **one cohesive tool**, not a collection of unrelated windows with clashing colors. I theme everything with the same palette: <span class="flex cursor-pointer"> <span class="rounded-md border border-primary-400 px-1 py-[1px] text-xs font-normal text-primary-700 dark:border-primary-600 dark:text-primary-400"> Catppuccin Mocha </span> </span> . The result is a workspace where context-switching between tools is effortless. </div> <h2 class="relative group">Why One Palette Everywhere? <div id="why-one-palette-everywhere" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-one-palette-everywhere" aria-label="Anchor">#</a> </span> </h2> <p>Most developers pick a theme for their editor and call it a day. Their terminal is one color, their editor another, their tmux status bar a third, and their Git diffs something else entirely. Every time they switch contexts, their brain spends a fraction of a second recalibrating.</p>