Clearing owner's guide
Everything from the download to your own palette, read from the files this theme ships.
- 1.0.0
- version
- 7
- pages
- 28
- components
- 120 × 2 modes
- tokens
- 4
- workflows
unzip clearing-1.0.0.zip
cd clearing-1.0.0
bun install
bun devThe download is a complete Next.js project, not a folder of snippets. It carries 7 routes, the token file, 28 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 clearing-1.0.0.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/clearing/, mirroring the tree below.
bunx shadcn add https://tailthemes.com/r/clearing.jsonClearing is paid, so the registry answers 402 with the price, the purchase URL and both token tables. Only the source files are withheld.
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.
- /Cash position4 sections
- /forecastThirteen-week forecast2 sections
- /paymentsPayment run R-26342 sections
- /accountLloyds · Operating2 sections
- /counterpartySolvay Chemicals BV3 sections
- /exposureExposure and facilities2 sections
- /componentsThe parts10 sections
Tokens are declared on .tt-clearing as well as :root, so an install cannot repaint components you already have. Wrap the page in <div className="tt-clearing"> 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 7 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 7 pages you saw above exist in both.
Making it yours
Tokens are the API: change the values, never the names.
- Edit the values. All 120 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
A page in src/app/ composes sections and does nothing else: no data fetching, no arithmetic, no markup that belongs in a section. Six routes ship today.
- .claude/skills/add-section
A section is one file in src/components/, self-contained, importing only from src/components/ui/. Sections never import each other — that rule is what lets a buyer delete one without a cascade.
- .claude/skills/check-quality
Four checks, in this order. The first three are mechanical and the fourth is the one that finds real defects.
- .claude/skills/rebrand
Every design decision in this theme lives in src/theme.css. Nothing in src/components/ or src/app/ carries a colour or a size, so a rebrand is a stylesheet edit plus a fixture edit — and if you find yourself editing a component to change a colour, you have found a bug, not a requirement.
Those summaries are the files' own opening lines. They are written against this repo, so where one names themes/clearing/ 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 299 lines of invariants, the file map, the type and spacing scale, and what never to touch. It opens like this.
# Clearing — the rules
You are working inside a shipped theme. This file is the contract; the repo's
`themes/CONTRACT.md` is the law above it. Read both before changing anything.
## What this theme is
**Clearing** is a treasury and cash-forecast dashboard. The fiction is
**Bellhouse Compounds**, a 340-person specialty-chemicals manufacturer in
Warrington: seven accounts across five banks in three currencies, a supplier
payment run every Thursday, a revolving credit facility whose covenant requires
£2.0m of liquidity at every week end, and a €4.10m development-loan repayment in
week 10 that takes them through it. That last fact is the reason the product
exists — every route is either finding it, explaining it, or doing something
about it.
**Positioning.** For the finance lead who has to say on Monday morning how much
cash is where and what leaves this week — unlike the accounting dashboards that
report last month's P&L, this is a forward view, and the number it is built
around is the week the money runs short.
**Fiction boundary.** The catalog already carries three money-ops fictions —
grove (bookkeeping close), relay (subscription billing queue), marquee (revenue
reconciliation). Clearing is none of them: it is the company's *own* cash,
looking forward, and the job is liquidity rather than reconciliation. Keep it
that way. A feature that reconciles invoices belongs in marquee.The kit is plain markdown, so the work continues on your machine and your own account. Nothing calls back here.