Cutroom owner's guide
Everything from the download to your own palette, read from the files this theme ships.
- 1.10.7
- version
- 10
- pages
- 36
- components
- 89 × 2 modes
- tokens
- 4
- workflows
unzip cutroom-1.10.7.zip
cd cutroom-1.10.7
bun install
bun devThe download is a complete Next.js project, not a folder of snippets. It carries 10 routes, the token file, 36 components and the agent kit.
See the priceInstall
Three ways in: the zip, the shadcn registry, or your agent over MCP.
The artifact is versioned and immutable, so the file you get is cutroom-1.10.7.zip. Unzip it, run the four commands above, and the site is on localhost:3000.
The link arrives with your license, and stays valid for every future version.
Every theme is a registry item the real shadcn CLI installs. Files land under src/tailthemes/cutroom/, mirroring the tree below.
Cutroom is paid, so the request has to carry your license key. Put it in TAILTHEMES_LICENSE_KEY in your .env.local, then add this to components.json. The CLI expands the variable and sends the key as a header, so it never enters a URL.
{
"registries": {
"@tailthemes": {
"url": "https://tailthemes.com/r/{name}.json",
"headers": {
"Authorization": "Bearer ${TAILTHEMES_LICENSE_KEY}"
}
}
}
}bunx shadcn add @tailthemes/cutroomAn all-access key works on every slug. A single-theme key works on the theme it was bought for.
A registry item is JSON, so image assets cannot travel with it. Themes that import images need the zip as well.
Point any MCP client at https://tailthemes.com/api/mcp and your agent can read the manifest, both token tables and AGENTS.md before it touches a file.
the four toolsWhat unzips
One directory, laid out the way you would lay it out yourself.
every file
Three of these do the work: src/theme.css holds every design decision, AGENTS.md is the contract your agent reads first, and .claude/skills/ holds the 4 workflows it can run.
Screenshots are not in the download. They are generated by the publish pipeline and live on the listing, not in your project.
Using it
Every page is a plain component, and the tokens are scoped to one class.
- /Overview3 sections
- /libraryMedia library2 sections
- /uploadsUploads2 sections
- /playerShared player2 sections
- /editorSequence builder2 sections
- /distributionDistribution2 sections
- /analyticsWatch analytics2 sections
- /peoplePeople and plan2 sections
- /titleAfterlight1 sections
- /componentsComponents24 sections
Tokens are declared on .tt-cutroom as well as :root, so an install cannot repaint components you already have. Wrap the page in <div className="tt-cutroom"> and everything inside picks them up.
Dark mode is a dark class on <html>. There is no second stylesheet and no dark: utility in the components.
The HTML edition
The same site again, with no framework under it.
Everything under html/ is a second, independently authored edition of the theme. html/dist/ is 10 compiled routes with local fonts and vanilla JavaScript — copy it to any static host and it is live, with no build step and no Node on the server. html/src/ is the Nunjucks source those routes compile from.
bun run build:html recompiles html/dist/ after you change the source or the tokens. bun run preview:html serves the compiled edition locally. Both ship in the download's package.json, backed by the two files in scripts/.
One token file drives both editions, so a rebrand made in src/theme.css reaches the HTML edition the next time you run the build — dist/ carries compiled CSS and never updates by itself.
The two editions are kept in step by the publish gate: every route in the manifest must have a compiled counterpart before a version ships, so the 10 pages you saw above exist in both.
Making it yours
Tokens are the API: change the values, never the names.
- Edit the values. All 89 tokens live in src/theme.css, in a light block and a dark one. Nothing in src/components/ carries a colour.
- Watch it land. Open /components. The styleguide reads every swatch, type step and radius live, so you see what the change did to the whole system at once.
- Re-check contrast. Run the check-quality workflow. The palette ships verified to WCAG AA in both modes and a rebrand should keep it there.
- .claude/skills/add-page
1. Create src/app/<slug>.tsx and compose existing sections inside AppShell unless the route is explicitly public.
- .claude/skills/add-section
1. Create one src/components/<name>.tsx.
- .claude/skills/check-quality
Run from the repository root and stop on failure:
- .claude/skills/rebrand
1. Edit values in src/theme.css and mirror light values into theme.json.tokens and dark values into tokensDark.
Those summaries are the files' own opening lines. They are written against this repo, so where one names themes/cutroom/ your copy has the project root instead.
For your agent
The theme brought its own rules, so nothing has to be reverse-engineered.
AGENTS.md is 541 lines of invariants, the file map, the type and spacing scale, and what never to touch. It opens like this.
# Cutroom theme guide
Cutroom is a media operations frontend for **Northline Pictures**, a small studio producing the fictional *Afterlight* anthology. It is a frontend template with realistic fixtures. It does not include storage, transcoding, streaming, auth, billing, analytics ingestion, or persistence.
The premium workflow pass makes five operational screens one traceable lifecycle. `mediaHref` and `getMediaItem` preserve asset identity from library and title entry into review; the player uses one clock for transport, waveform, and timecodes; ingest rejects unsupported or oversized local files without silent truncation; distribution separates rendition readiness from the central release gate; and studio access validates invitations and confirms removal. These remain browser-only fixtures.
## Identity
- **Positioning:** one review-to-release workspace for independent media teams.
- **Signature:** the continuous filmstrip recurs in the library, review timeline, and sequence builder.
- **Deviation:** `/title` drops the application rail and lets the player bleed to the viewport edge, creating a credible public title page inside the console system.
- **Register:** technical-plain in application screens; editorial on the title page.
- **Motion:** editorial-cut. Feedback is 140ms, state change is 240ms, **a close is 150ms**, and the playhead is the sole ambient animation *on a settled screen*. Reduced motion stops it. Opening carries the distance, the pre-scale (modal .96, menu .97, tooltip .98) and — only on surfaces narrower than a menu — a 2px blur; leaving drops all three and never bounces. Loading placeholders and a busy button may pulse or spin on opacity while data is pending; nothing else loops.
- **Display:** Red Hat Mono turns titles and timecode into one editorial-machine register.
- **Text:** Schibsted Grotesk keeps dense controls and comments easy to scan.
- **Mono:** Red Hat Mono carries timecode, IDs, durations, and stacked figures.
- **Type ratio:** 1.125, the dashboard/operations ladder.
## Color rules
- Light surfaces are achromatic white and gray. Dark surfaces are black and charcoal.
- Light-mode controls and links use near-black graphite. Chartreuse is reserved for dark-mode action and media overlays. An action that sits on a still or on `--scrim` takes `Button`/`ButtonLink` `variant="media"` (the `--media-primary` tokens, hover and active included), never `primary`: in light mode `primary` is graphite, and graphite on a near-black frame is a black pill on black (the title hero and the overview live card shipped that way through 1.10.4).
- Lilac marks collaboration. Blue is information, green is success, amber is warning, and red is failure. Neutral charts do not borrow status colors.
- Brand ground is a state, not a rest. The upload dropzone at rest is a field (`--field-border` on `bg-muted`, hover raises the edge to `--primary-border`), the same in both modes; `--primary-soft` under a `--primary` dash is the drag-over state only. Through 1.10.5 rest wore the brand pair, which in dark was 660×255px of olive under lime that read as a drag in progress.
- State colors always ship as text, soft, border, and foreground tokens. Status pills also include a dot or icon.
- A field is identified by its recessed `--field` ground and its label. `--field-border` is refinement and stays in the soft band (1.2–2.5:1 against every ground it meets); in dark it is quiet enough that the sidebar search reads as a dark well with no visible edge. Never raise it to 3:1 — that is the P-13 misreading. `--control-border` is the separate 3:1 token, and it is only for boundaries that identify on their own: the unfilled checkbox box and the switch track.
- The selected chip is a light step off the card with graphite ink, never an inversion of it. `--selection` was a near-black `#303030` through 1.10.3 — the same hex as `--primary-hover` — and because `--ring` is the same graphite the focus ring vanished inside it at 1.43:1. The fill carries the state quietly; `--selection-border` stays graphite and is what the focus ring paints over and past, so a focused selected row changes ~2px of `--selection` to `--ring` at 13.77:1. Do not darken the fill back, and do not soften the border: `theme.css` records what each of those two costs.
- Never use alpha color states. Use the declared hover, active, soft, and border tokens.
- The one translucent surface is the modal veil, `cutroom-overlay-veil`, which mixes `--scrim` to 78%. It is a non-text graphic under a `--card` panel: no foreground is ever composited against it, so it is not a color state and the rule above stands.
- Never add raw colors, palette utilities, bare shadows, or colored left-border cards.
## File map
- `src/app/` composes ten routes. Pages stay thin.
- `src/components/` contains one self-contained surface per file.The kit is plain markdown, so the work continues on your machine and your own account. Nothing calls back here.