All themes

Claude

A theme reconstructed from the Claude desktop app: neutral charcoal surfaces, a clay accent, 8px controls, and menus that stay out of the way. It follows the site's light or dark setting.

Claude's interface is quiet on purpose. Almost everything is one of four neutral greys, elevation is a hairline plus a single soft shadow, and the only saturated colour is the clay mark. This page rebuilds the app shell from screenshots and exposes the result as a scoped theme, .claude-theme, that any BoringUI surface can opt into.

The demo is live. Pick a session, press the sliders control beside the first project for the grouping menu, hover a session for its ⋯ menu, type in the composer and send with ⌘↵. It follows the site's theme setting — press T to cycle light, dark, and system. The AskUserQuestion, Task list, and Table sections below rebuild the surfaces Claude Code uses while it works.

App shell

SessionRework the checkout summary card
This still doesn't feel anything like the reference app. I sent over screenshots of the whole flow — study the layout and the interactions carefully, then rebuild the workspace around them.
2 days ago

Got it. The last version misread the information architecture: I treated it as a project board, but the screenshots show a conversation-first team workspace — navigation on the left, the thread in the middle, and a panel on the right that belongs to the current session. Opening a task swaps the center column for a run view. I'll rebuild it from the screenshots.

Let me look at the actual structure first:

Listed project files
store.js+96−21
messages.js+38
router.js
tasks.js+33−5
session.js+214
session.js+1−1
runs.js+181−92
shortcuts.js+248−121
api.js+342−98
api.js+2−2
index.html+164−102
styles.css+631−254
app.js+1208−341
Compacted session: saved 433.6k tokens
styles.css
api.js
runs.js

I'll list the project files to confirm where the page script, routes, and styles live, then split navigation, the session thread, and the task panel into three separate surfaces and align spacing, borders, and hover states layer by layer.

Sonnet 5.5 · High
·
Bypass permissions·Sonnet 5.5 · High

Sidebar 248px · context rail 300px · 620px reading column · 16px composer radius. Session rows are 28px high and every control sits on a 6 or 8px radius.

Palette

Four neutral greys carry the whole app. The dark ladder is additive: the sidebar is darker than the canvas, raised fields sit one step above it, and menus take the highest step. Nothing is pure white or pure black.

Canvas
--cl-bg
#FCFBFC / #151515
Sidebar
--cl-sidebar
#FAFBF8 / #111111
Panel
--cl-panel
#FCFBFC / #181818
Surface
--cl-surface
#FFFFFF / #1D1D1D
Menu
--cl-menu
#FFFFFF / #202020
Hover
--cl-hover
4% / 6% neutral
Border
--cl-border
10% / 10%
Ink
--cl-ink
#1F1F1F / #F2F2F2
Clay
--cl-accent
#D97757

Type

One system sans carries the interface at 13px, with a serif reserved for the greeting on an empty session. Mono appears only inside file names, diffs, and shortcuts.

30px / 1.0 · serif — empty-session greeting
You're here!
15px / 1.4 · sans — composer placeholder
Type / for commands
13px / 1.7 · sans — message body
The interface is the conversation. Everything else — navigation, context, tools — stays one step quieter than the text you are reading.
11.5px · mono — file and shortcut metadata
scripts/build-page.mjs · ⌘K

Controls

Buttons are 30px tall with a hairline border and no gradient. Only one control per surface earns the ink fill; clay is reserved for the mark, focus, and the single affirmative action. Inputs keep the border and add a 3px clay halo on focus.

LocalClaude

AskUserQuestion

When Claude needs a decision, the thread pauses on a question card. The question owns a tinted header, every option carries its own explanation, and the chosen row gets a single blue dot. Skip and Submit live inside the card; the amber status chip below belongs to the thread, not the card.

How should the right-side detail open from the table area?

Needs your input

A 480px card with one question header, one explanation per option, 18px radios and 28px actions. Click an option, then Submit (⌘↵) or Skip. The status chip reports the answer and returns to “Needs your input” as soon as another option is picked.

Task list

While Claude works, its checklist lives in a tool card. Finished steps collapse to a filled check and one step of muted ink, the step in flight is a solid ring, and everything still queued waits behind a dashed ring.

  1. Completed: Inventory the Harbor codebase
  2. Completed: Map the design tokens and type scale
  3. Completed: Trace the sync queue and retry path
  4. Completed: Walk the capture-to-archive flow
  5. Completed: Review the help center's tone
  6. In progress: Scaffold the Shared Spaces workspace
  7. Pending: Build the document model and local cache
  8. Pending: Build list, board, and calendar views
  9. Pending: Add search, filters, and saved views
  10. Pending: Wire import, export, and share links
  11. Pending: Write the migration notes and docs
  12. Pending: Test, build, and verify in browser
8m 42s · 126.7k tokens

A 620px card with twelve 28px rows and 14px markers, no dividers. State is carried by the marker and the title colour; the footer pairs clay activity dots with elapsed time and token spend.

Table

Tool output that needs structure lands in a quiet table: a raised header row, 1px grid gaps in the page colour, and top-aligned cells. Inline code keeps the mono face and takes one step toward the blue so identifiers read apart from the prose.

Working hypotheses from the Harbor sync audit, with their sources and whether they were observed or inferred.
#HypothesisSourceKind
H1First sync after sign-in takes p95 12.4 s on a 2,000-note library, against a 2 s target on a 20 Mbps link.TICKET-118 (High, Open, 05-12)Observed
H2The sync queue collapses every edit into one mutation, so conflictRetries never exceeds 1 and lost writes go unreported.TICKET-121 (High, Open, 05-14)Observed
H3The editor's autosave debounce resets on every keystroke; a minute of continuous typing produces no snapshot and a blank recovery draft after a crash.TICKET-126 (Medium, Open, 05-15)Observed
H40.8.3 SyncEngine treats offline as syncing while retryBackoff is pending, so the status pill keeps spinning and manual retry stays disabled.09-02 P1Inferred
H5parseCursor drops the last page when nextCursor is empty, so the final 12 local edits are marked acked without ever leaving the device.09-02 P1Inferred
H6resolveConflict trusts updatedAt from the client clock, so a machine three minutes behind silently overwrites the newer remote note.09-02 P1Inferred

Header cells sit one step above the body; the grid is drawn by 1px gaps, not borders. Columns are 9% / auto / 18% / 14%, and code fragments stay mono at 92% size.

Rules

  • Four greys, no gradients. Canvas, sidebar, panel, and menu. A card is a hairline border plus one low-opacity shadow, never a brighter fill stacked on a brighter fill.
  • Radii climb with the surface. 6px for rows and icon buttons, 8px for controls, 10px for cards, 12px for menus, 16px for the composer.
  • Warm ink, never #FFF. Primary text is #F2F0E9 on dark and #32312C on light. Muted text is one step above the border, not a grey of its own.
  • Clay is a signal. The accent appears on the mark, the focus halo, the selected count, and one action. Nothing else.
  • Menus are the only elevated layer. They keep the 1px ring, gain the 12px radius, and use a 30px row with a 6px inset highlight. Shortcuts sit on the right in mono.
  • Answers are the one blue exception. The AskUserQuestion card keeps Claude Code's blue selection dot; everywhere else the mark, focus, and affirmative action stay clay.
  • Tables are a grid of cells, not lines. A 1px gap in the page colour draws the grid; the header row is one step above the body, and the body never stripes. Code fragments stay mono and never wrap.