jig-ui 0.8.2 → 0.9.0

package/CHANGELOG.md

@@ -1,5 +1,50 @@
 # Changelog
 
+## 0.9.0
+
+One new rule and one amended correction, both from the same afternoon of
+dogfooding and both about the same blind spot: H-47's correction always pointed
+at a token, so an agent reading it literally always produced one.
+
+### Added
+
+- **`B-105` Monospace sized by a guessed ratio.** No rule in the corpus
+  mentioned monospace or inline `code` at all — `jig explain monospace` returned
+  nothing — while `brand.default.css` ships a `--font-mono` stack, so every Jig
+  project has the pairing and none had guidance on it.
+
+  Shrinking inline code by a ratio is right for faces drawn apart, where a mono
+  face often does sit larger at the same `font-size`. In a superfamily it is
+  wrong: IBM Plex Sans and IBM Plex Mono are both x-height 51.6 and cap-height
+  69.8 per 1000 units — identical — and mono is *narrower*. A `0.9em` there sets
+  code at x-height 46.8 inside text at 52, creating the mismatch it was meant to
+  remove. The rule asks for one measurement, once per project, when the brand
+  file is written.
+
+  It deliberately has no token. Inline `code` appears inside body text,
+  headings, table cells and captions; one multiplier has to be right for all
+  four, and a fixed token is worse — it collapses code in a heading to caption
+  size. Inheriting is correct in every host.
+
+### Changed
+
+- **`H-47`'s correction names a third branch.** It offered "reference the token"
+  or "a value that cannot be expressed as a token indicates a missing token".
+  Both end in a token. Twice in a row on Jig's own documentation site the right
+  answer was **deletion** — the `0.9em` above, and a `min-width` in `em` on a
+  table column that `max-content` measures for free. An agent following the text
+  as written invents `--text-code: 0.9em` and entrenches a value that should not
+  exist. The correction now says to check "should this value exist at all"
+  before minting a token.
+
+  `rules.index.json`'s `fix: token-substitute` on H-47 encoded the same
+  assumption and is now `token-substitute-or-remove`. Nothing consumes that
+  field yet, which is why it was worth correcting before something does.
+
+- **Rule count is 105.** The attestation line and the README's counts move with
+  it.
+
+
 ## 0.8.2
 
 Every fix here was found by a consumer using Jig rather than by Jig checking

package/README.md

@@ -12,7 +12,7 @@ Installed as `npx jig-ui` — the bare name was taken on npm.
 Jig is **a skill your coding agent reads**, and **a CLI you can run yourself**.
 They are two halves of the same thing, and the split is not arbitrary:
 
-- Of the 104 rules, **7 can be decided by a machine** — a hard-coded colour, a
+- Of the 105 rules, **7 can be decided by a machine** — a hard-coded colour, a
   contrast ratio below the floor, a removed focus ring. The CLI decides those.
 - The other **97 are judgment** — whether an empty state says anything useful,
   whether a label reads as an instruction, whether motion earns its place. No
@@ -181,7 +181,7 @@ on the result — the CLI reports, the agent applies the judgment half.
 | Slash command | Equivalent |
 | --- | --- |
 | `/jig init` | `jig init` — then states the mode it chose and what it wired |
-| `/jig check` | `jig check` — then applies the 94 judgment rules and reports both halves |
+| `/jig check` | `jig check` — then applies the 95 judgment rules and reports both halves |
 | `/jig explain C-19` | `jig explain C-19` — prints the rule as-is, without paraphrasing it |
 | `/jig explain contrast` | `jig explain contrast` — every rule matching a word, when you do not have an id |
 | `/jig install --agent cursor` | `jig install --agent cursor` |
@@ -262,7 +262,7 @@ In CI:
 code — nothing model-dependent, no network. As a pre-commit hook, plain `check`
 looks at changed files only.
 
-What you will not get from the CLI alone is the other 94 rules. `check` says so
+What you will not get from the CLI alone is the other 95 rules. `check` says so
 rather than letting a narrow pass read as a broad one.
 
 ## What `check` covers
