House of Slabs

Designer presentation deck

Brand system for live collectible trust.

Use this as the working spec. Every page, document, and component must expose the object, state, proof, and next action using the tokens and anatomy shown in this deck.

  • 01Pages
  • 02Components
  • 03Documents

01 / Creative direction

Use the same required page recipe every time.

1. What is the object?

First visual block is always the slab, pack, wave, shipment, ledger event, chart, or document page.

2. What state is it in?

State is always a chip: live, locked, quoted, high value, danger, grail, one of one, resolved.

3. What proves it?

Show verifier, custody, PSA, carrier, price source, timestamp, or hash beside the object.

4. What happens next?

Expose one primary action plus fallback: rip, resolve, buy back, ship, quote, review, hold.

Do not ship

Do not ship a page where the object, state, proof, or next action has to be inferred.

02 / Palette

Use exact state tokens and raw values.

Hit lime#C7FF3D
--color-brand-hit-lime

Primary action, active wave, verified success

Chase gold#FFC53D
--color-brand-chase-gold

Premium cards, chase pool, high-value review

Live red#FF2E2E
--color-brand-live-red

Danger, failed quote, blocked action, hard stop

Info blue#5CABFF
--color-brand-info-blue

Carrier quoted, adapter status, neutral proof

Grail magenta#FF3DC7
--color-brand-grail-magenta

Grail badge, one-of-one badge, rare reveal only

Ratio80 / 15 / 5

Rule: one dominant accent state per object. Danger overrides all. Grail and one-of-one use grail magenta only when the inventory data says so. Carrier quoted is info blue, not lime or gold.

03 / Typography

Use explicit font roles and text types.

Visual type stackRip proof

Body: use 15px/1.5 for page copy and 18px for short summaries.

Mono: WAVE-04 / LOCKED / 28 OF 40Eyebrow: verifier signal
Display--font-family-display
Anton / Oswald / ImpactHero headlines, slide titles, document covers
Sans--font-family-sans
Manrope / system UIBody copy, labels, controls, metadata
Mono--font-family-mono
JetBrains Mono / SF MonoCounts, codes, hashes, prices, tokens
Display--typography-display-1 / 2 / 3
168 / 112 / 64 maxOne per page. Uppercase. Never use for table or card text.
Headline--typography-headline-1 / 2
36px / 24pxSection titles, card titles, panel titles.
Body--typography-body-lg / body / body-sm
18px / 15px / 13pxSummaries, paragraph copy, helper text.
Label--typography-label
13px semiboldButtons, badges, form labels, compact commands.
Eyebrow--typography-eyebrow
12px bold + 0.16emSlide numbers, metadata headers, section prefixes.
Mono--typography-mono-xl / mono / mono-sm
32px / 13px / 11pxStats, SKUs, hashes, prices, counts, token specimens.

04 / UI language

Use this visible component anatomy.

Locked pool40 cards
Carrier quoted$18.42
High valueReview
DangerHold

Status chip

Top-left or next to title. Use Badge tone names: success, info, warning, danger, grail.

Object area

Fixed aspect area for slab, pack, PDF page, chart, transaction, or quote preview.

Evidence row

Directly under object: timestamp, source, count, price, carrier, verifier, owner, hash.

05 / Usage checklist

Approve or reject with clear rules.

Approve when

  • Pages: first screen has title, object/state, proof, and one primary action.
  • Components: state chip, object area, evidence row, and action slot are present.
  • Documents: each page has a title, page number, source/date, and decision summary.
  • Color: every accent maps to a real token/state listed in this guide.
  • Type: display, headline, body, label, eyebrow, and mono roles match this guide.

Reject when

  • A user cannot tell what object or state they are looking at in three seconds.
  • A badge uses danger, grail, high value, or quoted colors without matching data.
  • A card hides custody, pricing, carrier, verifier, or count metadata in a drawer.
  • Text styles are improvised instead of using the defined type roles and tokens.
  • The layout looks like generic SaaS, a crypto dashboard, or decorative brand art.