jig-ui 0.26.0 → 0.26.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jig-ui",
-  "version": "0.26.0",
+  "version": "0.26.2",
   "description": "A design system for coding agents. 160 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/03-patterns.md

@@ -53,7 +53,16 @@ Four numbers, and most button designs in the wild fail at least one:
 | Button **shape** — fill or border — against its background | **3:1** |
 | Button **text** against the button | **4.5:1** |
 | Two buttons sharing a style, distinguished only by contrast | **3:1 between them** |
-| Hit area | `--size-touch-target` — **48×48px** floor |
+| Hit area | `--size-touch-target` — **48×48px** floor, except inside a table row (below) |
+
+**Inside a table row, a button takes the row's height.** A dense row is shorter
+than the floor, and a button given `min-height: var(--size-touch-target)` there
+stretches the rows that hold it and not the rest: an invoices table had its
+"Mark as paid" rows at 65px among 41px ones, twice. Size it to `--size-control`
+and never give it a minimum height of its own. On a touch screen the row itself
+rises to `--size-touch-target` (the mode files do it under a coarse pointer), so
+a finger still gets the floor. The render probe reports rows made uneven this
+way.
 
 A secondary button's fill or border is **not decorative**. It is the only thing identifying the element as a button, so it carries the 3:1 non-text requirement (`02-tokens.md`). Strip it and you have coloured text.
 
@@ -285,6 +294,7 @@ Primarily an `operator` pattern; the rules apply wherever a table appears.
 **Rules**
 - Row identity is stable across refresh, sort and filter. A row that moves under a click causes the wrong record to be acted on — the most damaging bug this pattern has.
 - Numeric columns are right-aligned and use tabular figures (`--font-numeric`). Text columns are start-aligned. Never centre either.
+- Every row is one height. A button or link in a row takes the row's height and has no minimum height of its own (see the Button pattern, Hit area).
 - A cell stays a table cell. To line up what is inside it (a name and a tag, an icon and a label), put `display: flex` on a wrapper inside the cell, never on the `<td>` or `<th>` itself: a cell given its own display stops taking its row's height, so its text and its border drift from the rest of the row. A table stacked on a phone, the whole table set to `block`, is the exception (`L-01`, step 6). The render probe reports a cell that has left its table.
 - Column headers state units. "Weight" is ambiguous; "Weight (kg)" is not.
 - Truncation is resolvable by click or expand, never by hover alone (`E-31`, `01-modes.md`).

package/templates/COMMAND.md.tmpl

@@ -78,12 +78,13 @@ came from, and the surfaces it used — the output says whether they came from
 `jig.config.json` or from the default.
 
 If the token layer does not exist yet, this is the command that creates it. **Do
-not author token values yourself.** `init` derives the brand colour, checks it
+not write the token files by hand.** `init` derives the brand colour, checks it
 against the contrast floor in both light and dark, and records a checksum for
 each file it writes; a file you write by hand is untracked, so `jig update` can
-never refresh it again. `jig check` now reads the token layer back and holds it
-to those floors either way, so a hand-written value will be caught — but caught
-late, and unmaintainable, is worse than derived.
+never refresh it again. The brand file it writes is the project's own, though:
+once `DECISIONS.md` records a colour, a typeface or corners, change those values
+in it to match (see `decide`). `jig check` reads the token layer back and holds it
+to those floors, so a value that fails one is caught however it got there.
 
 ## check
 
@@ -1973,6 +1974,18 @@ the user as left out on purpose, with the reason. Then go the other way: every
 and ask. A `Why (inferred):` traces to what it was inferred from; say what that was.
 Include this mapping in your message, below the file.
 
+**Then put the answers into the brand file.** The type, the colour and the
+corners each name the token they become, and the brand file `init` wrote is the
+project's own: `jig update` refreshes the mode files and never touches it. Change
+its values to match what the user decided: the brand hue, saturation and lightness
+for the colour, `--font-text` and `--font-display` for the type (and load the face
+wherever the pages load their styles, if it is a web font), and the `--radius-*`
+scale for the corners. A value the user did not decide stays as `init` wrote it.
+Then run `{{scripts_path}} check`: it holds the brand file to the contrast floors
+in light and dark, and says if a decided colour or typeface never reached it. Of
+six runs whose owner named a colour and a typeface, four recorded both in this file
+and built every page in Jig's unbranded default, because no step said to apply them.
+
 Show it and ask the user to confirm it is right before you stop. Leave no
 `[TODO]` markers — the gate treats them as an unwritten file, correctly, because
 a placeholder decision is not a decision.