@@ -330,7 +330,7 @@ treatment.
 
 | File | Contents |
 | --- | --- |
-| `rules/00-anti-patterns.md` | 87 universal rules with corrections |
+| `rules/00-anti-patterns.md` | 88 universal rules with corrections |
 | `rules/01-modes.md` | `editorial` / `product` / `operator` profiles |
 | `rules/02-tokens.md` | Token contract, naming, consumption |
 | `rules/03-patterns.md` | Component anatomy and behaviour |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jig-ui",
-  "version": "0.8.2",
+  "version": "0.9.0",
   "description": "A design system for coding agents. 104 numbered UI rules, brand x mode design tokens, and an installer for Claude Code, Codex, Cursor and opencode.",
   "license": "Apache-2.0",
   "type": "module",

package/rules/00-anti-patterns.md

@@ -144,6 +144,13 @@ Four workable treatments:
 4. **Solid background behind the text** — the caption approach; most reliable, least subtle.
 A text shadow may reinforce any of these but never substitutes for one. Verify against the worst image the slot will ever hold, not the one in the mockup.
 
+### B-105 Monospace sized by a guessed ratio
+❌ Inline `code` set to `0.9em` — or any fixed ratio — to stop it looking bigger than the text around it
+✅ Measure both faces before correcting either. If they share an x-height, the ratio is the mismatch. Let code inherit its host's size.
+The habit comes from pairings where it is true: a mono face drawn separately from the text face often does sit larger at the same `font-size`. In a superfamily it does not. IBM Plex Sans and IBM Plex Mono are both x-height 51.6 and cap-height 69.8 per 1000 units — identical — and mono is *narrower*, not larger. A `0.9em` there sets code at x-height 46.8 inside text at 52, creating the mismatch it was meant to remove.
+A ratio is also the wrong shape of answer. Inline `code` appears inside body text, headings, table cells and captions; one multiplier has to be right for all of them, and a fixed token is worse still — it collapses code in a heading to caption size. Inheriting is correct in every host, which is why this rule has no token.
+The measurement is one line in a browser: render `x` in both faces at the same size and compare the rendered heights, or read `sxHeight` from each font's `OS/2` table. Do it once per project when the brand file is written, not per component.
+
 ---
 
 ## C. Colour and contrast
@@ -485,7 +492,8 @@ Where people must *browse* to decide, split the list into two dependent fields
 
 ### H-47 Values hard-coded past the token layer
 ❌ A raw hex colour or pixel size written in component code
-✅ Reference the token. Consume the semantic role (`--color-text-strong`), not the primitive (`--color-neutral-900`). A value that cannot be expressed as a token indicates a missing token.
+✅ Reference the token. Consume the semantic role (`--color-text-strong`), not the primitive (`--color-neutral-900`). A value that cannot be expressed as a token is a missing token — or a value that should not exist at all. Check the second before minting the first.
+Deletion is a real answer and the easy one to miss, because the correction points at a token and an agent reading it literally invents one. Both times this rule fired on Jig's own documentation site the fix was removal: `font-size: 0.9em` on inline `code`, where the two faces share vertical metrics and inheriting is correct (`B-105`); and a `min-width` in `em` on a table column that `max-content` measures for free. A token minted to satisfy a detector entrenches the value it was invented for.
 
 ### H-48 JavaScript for something CSS does
 ❌ Scroll listeners for sticky positioning; scripted accordions and dialogs that have native equivalents

package/rules.index.json

@@ -49,7 +49,7 @@
     "bucket": "mechanical",
     "severity": "error",
     "detector": "hardcoded-value",
-    "fix": "token-substitute",
+    "fix": "token-substitute-or-remove",
     "since": "0.1.0"
   },
   {
@@ -187,6 +187,12 @@
     "severity": "note",
     "since": "0.1.0"
   },
+  {
+    "id": "B-105",
+    "bucket": "judgment",
+    "severity": "note",
+    "since": "0.9.0"
+  },
   {
     "id": "C-66",
     "bucket": "judgment",