A theme, in most applications, changes a few colors and calls it a day. In Quilltap, a theme can redefine the entire personality of the application.

Quilltap’s theming system is built on a layer of semantic CSS variables—the qt-* utility classes—that map to every UI surface: cards, panels, buttons, chat bubbles, sidebars, message styling, typography, form inputs, status badges, and alert states. A theme overrides these tokens and can embed its own fonts, CSS, background images, and visual personality. Switching themes happens live, instantly, with no page reload. The entire application redraws itself around you like a room being redecorated while you sit in the chair.

Themes can also override subsystem names and navigation card descriptions. The room called “The Foundry” in one theme becomes “Settings” in another and “The Machinist’s Floor” in a third. The characters who personify each subsystem adjust their presence to match the current theme’s register. The Estate speaks in its own voice, whatever voice you choose.

Quilltap ships with six themes, each with full light and dark mode support. The theme selector shows each theme’s name in its own heading font, with rich interactive previews that expand to show actual UI elements in both modes side by side.

Calliope does not guard the studio door. Theme creation is supported through two paths, both designed so that you never need access to Quilltap’s source code.

A registry system with Ed25519 signature verification lets you browse, search, and install themes from remote sources. The Theme Browser in Appearance settings provides the full experience without touching a command line—compatibility indicators, verified and unverified badges, and one-click installation.

The signature does not prove a theme is safe in the security sense—themes cannot execute code, only define JSON tokens and static assets—but it does prove that someone at the Estate vouched for it. Registry sources can be added and removed. The distinction between curated distributions and community contributions is always visible.

Themes are Calliope’s most visible work, but the Studio governs the entire user experience. Every layout decision, every interaction pattern, every piece of visual feedback passes through the same aesthetic judgment.

Underneath every theme is the qt-* utility class system—a comprehensive layer of CSS variables that maps to every visual surface in the application. This is what makes Quilltap’s theming possible without the theme author needing to know the component structure, and what makes theme switching instant without a page reload.

The system covers backgrounds (qt-bg-surface, qt-bg-card, qt-bg-muted), borders (qt-border, qt-border-primary), text (qt-text-secondary, qt-text-warning), buttons, alerts, entity badges, status badges, plugin source badges, form inputs, filter chips, file previews, chat messages, sidebar elements, and more. Over the course of the 2.x and 3.x release cycles, hundreds of component files were migrated from raw Tailwind color classes to these semantic tokens, so that a single theme override changes the application consistently rather than leaving orphaned hard-coded colors behind.

The @quilltap/theme-storybook package reached comprehensive coverage of all qt-* classes during the 3.3 cycle. If you are building a theme, every variable you might want to override is documented, previewable, and testable before you ship.