better-typography ยท diff
v5.0.0 to v5.0.0
1 added, 76 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: better-typography
- description: Use when Web typography from choosing fonts to spacing, wrapping, and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, styling text in components, truncating text, styling underlines, selection, placeholders, or carets. Triggers on typography, fonts, variable fonts, font-weight, opentype, letter-spacing, line-height, type scale, tabular numbers, text-wrap, truncation, line clamp, measure, line length.
+ description: "Use when Web typography from choosing fonts to spacing, wrapping, and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, styling text in components, truncating text, styling underlines, selection, placeholders, or carets. Triggers on typography, fonts, variable fonts, font-weight, opentype, letter-spacing, line-height, type scale, tabular numbers, text-wrap, truncation, line clamp, measure, line length."
version: 5.0.0
last-updated: 2026-09-13
tools: Read, Grep, Glob, Bash, Edit, Write
scripts-binding:
- .agent/scripts/lint_runner.js
- .agent/scripts/verify_all.js
---
# Better Typography โ Web Typography & Font Engineering
- ## Mandatory Pre-Flight Context Inspection
-
- Before generating, refactoring, or reviewing code in the `better-typography` domain, inspect these 5 critical parameters:
-
- 1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
- 2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
- 3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
- 4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
- 5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
-
- ## Activation Boundaries
-
- - **Activate when:** Use when Web typography from choosing fonts to spacing, wrapping, and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, styling text in components, truncating text, styling underlines, selection, placeholders, or carets. Triggers on typography, fonts, variable fonts, font-weight, opentype, letter-spacing, line-height, type scale, tabular numbers, text-wrap, truncation, line clamp, measure, line length.
- - **DO NOT activate when:** The task falls outside the `better-typography` domain or is managed by a different dedicated specialist.
-
- ## ๐ Multi-Pass Execution Protocol
-
- Execute all non-trivial tasks through this 7-pass cognitive loop:
-
- | Pass | Phase | Core Action |
- | :--------- | :--------------- | :------------------------------------------------------------------------------------------- |
- | **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. |
- | **Pass 2** | **Plan** | Decompose the task into smallest logical steps; map dependencies and required tool calls. |
- | **Pass 3** | **Execute** | Implement the solution with production-grade craft, zero placeholders, and strict typing. |
- | **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. |
- | **Pass 5** | **Attack** | Perform an adversarial review searching for edge-case failures, race conditions, and traps. |
- | **Pass 6** | **Improve** | Eliminate discovered friction, optimize performance, and harden error boundaries. |
- | **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. |
-
---
## ๐ ๏ธ Technical Architecture & Reference Recipes
---
## 1. Modular Type Scales & Line Cadence
Scale font sizes using a consistent multiplier ($1.25$ Major Third or $1.20$ Minor Third):
```css
:root {
--font-size-xs: 0.75rem; /* 12px - Labels, Badges */
--font-size-sm: 0.875rem; /* 14px - Meta, Caption */
--font-size-base: 1rem; /* 16px - Body Text */
--font-size-lg: 1.125rem; /* 18px - Lead Body */
--font-size-xl: 1.375rem; /* 22px - Subheadings */
--font-size-2xl: 1.75rem; /* 28px - H3 */
--font-size-3xl: 2.25rem; /* 36px - H2 */
--font-size-4xl: 3rem; /* 48px - H1 Hero */
/* Line Heights proportional to font size */
--line-height-heading: 1.15;
--line-height-body: 1.5;
--line-height-tight: 1.25;
}
```
---
## 2. Line Length (Measure) & Text Wrapping
- **Optimal Line Length (Measure)**: Body text MUST be constrained between **45 to 75 characters** per line (`max-width: 65ch`).
- **Heading Balancing**: Always apply `text-wrap: balance` to headings (`h1`-`h4`) to eliminate single-word widows.
- **Paragraph Wrapping**: Use `text-wrap: pretty` for long body paragraphs to prevent awkward line breaks.
```css
h1,
h2,
h3,
h4 {
text-wrap: balance;
letter-spacing: -0.025em;
line-height: var(--line-height-heading);
}
p {
max-width: 65ch;
text-wrap: pretty;
line-height: var(--line-height-body);
}
```
---
## 3. OpenType Features & Tabular Numbers
- **Tabular Numbers for Data & Timers**: Use `font-variant-numeric: tabular-nums` (or `tnum`) for data tables, counters, prices, and timestamps so numbers align vertically without jumping when values update.
- **Font Smoothing**: Enable crisp font smoothing on macOS/iOS:
```css
body {
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale;
}
```
---
## Anti-Slop Table
| Anti-Pattern | Typography Solution | Rationale |
| ------------------------------------------- | ------------------------------------ | ------------------------------------------------ |
| Full-width body text (`width: 100%`) | `max-width: 65ch` | Prevents eye fatigue across wide desktop screens |
| Single-word widows on headings | `text-wrap: balance` | Creates balanced visual hierarchy |
| Jittering numbers in data tables | `font-variant-numeric: tabular-nums` | Keeps columns strictly aligned |
| Default browser line-height (`1.2` on body) | `line-height: 1.5` | Improves reading comfort |
-
- ---
-
- ## ๐จ Edge-Case & Failure Mode Matrix
-
- | Scenario | Risk | Mitigation Strategy |
- | :------------------------------------- | :--------------------------------------------------- | :------------------------------------------------------------------------------ |
- | **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
- | **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
- | **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
- | **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
- | **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
-
- ---
-
- ## ๐ค LLM-Specific Traps Table
-
- | Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
- | :--------------------------------- | :------------------------------------------------------------------------ | :----------------------------------------------------------------------- |
- | **Hallucinated Tool Capabilities** | Assuming an external library or CLI command exists without verification | Run a verification check or verify package.json before referencing tools |
- | **Premature Completion Claim** | Declaring a task finished because code was generated without verification | Execute tests, linters, or terminal commands to provide concrete proof |
- | **Context Bloat Dumping** | Pasting entire multi-thousand-line files into prompt context | Extract targeted excerpts, symbols, and signatures to preserve tokens |
-
- ---
-
- ## ๐๏ธ Tribunal Verification & Guardrails
-
- **Active Reviewers:** `orchestrator` ยท `agent-organizer` ยท `logic-reviewer`
- **Slash Command:** `/review` or `/tribunal-full`
-
- ### โ
Pre-Flight Self-Audit Checklist
-
- ```
- โ
Did I deconstruct the root objective before proposing architecture?
- โ
Did I identify dependencies, bottlenecks, and parallelizable sub-tasks?
- โ
Did I avoid over-engineering and select the simplest effective pattern?
- โ
Did I verify assumptions with concrete file reads instead of speculation?
- โ
Did I establish measurable verification criteria before completion?
- ```
-
- ### ๐ Verification-Before-Completion (VBC) Protocol
-
- **CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-
- - โ **Forbidden:** Declaring a task complete because the output "looks correct."
- - โ
**Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing test suites, compiler success, or equivalent operational proof) that your output works as intended.