---
name: fluency-brand-guidelines
description: "Design, build, or substantially improve an official Fluency-authored page. Use for customer executive reports, pilot readouts, opportunity analyses, proposals, business cases, ROI or payback calculators, security and privacy briefs, benchmarks, and one-off landing or decision pages that need Fluency information architecture, Instrument Sans typography, evidence-led data storytelling, and responsive craft."
---

# Design pages like Fluency

Use this guide for work commissioned by Fluency. Identify the actual author and use customer names, marks, quotes and results only when cleared for the intended audience. A public artifact requires clearance for public reuse. Shape the argument and the interface together; do not restyle a data dump or assemble generic components.

## Fluency product and brand context

Fluency is a work intelligence platform. It keeps a living, evidence-backed model of how an enterprise works (the work ontology), built from opt-in observation of work, so decisions about how work should change are made on evidence and then measured. Readers are operations leaders, COOs, CIOs, finance executives, transformation teams, security reviewers and works councils.

Make the artifact precise, calm, direct, specific and evidence-led: an institution the reader can trust with sensitive, consequential work, that still sounds ambitious. Build confidence through clarity, proof and command of the material. Never manufacture confidence through hype, decoration, novelty, false certainty or invented numbers.

Start with the reader's job, not the document type. Identify what the reader must understand or decide, the strongest supported answer, the evidence that earns it, and the caveat that could change it.

Two beliefs shape every Fluency page:

- **Work, not people.** The thing observed is always work or a process. Never write or imply "monitor employees", "track productivity" or "see what your people do all day". No eye or camera imagery.
- **Evidence over adjectives.** Every figure carries its unit, scope and period. Every claim is labelled with how much weight it can carry.

Treat calculators and interactive pages as brand surfaces too. Communicate official Fluency authorship without resembling the Fluency product UI, a generic SaaS landing page or a campaign.

## Download logos

Official Fluency horizontal lockup (symbol plus wordmark), transparent backgrounds:

