Identity.
Positioning, voice, and visual identity for Evalgist. Code sources from @evalgist/content-style and @evalgist/design-system.
Evidence, not verdicts.
The brand promise. Every external surface stays beneath this ceiling.
Three load-bearing clauses. Large volumes of structured documents: CVs, exam answers, proposals — not arbitrary conversation. Faster, more consistently, with evidence: three measurable promises. Substantiation, not conclusions: the product ceiling is set deliberately below "the AI decides."
Episodic evaluators.
Professionals who do evaluation work a few times a year, not as a main job. The first pilot is academic because the pain is sharpest there, but the product is not education-only.
Sober. Confident. Dry.
Short sentences. Reference voice: The Economist, not TechCrunch. English even in Belgian context. The brand does not joke about regulators.
Prefer
Avoid
✓ Do say
Evalgist Shortlist surfaces the candidates who best match your criteria, each anchored to quotes from their CV.
× Don't say
Supercharge your hiring with revolutionary AI-powered screening that seamlessly shortlists top talent.
Why: States the function, names the evidence. No superlatives, no startup enthusiasm.
✓ Do say
The human remains the decider. The model supplies substantiation.
× Don't say
Our AI makes smarter hiring decisions for you, so you don't have to.
Why: Evalgist never claims to decide. The product's value is that the human is accountable.
✓ Do say
Every score is traceable to a literal passage. Review it before you accept it.
× Don't say
Trust our AI — it's been trained on millions of documents.
Why: Authority comes from traceability, not scale.
Forbidden by default: emoji, exclamationMarks, superlatives, startupEnthusiasm, ironyTowardRegulators. On AI positioning: say "AI-assisted screening", not "Powered by AI". Name the function, not the marketing claim.
Evalgist is the brand. Products take suffixes.
Never sub-brands with independent identity. First mention uses the full name; second mention may shorten to the suffix.
Portfolio: Evalgist Shortlist · Evalgist Grade · Evalgist Review · Evalgist Interview · Evalgist Benchmark.
Eight cells of ink. One cell of tone.
No outline, no frame, no highlight. The absence is a quiet member of the field, not a UI state.
The sizes it will actually be seen at.
Above 24 px the tonal cell renders at slate-300. Below 24 px it lifts automatically to slate-400 so the cell stays legible.
Mark, wordmark, and their agreed proportions.
Geist Sans 600. Primary wordmark ≈ 0.78× mark size; product suffix 10 px uppercase with 0.15em tracking, stacked beneath. Gap between mark and wordmark is optical.
Authoritative specification.
These values are the source of truth. Everything else is a derivation.
The component handles size- and surface-aware logic.
Never manually select between mark variants or hard-code lockup proportions. Import the primitive.
// Product UI — default size, inherits color
import { EvalgistMark } from "@evalgist/design-system/brand";
<EvalgistMark size={20} />
// Dark surface — sidebar, topbar, any inverted region
<EvalgistMark size={24} inverted />
// Full lockup — product pages, auth screens, hero
import { EvalgistLockup } from "@evalgist/design-system/brand";
<EvalgistLockup markSize={32} />
// Product header — Shortlist, Grade
import { EvalgistProductLockup } from "@evalgist/design-system/brand";
<EvalgistProductLockup product="Shortlist" markSize={32} />
// Tight context — nav, breadcrumb, dense header
import { EvalgistWordmark } from "@evalgist/design-system/brand";
<EvalgistWordmark size={15} />// app/layout.tsx — wire the favicons
export const metadata = {
title: "Evalgist",
icons: {
icon: [
{ url: "/favicon.svg", type: "image/svg+xml" },
{ url: "/favicon-32.png", sizes: "32x32", type: "image/png" },
{ url: "/favicon-16.png", sizes: "16x16", type: "image/png" },
],
apple: "/apple-touch-icon.png",
},
manifest: "/site.webmanifest",
};
export const viewport = { themeColor: "#0f172a" };Constraints that protect the reading.
Rules first; then visual examples of violations.
Mark violations
Source files for non-React contexts.
In product code, always use the React components. These files are for slide decks, email signatures, partner decks, press.