- For light backgrounds: [Black SVG](https://usefluency.com/brand-assets/svg/logo-horizontal-black.svg) · [Black PNG](https://usefluency.com/brand-assets/png/logo-horizontal-black.png)
- For dark backgrounds: [White SVG](https://usefluency.com/brand-assets/svg/logo-horizontal-white.svg) · [White PNG](https://usefluency.com/brand-assets/png/logo-horizontal-white.png)

Symbol only, for square, small or repeated placements:

- [Black SVG](https://usefluency.com/brand-assets/svg/icon-black.svg) · [Black PNG](https://usefluency.com/brand-assets/png/icon-black.png) · [White SVG](https://usefluency.com/brand-assets/svg/icon-white.svg) · [White PNG](https://usefluency.com/brand-assets/png/icon-white.png)

Fetch these URLs directly. Prefer SVG for web; use PNG only when a raster is required. Never use the files named `-color` or `-blue`: the blue mark is retired. See the [brand asset catalog](https://usefluency.com/brand-assets.md) for clear space, minimum sizes and permitted use. Inside a page, use the `.flu-lockup` and `.flu-symbol` classes instead of image tags (see Authorship shell).

## Use this priority order

When requirements compete, protect them in this order:

1. Preserve supplied facts, formulas, units, qualifiers, privacy requirements and task constraints.
2. Preserve the caller's framework, routes, delivery surface and established Fluency foundation.
3. Make the reader's question, the strongest supported answer and the material evidence immediately clear.
4. Keep claims honest: label evidence, never invent proof, never imply capabilities that do not ship.
5. Establish unmistakable Fluency authorship through the shell, Instrument Sans, the shared grid and restraint.
6. Choose a composition specific to this material; avoid both generic model defaults and a fixed template.
7. Refine responsive behaviour, interaction and details without weakening the hierarchy.

Ask one grouped set of questions only when proceeding could change commercial meaning, security, privacy or legal claims, formulas, units, populations, periods, customer identity, recommendations, approvals, deadlines, owners or calls to action. Otherwise omit the unknown, label it honestly and proceed.

## Integrate with the caller's project

- Preserve the host framework, file structure, routes, build system and output form. Do not force a filename or a single-file deliverable.
- Load the stylesheet from `https://usefluency.com/design/fluency-brand.css`. If that URL cannot be loaded in the target environment, copy the file and serve it locally, or inline its exact bytes. Never emit `file://` paths, placeholder URLs, a translated token system or a CSS `@import`.
- Stock v0, Next.js, Tailwind or shadcn projects: keep the stack. Add the stylesheet at the page boundary and use the `.flu-*` classes for brand surfaces. In React: `<link rel="stylesheet" href="https://usefluency.com/design/fluency-brand.css" precedence="flu" />`.
- Standalone HTML:

```html
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Instrument+Sans:wght@400;500&family=JetBrains+Mono:wght@400&display=swap" rel="stylesheet" referrerpolicy="no-referrer">
<link href="https://usefluency.com/design/fluency-brand.css" rel="stylesheet">
```

- Inside the usefluency.com codebase or the Fluency product, use the installed tokens and components instead of this layer.
- Page CSS may read public `--flu-*` tokens and must use its own namespace (`.flu-custom-*`, `.flu-viz-*`). Never restyle a published `.flu-*` class.
- Network allowlist: the stylesheet, the Fluency assets above, Google Fonts and user-supplied assets. No third-party JavaScript, chart libraries, icon kits, stock imagery or analytics unless the caller authorises them.

## Work in four passes

### Frame the reader's job

Privately establish who opens the page, what they must decide, the strongest supported answer, the evidence that earns it, the trade-off, and what belongs in the audit trail.

- Normalise facts, units, dates and sources. Write dates unambiguously (10 Sep 2026, never 10/09/2026). One rounding rule per page.
- Distinguish observation, derivation, projection, recommendation and causation. Say "after adopting", never "because of", unless a control group measured it.
- Give two reading paths: an executive path in plain language (claim, number, decision) and an audit path (exact tables, assumptions, methodology) further down or behind a disclosure.
- Every section answers a new reader question. Cut sections that repeat a conclusion.
- Leave out failed attempts, tool diaries and internal or server terms ("pipeline", "KG", error strings).

### Choose the composition

The first viewport is the argument: the claim, the headline number and what the reader should do. Reject the obvious category layout and compare two composition hypotheses before building.

Match the opening to the job:

| Job | Opening |
|---|---|
| Recommendation or decision | The recommendation as the title, the number that earns it, the decision and its cost |
| Where the time goes | One sentence answer, then a stat strip of the two or three figures that matter |
| Comparison | The winner and the margin, then aligned rows on a shared scale |
| Calculator or business case | The default result already rendered, inputs beside it |
| Security or privacy brief | The controls in plain language, then verifiable specifics |
| Landing page | Hero promise, early proof, workflow, value pillars, customer result, objection, final action (one question each) |

Map data to geometry: magnitude to length on a common scale; time to horizontal order; composition to proportion; process to the trace (ordered steps joined by a hairline); alternatives to aligned rows. Use tables for lookup, prose for one conclusion, charts only for relationships. One throughline per section. Squint at the page: the hierarchy should survive.

### Authoritative Fluency visual system

#### Authorship shell

Lockup on the left of the header; symbol on the left of the footer. Header right: at most two sourced fields (recipient, date). Footer right: at most one ownership or confidentiality line. The footer may carry the trace rule. Separate with spacing, not borders. Use this markup, in this order:

```html
<body class="flu-page">
  <div class="flu-shell">
    <a class="flu-skip-link" href="#main">Skip to content</a>
    <header class="flu-header">
      <div class="flu-masthead">
        <span class="flu-identity"><span class="flu-lockup" role="img" aria-label="Fluency"></span></span>
        <div class="flu-document-meta"><span>Illustrative claims workflow</span><span>Sample document</span></div>
      </div>
    </header>
    <main id="main">...</main>
    <footer class="flu-footer">
      <div class="flu-trace-rule"><i></i><i></i></div>
      <div class="flu-footer-row">
        <span class="flu-symbol" role="img" aria-label="Fluency"></span>
        <span>Fictional example</span>
      </div>
    </footer>
  </div>
</body>
```

Do not substitute text, inline art, a serif wordmark or a coloured logo. The marks are ink on light and white on dark, nothing else.

#### Grid and alignment

- 12 columns at 1280px and wider, 8 from 768px, 4 below. Content max 1248px; side margins 48 / 32 / 20; gutters 24 / 16 / 16.
- Prose spans 5 to 7 columns (65 characters maximum). Tables, charts and calculators may span 12.
- Section padding 96 / 64 / 48. Spacing comes only from the scale: 4 8 12 16 20 24 32 48 64 96 128.
- Every object aligns to a shared edge. Three true peers may share a row; do not force unequal findings into equal cells.
- Content sets section height. No fixed-height heroes.

#### Typography and rhythm

- Instrument Sans for everything, weights 400 and 500 only (never 600 for headings, never 700). JetBrains Mono only for IDs, timestamps, code, source lines and axis labels. Headline figures use Instrument Sans with tabular numerals.
- Roles: `flu-display` (one page-defining statement, 64px desktop), `flu-title` (section, 48px), `flu-heading-24`, `flu-heading-20`, `flu-heading-16`, `flu-lede` (20px), body (18px), `flu-label`, `flu-caption` (12px, the minimum), `flu-meta`.
- Headings: medium weight, -2.5% tracking, sentence case, one or two balanced lines, left-aligned. Each states a reader-specific claim ("Claims intake is where the time goes"), not a topic ("Overview").
- No eyebrows above headings. No all-caps labels. No em dashes in copy. No exclamation marks.
- Gaps: within a group 8 to 16; between groups 24 to 32; section turns 48 to 96.
- Units inline and compact: `3,420 h/yr`, `$86,400/yr`, `$48/hr`. Middle dot (·) as a separator. Missing values are "–", never 0 or N/A.

#### Color, surfaces and boundaries

- Monochrome zinc. No brand accent colour, no blue. Emphasis comes from type size, weight and ink density.
- Sections are white, zinc-50 (`.flu-band[data-tone="raised"]`) or dark zinc-950 (`.flu-band[data-tone="contrast"]`). Alternate tones to separate sections. At most two dark sections per page; use them for the opening or the closing decision.
- Colour appears only for status, always with a word: success green, warning olive, danger red via `.flu-status`. Never favourable-means-green on charts.
- Borders over shadows: depth comes from a 1px zinc-200 line or a tonal step. **No drop shadows anywhere**; the focus ring is the only shadow. No nested cards.
- Light theme only. No theme switcher.
- Hard reject: gradients, glows, blobs, glassmorphism, grain, grid backgrounds, neural-net meshes, coloured side rails and ornamental shadows.

#### Data and evidence

- Label every figure, quote and product example with `.flu-proof` and a `data-kind`: `customer-reported` (measured by the customer, approved for use), `pilot` (scoped pilot; show scope and period), `illustrative` (fictional example data or company), `estimated` (model or projection; state the assumption). Pair it with a `.flu-source` line: unit, scope, period, source.
- Omit a claim when approved evidence is missing. If the brief calls for a demonstration, label its fictional inputs beside each result. Keep customer evidence, annualised estimates and fictional examples distinct when a section is quoted on its own.
- Put proof beside the claim it supports, in the same section.
- Zero baselines for length encodings. Bars share one scale; label lane, plot lane and value lane align across rows. Direct labels over legends.
- Chart series: zinc-900, then zinc-400, then zinc-300. One highlighted series may use `--flu-chart-highlight` (pink) in analytics only. No pies, donuts, 3D, dual axes or stacked areas. 11px mono axis labels, zinc-100 horizontal gridlines only.
- Gaps for missing data, never interpolated or zero. Mark partial periods.
- Tables are semantic `<table>` with caption, head and body, inside `.flu-table-wrap`, full width by default. Numeric headers and cells use `.flu-numeric`. Highlight a recommended row (`tr[data-highlight]`) only when the source supports it.

```html
<div class="flu-stat-strip">
  <div class="flu-stat">
    <p class="flu-stat-label">Illustrative rekeying time</p>
    <p class="flu-stat-value">1,555<small>h/yr</small></p>
    <p class="flu-stat-detail">Fictional claims intake team · annualised example</p>
  </div>
</div>
<p class="flu-source"><span class="flu-proof" data-kind="illustrative">Illustrative</span> Fictional inputs · hours per year</p>
```

#### Process and the trace

The trace is Fluency's one recurring motif: a 1px hairline joining 6px square nodes, drawing one piece of work across people, agents and systems. Executor type shows through the node's fill only: person filled, agent outlined, system half-filled. Use it for workflows, the footer rule and title cards. If it does not trace actual work, do not draw it.

```html
<ol class="flu-trace">
  <li class="flu-trace-step"><span class="flu-trace-node" data-executor="person"></span>
    <span class="flu-meta">01 · Input</span><h3 class="flu-heading-24">Claim arrives by email</h3>
    <p class="flu-body">An intake officer reads the policy number.</p></li>
  <li class="flu-trace-step"><span class="flu-trace-node" data-executor="agent"></span>...</li>
</ol>
```

Always show the human decision point in a workflow. Fluency recommends; people decide.

#### Calculators and interaction

- One canonical state model: variables, fixed inputs, formulas, units, ranges, defaults and precision. One control per variable.
- Pre-render the default result. Keep invalid entries visible with an error and keep the last valid result.
- Identify the source and currency of each rate. Label any example rate as an editable assumption. Include a reset for editable projections.
- Native controls with visible labels; placeholders are not labels. `.flu-calculator` owns `.flu-calculator-inputs` and `.flu-calculator-output`.

```html
<div class="flu-field">
  <label for="rate">Loaded hourly rate</label>
  <div class="flu-unit-field"><span class="flu-unit-prefix">$</span><input id="rate" type="number" value="48"><span class="flu-unit-suffix">/hr</span></div>
  <p class="flu-helper">Illustrative assumption · USD per hour. Edit to match your costs.</p>
</div>
```

#### Actions

One action per page, literal and the same everywhere: **Book a demo** (`.flu-button`). A secondary literal text link is allowed (`.flu-link`, "Read the methodology"). For customer reports the action is the decision itself ("Approve the intake agent for a four-week build"). Never "Get started", "Start your journey" or a free trial.

#### Motion

Default to stillness. Motion only explains a change: transform and opacity, 120 to 260ms, `cubic-bezier(0.2, 0, 0, 1)`. Animate individual elements or nothing; never pulse or scale a whole graphic. No bounce, parallax, marquees, typing effects or scroll-gated reveals. Respect reduced motion.

#### Media and icons

- Product screenshots only as evidence, cropped to teach one thing, inside `.flu-screenshot` (white, 1px border, 6px radius, no browser chrome, no shadow, no tilt) with fictional data labelled Illustrative. Use customer screenshots only with redaction and permission for the intended audience. Product text must stay 12px or larger at delivery size. At most three annotations of eight words or fewer.
- Photography is atmosphere only: real places where enterprise work happens, calm, neutral grade, people never identifiable as being watched.
- Icons: Lucide, stroke 2, inheriting text colour, only where they label something. No icon tiles, no emoji, no decorative icons. Never AI imagery that depicts a customer, a real place or a real event.

### Inspect and revise privately

Render and inspect the first viewport, the full page and reflow at 390, 768 and 1440 wide. Review in order: first read, language, composition, typography, evidence and labels, restraint, reflow, trust and access. Fix what fails. Deliver the page, not a score or a diary.

## Reject generated-design reflexes

- Eyebrows or all-caps labels above headings
- Em dashes, exclamation marks, "unlock", "supercharge", "seamless", "revolutionise"
- Gradients, glows, blobs, glass, grain, grid backgrounds or any drop shadow
- Blue or any brand accent colour; colour without a word beside it
- A centred hero above a three-card grid
- Repeated metric boxes; pills for ordinary metadata; nested cards
- Dark rounded rectangles around charts or calculators
- Icon tiles, emoji, stock photos, fake screenshots, AI illustrations of people
- Surveillance language or imagery: monitoring employees, eyes, cameras, CCTV
- Unlabelled numbers, figures without unit, scope or period, invented customers or logos
- Tiny muted prose; text under 12px; tables floating narrow in wide sections
- Legends replacing direct labels; bars without a shared scale
- Identical section silhouettes; the same conclusion stated twice
- Captions narrating how the page was made; visible theme or print controls

## Use the published CSS API

Put `.flu-page` on `<body>` and wrap content in `.flu-shell`. Use `.flu-container` inside each section to apply the content width and margins.

- **Shell and layout:** `flu-skip-link`, `flu-header`, `flu-masthead`, `flu-identity`, `flu-lockup`, `flu-symbol`, `flu-document-meta`, `flu-footer`, `flu-footer-row`, `flu-trace-rule`, `flu-container`, `flu-opening`, `flu-opening-claim`, `flu-opening-proof`, `flu-opening-actions`, `flu-section`, `flu-section-header`, `flu-band` (`data-tone="raised"` or `"contrast"`), `flu-grid`, `flu-span-4`, `flu-span-5`, `flu-span-6`, `flu-span-7`, `flu-span-8`, `flu-span-12`, `flu-split`, `flu-stack` (`data-gap="tight"` or `"loose"`), `flu-cluster`, `flu-reading`
- **Type:** `flu-display`, `flu-title`, `flu-heading-24`, `flu-heading-20`, `flu-heading-16`, `flu-lede`, `flu-body`, `flu-compact`, `flu-label`, `flu-caption`, `flu-meta`, `flu-mono`, `flu-numeric`, `flu-visually-hidden`
- **Evidence:** `flu-proof` (`data-kind`), `flu-source`, `flu-note`, `flu-sources`, `flu-stat-strip`, `flu-stat`, `flu-stat-label`, `flu-stat-value`, `flu-stat-detail`, `flu-table-wrap`, `flu-chart`, `flu-chart-header`, `flu-bar-list`, `flu-bar` (`data-series="2"` or `"3"`, `style="--value: 0-100"`), `flu-bar-label`, `flu-bar-track`, `flu-bar-fill`, `flu-bar-value`, `flu-status` (`data-tone="success|warning|danger|neutral"`)
- **SVG charts:** `flu-chart-gridline`, `flu-series-1`, `flu-series-2`, `flu-series-3`, `flu-series-highlight`, `flu-chart-direct-label`
- **Process and proof blocks:** `flu-trace`, `flu-trace-step`, `flu-trace-node` (`data-executor="person|agent|system"`), `flu-quote` (on `<figure>` with `<blockquote>` and `<figcaption>`), `flu-fact-list`, `flu-fact`, `flu-figure`, `flu-screenshot`
- **Actions and calculator:** `flu-button` (`data-size="default"` for the compact size), `flu-link`, `flu-calculator`, `flu-calculator-inputs`, `flu-calculator-output`, `flu-field`, `flu-field-label`, `flu-unit-field`, `flu-unit-prefix`, `flu-unit-suffix`, `flu-helper`, `flu-error`, `flu-result`, `flu-result-label`, `flu-result-value`, `flu-result-detail`

Page-readable tokens:

- **Surfaces and text:** `--flu-surface-primary`, `--flu-surface-raised`, `--flu-surface-muted`, `--flu-surface-contrast`, `--flu-text-primary`, `--flu-text-secondary`, `--flu-text-tertiary`, `--flu-text-disabled`, `--flu-text-on-contrast`, `--flu-text-on-contrast-secondary`
- **Boundaries and state:** `--flu-border-subtle`, `--flu-border-default`, `--flu-border-strong`, `--flu-border-on-contrast`, `--flu-action`, `--flu-action-text`, `--flu-focus-ring`, `--flu-success-fg`, `--flu-success-bg`, `--flu-warning-fg`, `--flu-warning-bg`, `--flu-danger-fg`, `--flu-danger-bg`
- **Data:** `--flu-chart-1`, `--flu-chart-2`, `--flu-chart-3`, `--flu-chart-highlight`, `--flu-chart-grid`, `--flu-trace`, `--flu-trace-context`
- **Type:** `--flu-font-sans`, `--flu-font-mono`, `--flu-type-display`, `--flu-type-title`, `--flu-type-heading-24`, `--flu-type-heading-20`, `--flu-type-heading-16`, `--flu-type-lede`, `--flu-type-body`, `--flu-type-compact`, `--flu-type-label`, `--flu-type-caption`, `--flu-type-stat`, `--flu-weight-regular`, `--flu-weight-medium`, `--flu-tracking-heading`
- **Rhythm and shape:** `--flu-space-1` to `--flu-space-6`, `--flu-space-8`, `--flu-space-12`, `--flu-space-16`, `--flu-space-24`, `--flu-space-32`, `--flu-radius-small` (4px), `--flu-radius` (6px), `--flu-content-max`, `--flu-margin`, `--flu-gutter`, `--flu-duration-fast`, `--flu-duration-base`, `--flu-ease`

Never invent, alias or redeclare a `--flu-*` token. Do not read the stylesheet to find internal selectors.

## Accessibility and responsive behaviour

Landmarks, one descriptive `h1`, ordered headings, a skip link, native controls, semantic tables, `figure` with `figcaption`, visible focus (the focus ring), WCAG AA contrast (muted text is zinc-500 or darker on white; zinc-400 is for disabled only), and no colour-only meaning. Give grid and flex children `min-width: 0`. Reflow before shrinking type. No hidden overflow; long tables may scroll inside `.flu-table-wrap`. Every image and chart has alt text or a caption that states its takeaway.
