@ericrisco/rsc 1.0.24 → 1.0.26

package/README.md

@@ -119,6 +119,11 @@ also wires a `SessionStart` hook (so your assistant proposes new skills on its
 own) and a `UserPromptSubmit` hook that re-asserts the **SDD new-feature gate**
 on every turn — so a feature request, in any language, routes through `specify`
 first, before any skill writes code. Opt out per project with `.rsc/.no-feature-gate`.
+It also wires a `PreToolUse` **gitmoji guard**: a `git commit` whose message carries no
+[gitmoji](https://gitmoji.dev) is denied, with the corrected message inside the refusal
+(`✨ feat(api): add cursor paging`) — so `git log --oneline` stays readable at a glance instead of
+depending on the agent remembering a convention. It only judges messages it can actually read
+(`-m`, heredoc), never an editor commit or `--amend --no-edit`. Opt out with `.rsc/.no-gitmoji`.
 
 Everything stays **in the project**, and the real skill files are written
 **once** to `.rsc/skills/<id>/`. Each assistant you pick gets a lightweight

package/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.24",
+  "version": "1.0.26",
   "counts": {
     "skills": 264
   },
@@ -2114,11 +2114,12 @@
     },
     {
       "id": "git-workflow",
-      "description": "Use when naming or scoping a branch, writing or fixing a commit message, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers Conventional Commits, SemVer tags, branch hygiene, force-push safety and gh pr/release mechanics. NOT the land-it decision and pre-ship checklist (that is `ship`), NOT an isolated checkout before coding (that is `worktrees`), NOT CI/CD release automation (that is `deployment`).",
+      "description": "Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene, force-push safety and gh pr/release mechanics. NOT the land-it decision and pre-ship checklist (that is `ship`), NOT an isolated checkout before coding (that is `worktrees`), NOT CI/CD release automation (that is `deployment`).",
       "tags": [
         "git",
         "version-control",
         "conventional-commits",
+        "gitmoji",
         "semver",
         "pull-request"
       ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ericrisco/rsc",
-  "version": "1.0.24",
+  "version": "1.0.26",
   "description": "Eric Risco's agent-skills catalog as a granular, self-recommending CLI installer.",
   "type": "module",
   "bin": {

package/scripts/doctor.js

@@ -57,6 +57,9 @@ export function doctor({ target, home, cwd }) {
     },
     contextBudget: contextBudget({ target, home, cwd }),
     sello: selloStatus(root),
+    // An inert gate must never read as an armed one (the same rule the sello follows):
+    // the gitmoji guard has a per-project kill switch, so say which state it is in.
+    gitmojiGuard: existsSync(join(root, '.rsc', '.no-gitmoji')) ? 'opted-out' : 'armed',
     // Counted, never interpreted — by spec, the gap log's reader is the user.
     automationGaps: countGaps(root),
   };

package/scripts/install-apply.js

@@ -60,6 +60,7 @@ function generatedHookFiles({ target, cwd }) {
     join(cwd, '.rsc', 'worklog-checkpoint.mjs'),
     join(cwd, '.rsc', 'ship-guard.mjs'),
     join(cwd, '.rsc', 'danger-guard.mjs'),
+    join(cwd, '.rsc', 'gitmoji-guard.mjs'),
     join(cwd, '.rsc', 'userprompt-gate.mjs'),
     join(cwd, '.rsc', 'hook-once.mjs'),
     join(cwd, '.rsc', 'sello.mjs'),

package/skills/constitution/references/constitution-template.md

@@ -40,7 +40,7 @@ version: v1.0.0
 
 7. Naming & structure: <directory layout, module boundaries, file naming>.
 8. API & errors: <error shape, status codes, response envelope> where applicable.
-9. Commit messages: <format, e.g. Conventional Commits>.
+9. Commit messages: <format, e.g. gitmoji + Conventional Commits — `✨ feat(scope): subject`>.
 
 ## 4. Branching & shipping
 

package/skills/design/SKILL.md

@@ -234,6 +234,36 @@ img  { outline: 1px solid oklch(0 0 0 / 0.1); outline-offset: -1px; }
 
 Depth recipes, glass, noise, concentric math → `references/visual-system.md`.
 
+## The three locks, and who checks them
+
+A long page generated in passes drifts against itself. Three things must be **one** thing for
+the whole page, and they are not preferences — a page that breaks one of them is defective:
+
+1. **Theme lock.** One theme for the page (light, dark, or auto). No section flipping to
+   inverted halfway down because it looked good alone.
+2. **Accent lock.** One accent, used identically in every section. **This one is judgement**:
+   deciding which token is the accent needs to read the system's intent, so no script claims
+   to check it — you do, before you claim done.
+3. **Radius lock.** One radius system. Four different `rounded-*` scales in one tree means
+   there is no system, and `scripts/verify.sh` counts them.
+
+## The tells the script owns, and the ones you own
+
+`scripts/verify.sh` carries a **registry of mechanical tells** and reports each with file and
+line: dashes in rendered copy, scroll cues, numbered eyebrows, build stamps on marketing
+pages, unstable viewport heights, middot chains, hype words, plus counted ratios (eyebrows
+against sections, double-bordered rows, radius scales). Run it; do not re-derive that list
+from memory, and do not treat its silence as a design review.
+
+What it cannot see is the other half: fabricated substance (a product UI built from divs,
+invented photo credits, the Jane Doe cast), decoration posing as information, labels that say
+nothing, and composition habits like three identical feature cards. That half is
+`references/ai-tells.md`, and it is read with your eyes on the page.
+
+When the brief corresponds to an official, maintained design system rather than an aesthetic —
+UK or US public sector, Shopify admin, Carbon, Atlassian, Primer, Fluent — install the
+official package instead of approximating it: `references/design-systems.md`.
+
 ## Anti-patterns
 
 | Rationalization | Reality / Fix |
@@ -314,6 +344,6 @@ Score = Σ(dimension × weight), max 115 (normalize to /100 by ×100/115 if you
 Two records, both indexed in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer to it), both read first on every use so outputs stay consistent with them:
 
 - The **brand study** at `02-DOCS/wiki/brand/` — the hard gate above: missing or incomplete → ask until complete before designing.
-- The **design-system decisions** at `02-DOCS/wiki/stack/design.md` — the chosen tokens (color/OKLCH, type scale, spacing, radius, shadow, motion), the 2026 direction picked, and the reference sites. Recorded, not gated; create/update it as decisions are made.
+- The **design-system decisions** at `02-DOCS/wiki/stack/design.md` — the chosen tokens (color/OKLCH, type scale, spacing, radius, shadow, motion), the 2026 direction picked, and the reference sites. Recorded, not gated; create/update it as decisions are made. **Read it before fixing type and palette on a new surface**, and either reuse what is there or state why you are departing — otherwise every surface of the project drifts into a different design. (Across *different* projects this record cannot help: it lives inside each one. Distrusting your own second default is the only guard there — see the repetition note in `references/ai-tells.md`.)
 
 The wiki article protocol both follow is `../harness/SKILL.md`'s.

package/skills/design/evals/cases.yaml

@@ -49,7 +49,7 @@ capability:
   - scenario: "User asks: 'Here's our current pricing page — do a design review and tell me how good it actually is.'"
     must_include:
       - "Applies the design-review QA checklist (value prop in 5s, contrast >= 4.5:1, visible focus, one <h1>, semantic landmarks, LCP image priority, next/font, no transition: all, tokens not magic numbers, ban-list-clean copy, 360px fit, empty/loading/error states)."
-      - "Scores the 10-dimension visual-audit rubric 0-10 with weights and reports a weighted total out of 100, mapped to a band (<60 generic / 60-79 competent / 80-94 premium / 95+ award-tier)."
+      - "Scores the 11-dimension visual-audit rubric 0-10 with weights and reports the weighted total on its /115 scale, mapped to a band (<69 generic / 69-91 competent / 92-108 premium / 109+ award-tier)."
       - "For each dimension scoring below 8, gives a concrete actionable fix (e.g. exact spacing/token change), not a vague 'improve spacing'."
       - "Checks copy against the ban-list and flags hype/vague value props that fail the 5s test."
       - "Flags any transition: all, magic hex/px, cards-in-cards, or purple->blue everything gradient as defects, not preferences."

package/skills/design/references/ai-tells.md

@@ -0,0 +1,75 @@
+# AI tells — the ones only a reader can catch
+
+The mechanical tells are **not here**. `scripts/verify.sh` carries a registry of them and
+flags them with file and line, so re-teaching them as prose would be paying twice for the
+same rule. This file holds only what a `grep` cannot decide: presences you have to *look* at
+the page to see.
+
+Part of this corpus is adapted from [Leonxlnx/taste-skill](https://github.com/Leonxlnx/taste-skill)
+(MIT), whose lists came out of real production tests. The split into checkable-vs-judged, the
+thresholds, and the wording are ours.
+
+Every item below is a **default**, overridable by a brief that explicitly asks for it. What
+makes them tells is that they show up *unasked*, as the model's idea of "looking designed".
+
+## Fabricated substance
+
+- **A product UI built out of divs.** A fake task list, fake terminal or fake dashboard
+  assembled from styled rectangles is the single most reliable signature of generated work.
+  Use a real screenshot, a real component, a generated image, or show nothing.
+- **Hand-rolled decorative SVG.** Abstract squiggles and blobs authored inline to fill space.
+  Icons come from a maintained set; decoration comes from a real asset or not at all.
+- **The Jane Doe cast.** "John Doe", "Sarah Chan", egg avatars, `99.99%`, `50%`, round
+  thousands, and startup-slop brand names ("Acme", "Nexus", "SmartFlow"). Real work has
+  specific, slightly awkward names and messy numbers (`47.2%`, not `50%`).
+- **Testimonials nobody said.** A quote with no attributable person, or five quotes with the
+  same cadence, reads as filler. One real quote beats three invented ones.
+
+## Decoration wearing the costume of information
+
+- **Atmospheric locale strips.** A city, a timezone, a temperature in the nav or footer. Only
+  earns its place for a genuinely distributed studio, a travel brand, or a physical venue.
+- **Status dots with no status.** A coloured dot before nav items, list rows or badges. Keep
+  it only where it reports real state, and then only once per section.
+- **Invented photo credits.** `Field study no. 12 · Ines Caetano` under a stock image.
+  Credit a real photographer or write a functional caption.
+- **Pills laid over images.** Tags floated on top of a photo. Either the image speaks alone,
+  or the caption sits below it, outside the frame.
+- **Decoration strips under the hero.** `BRAND. MOTION. SPATIAL.` in small mono caps. Only
+  legitimate when those words are real navigation or real status.
+
+## Labels that say nothing
+
+- **Poetic section labels.** "Field notes", "From the field", "On our desks", "Currently on
+  the bench". Use the functional name ("Testimonials", "Latest writing") or no label.
+- **Generic step labels.** "Stage 1 / Stage 2", "Phase 01 / 02". The step content *is* the
+  label: "Install", "Configure", "Ship".
+- **Mock-humble asides** and micro-meta sentences under a heading ("The list will stay short
+  on purpose"). Eyebrow, headline, body. Nothing else.
+- **"Quietly trusted by".** Say "Used at", "Customers include", or let the logos speak.
+
+## Composition habits
+
+- **Three identical feature cards.** The default feature row. Reach for a two-column zig-zag,
+  an asymmetric grid, or a horizontal rail instead — and do not run the same split three
+  sections in a row.
+- **The corner floater.** A giant left-aligned headline with a small explainer paragraph
+  floating in the section's top-right, aligned to nothing. Stack it, or build a real
+  two-column header.
+- **Rotated vertical text** and crosshair grid lines drawn only to look designed. Both are
+  agency-portfolio clichés unless they organise real content.
+- **A bento with empty cells.** N items means N cells, and at least two cells need real
+  visual variation — otherwise it is a white card grid with extra steps.
+
+## The second default (repetition)
+
+Obeying every rule produces correct pages that all look the same. Before fixing type and
+palette, read the project's recorded design decisions and either reuse them deliberately or
+say why you are departing. Two specific defaults to distrust: reaching for the same display
+serif again, and answering every premium-consumer brief with the beige/brass/oxblood family.
+
+## Surface treatments to distrust by default
+
+Outer glows and neon; pure `#000000` (use an off-black); oversaturated accents that refuse to
+sit with the neutrals; gradient fills on large headings; custom cursors (outdated, hostile to
+accessibility and to performance); glass on every surface rather than on floating ones.

package/skills/design/references/design-systems.md

@@ -0,0 +1,41 @@
+# When the brief is a design system, not an aesthetic
+
+This skill's default is Tailwind v4 + Next.js, and for most briefs that is right. But some
+briefs correspond to a **maintained, official design system**, and there the correct answer is
+to install it. Recreating its CSS by hand produces something that looks like it, fails its
+accessibility work, and drifts on its next release.
+
+The list is deliberately short: only the cases where using the official package is
+**obligatory or strongly expected**, and where the default instinct would be to hand-roll it.
+Free choices (Bootstrap, Material for a non-Google product, Radix Themes, shadcn/ui) are not
+here — they are ordinary picks, and shadcn/ui in particular is already this skill's territory,
+where the rule is simply never to ship it in its default state.
+
+| The brief reads as | Install | Why it is not a choice |
+| --- | --- | --- |
+| A UK public-sector service | `govuk-frontend` | Expected by the Service Standard; deviating is a finding at assessment |
+| A US federal or trust-first public service | `uswds` | Same, under the US Web Design System |
+| A Shopify admin surface or embedded app | `@shopify/polaris` (or Polaris web components) | Required for admin UI to be accepted |
+| IBM-flavoured enterprise or dense analytics | `@carbon/react` + `@carbon/styles` | Mature data-density patterns you will otherwise reinvent badly |
+| An Atlassian / Jira-adjacent product surface | `@atlaskit/*` + `@atlaskit/tokens` | Official DS; token-driven theming |
+| A GitHub-style devtool or community page | `@primer/css`, or `@primer/react-brand` for marketing | Official Primer; the Brand variant is the marketing half |
+| A Microsoft / Fluent-flavoured product | `@fluentui/react-components` | Official Fluent, Microsoft tokens, accessibility already done |
+
+## The three rules that come with them
+
+1. **Do not recreate it.** If the brief names one of these, install the package. Importing its
+   tokens and then overriding ninety percent of them is the same mistake with extra steps.
+2. **One system per project.** No Fluent components inside a Carbon tree, no shadcn/ui
+   dropped into a Material app. Mixing two systems produces a third, worse one.
+3. **Name what is an approximation.** When the brief is an *aesthetic* rather than a system —
+   glassmorphism, bento tiles, brutalism, editorial, aurora gradients, kinetic type — there is
+   no official package, and saying so is part of the work. Apple's Liquid Glass is documented
+   for Apple platforms only: there is no official web implementation, so a web version is a
+   `backdrop-filter` approximation and must be labelled as one, in the code and to the user.
+
+## What still applies
+
+Everything in `../SKILL.md` that is not styling: the brand gate, the accessibility floor,
+the Core Web Vitals budget, the 5-second value-prop test, and the tell registry in
+`../scripts/verify.sh`. An official design system settles which components you use. It does
+not settle whether the page says anything.

package/skills/design/references/motion-and-interaction.md

@@ -174,6 +174,41 @@ export function Toast({ open, message }: { open: boolean; message: string }) {
 
 Once you are in `motion/react`, defer the mechanics (spring config, variants, `layoutId` shared transitions) to the external *motion-foundations* and *motion-ui* references.
 
+## Escalating past the native path
+
+Native `animation-timeline: view()` covers reveals, progress rails and parallax. Two effects it
+cannot express are **pinning** (a section holds still while its content advances) and a
+**horizontal pan** driven by vertical scroll. Those need a scroll library, and the improvised
+version is always wrong in the same three ways. Escalate deliberately:
+
+**Never listen to scroll directly.** `window.addEventListener('scroll')` fires off the main
+thread's budget, blows INP, and never gets a passive-listener or cleanup story right. The
+allowed inputs are `IntersectionObserver`, a scroll-driven CSS timeline, `useScroll()` from
+`motion/react`, or GSAP's ScrollTrigger. Nothing else.
+
+**Sticky stack** (pin a section, advance its layers):
+
+```ts
+// 'use client' leaf only. One trigger per pinned section, killed on unmount.
+const st = ScrollTrigger.create({
+  trigger: sectionRef.current,
+  start: "top top",          // pin the moment the section's top reaches the viewport top
+  end: () => `+=${panels.length * window.innerHeight}`,
+  pin: true,
+  pinSpacing: true,          // without this the next section slides under the pin
+  scrub: 1,                  // 1 = follow scroll with a 1s catch-up, not a hard 1:1 jump
+  invalidateOnRefresh: true, // recompute on resize, or the end point is stale on rotate
+});
+// cleanup is not optional: return () => st.kill();
+```
+
+**Horizontal pan** is the same trigger with `end: () => "+=" + track.scrollWidth` and the
+track moved via `x`, not `left` — `transform` is compositor-only, `left` triggers layout.
+
+Both are opt-in above a motion budget, both stay inside
+`@media (prefers-reduced-motion: no-preference)`, and both collapse to a plain vertical stack
+below `768px` rather than pinning on a phone.
+
 ## See Also
 
 - `visual-system.md` — the easing and duration tokens these animations consume.

package/skills/design/scripts/verify.sh

@@ -7,9 +7,17 @@
 #      performance + accessibility audit and checks Core Web Vitals against the
 #      skill's hard thresholds (LCP < 2.5s, CLS < 0.1, INP proxy via TBT < 200ms,
 #      a11y score >= 0.9).
-#   2. Always runs static, network-free design-review grep checks (one <h1>,
-#      no `transition: all`, hardcoded hex vs tokens, missing image alt, missing
-#      prefers-reduced-motion, marketing ban-list words).
+#   2. Always runs static, network-free design-review checks, in three groups:
+#      - four judgement-shaped ones (more than one <h1>, image without alt,
+#        hardcoded hex despite a token system, animation with no reduced-motion
+#        guard) — see static_checks();
+#      - the tell registry: one row per checkable AI tell, iterated generically
+#        (dashes in rendered copy, scroll cues, numbered eyebrows, build stamps,
+#        unstable viewport heights, middot chains, transition-all, hype words)
+#        — see tell_table(); every row has a fixture in the repo's test suite;
+#      - three counters that need a ratio rather than a match (eyebrows against
+#        sections, double-bordered rows, radius scales) — see counter_checks().
+#      Everything here WARNS. Nothing here fails, unless --strict is passed.
 #   3. If Lighthouse did not run, prints the manual QA checklist. For a graded
 #      0-10 critique, use the visual-audit rubric in SKILL.md instead.
 #
@@ -78,7 +86,10 @@ have() { command -v "$1" >/dev/null 2>&1; }
 SELF_NAME="$(basename "$0")"
 search() {
   [ "$#" -gt 0 ] || return 1
-  if have rg; then
+  # VERIFY_FORCE_GREP=1 pins the grep branch. It exists so the test suite can prove BOTH
+  # engines agree on the multibyte patterns (em-dash, middot) on any machine, instead of
+  # only exercising whichever one happens to be installed.
+  if have rg && [ -z "${VERIFY_FORCE_GREP:-}" ]; then
     # rg already ignores .gitignore'd paths (node_modules, .next, dist); also skip self.
     rg -n --no-heading --glob "!$SELF_NAME" "$@"
   else
@@ -165,6 +176,102 @@ run_lighthouse() {
   fi
 }
 
+# --- the tell registry ------------------------------------------------------
+# One row per checkable AI tell. A row is DATA, not code, so the test suite can enumerate
+# every row and demand a fixture for each: a check nobody has ever seen fire cannot ship.
+# Add a tell by adding a row plus tests/fixtures/design-tells/tells/<id>.tsx — nothing else.
+#
+# Columns, delimited by %% (the pattern column needs `|` for ERE alternation):
+#   id %% sev %% extensions %% POSIX-ERE pattern %% what to do instead / the legit exception
+#
+# Patterns are POSIX ERE: no lookahead, no \b, no \s — they must behave identically under rg
+# and under grep -E. Part of the corpus is adapted from Leonxlnx/taste-skill (MIT).
+tell_table() {
+  cat <<'TELLS'
+em-dash%%warn%%tsx,jsx,html,vue,svelte,mdx%%—|–%%em-dash or en-dash in rendered copy is the loudest AI tell. Use a period, a comma, a colon or parentheses instead
+scroll-cue%%warn%%tsx,jsx,html,vue,svelte%%[Ss]croll to (explore|walk|discover|see|begin)|↓ *[Ss]croll%%a scroll cue explains scrolling to someone already looking at the hero. Delete it, or use a real anchor link instead
+numbered-eyebrow%%warn%%tsx,jsx,html,vue,svelte%%(^|[^0-9A-Za-z])[0-9]{2,3} +(·|/) +[A-Za-z]%%numbered section eyebrow (001 · Capabilities). Name the topic in plain language instead
+version-stamp%%warn%%tsx,jsx,html,vue,svelte%%v[0-9]+\.[0-9]+\.[0-9]+|Build [0-9]{3,4}%%a build or version stamp is devtool furniture on a marketing page. Delete it. Legitimate exception: a real devtool footer, a changelog or a release page
+viewport-unit%%warn%%tsx,jsx,html,vue,svelte,css%%h-screen%%h-screen jumps when mobile browser chrome slides away. Use min-h-[100dvh] instead
+middot-chain%%warn%%tsx,jsx,html,vue,svelte%%·[^·]*·%%more than one middot on a line is decoration pretending to be metadata. Use line breaks, columns or a hairline instead
+transition-all%%warn%%tsx,jsx,css,html,vue,svelte%%transition:[[:space:]]*all|transition-all%%transition-all animates layout properties and janks. List the exact properties instead
+ban-list%%warn%%tsx,jsx,html,md,mdx%%revolutionary|game-?changer|cutting-edge|supercharge|seamless|unlock%%hype words carry no value prop. Use the concrete benefit and a real number instead
+TELLS
+}
+
+run_tell_table() {
+  local line id sev globs pat msg hits exts rest
+  # NOT `IFS='%%'`: IFS is a set of characters, so it would split on a single `%` and put an
+  # empty field between every pair. Parameter expansion splits on the two-character
+  # delimiter exactly, which is what the pattern column needs to keep its ERE `|`.
+  while IFS= read -r line; do
+    case "$line" in ''|'#'*) continue ;; esac
+    id="${line%%"%%"*}";    rest="${line#*"%%"}"
+    sev="${rest%%"%%"*}";   rest="${rest#*"%%"}"
+    globs="${rest%%"%%"*}"; rest="${rest#*"%%"}"
+    pat="${rest%%"%%"*}";   msg="${rest#*"%%"}"
+    exts="${globs//,/|}"
+    # Two post-filters, both learned from a real run over this repo:
+    #   1. keep only the extensions the row declares (anchored before the first colon, so it
+    #      behaves the same under rg and grep and never matches content that names a file);
+    #   2. drop lines whose match sits in a code comment. A dash in `/* tokens — lifted */`
+    #      is not rendered copy, and flagging it trains the reader to ignore the tool.
+    hits="$(search "$pat" 2>/dev/null \
+      | grep -E "^[^:]*\.($exts):" \
+      | grep -vE "^[^:]*:[0-9]+:[[:space:]]*(//|/\*|\*[^a-zA-Z]|#|<!--|\{/\*)" || true)"
+    if [ -n "$hits" ]; then
+      # The sev column is real, not decoration: anything other than `warn` breaks the build.
+      case "$sev" in
+        warn) warn "$id: $msg" ;;
+        *)    fail "$id: $msg" ;;
+      esac
+      printf '%s\n' "$hits" | head -n 5
+    fi
+  done <<EOF
+$(tell_table)
+EOF
+}
+
+# --- counters: the tells that are a ratio or a repetition, not a pattern -----
+# These cannot be table rows because one match proves nothing — it takes a count. Each one
+# carries its own named test instead of riding the generic row mechanism.
+counter_checks() {
+  local eyebrows sections ceiling hits variants v
+
+  # Eyebrow ceiling. Threshold ceil(sections/3) is BORROWED from taste-skill and has never
+  # been calibrated against a page of ours — the warning says so rather than implying rigour.
+  eyebrows="$(search 'uppercase[^"]*tracking|tracking[^"]*uppercase' 2>/dev/null | grep -cE '^[^:]*\.(tsx|jsx|html|vue|svelte):' || true)"
+  sections="$(search '<section' 2>/dev/null | grep -cE '^[^:]*\.(tsx|jsx|html|vue|svelte):' || true)"
+  [ -z "$eyebrows" ] && eyebrows=0
+  [ -z "$sections" ] && sections=0
+  if [ "$sections" -eq 0 ]; then
+    if [ "$eyebrows" -gt 0 ]; then
+      skip "eyebrow ceiling: no <section> found, so there is no denominator — not guessing one"
+    fi
+  else
+    ceiling=$(( (sections + 2) / 3 ))
+    if [ "$eyebrows" -gt "$ceiling" ]; then
+      warn "eyebrow count $eyebrows exceeds the ceiling $ceiling for $sections sections (uncalibrated threshold, borrowed): drop the uppercase micro-labels, or let the headline carry it instead"
+    fi
+  fi
+
+  # A hairline above AND below every row of a long list is the laziest possible layout.
+  hits="$(search 'border-t[^"]*border-b|border-b[^"]*border-t' 2>/dev/null | grep -cE '^[^:]*\.(tsx|jsx|html|vue|svelte):' || true)"
+  [ -z "$hits" ] && hits=0
+  if [ "$hits" -gt 3 ]; then
+    warn "double border on $hits list rows: pick one edge, or use spacing instead of hairlines"
+  fi
+
+  # More than two radius scales in one tree means no radius system at all.
+  variants=0
+  for v in none sm md lg xl 2xl 3xl full; do
+    if search "rounded-$v" >/dev/null 2>&1; then variants=$((variants + 1)); fi
+  done
+  if [ "$variants" -gt 2 ]; then
+    warn "$variants different radius scales in use: one radius system per project — use a --radius-* token instead"
+  fi
+}
+
 # --- static design-review checks (always run, no network) -------------------
 static_checks() {
   local hits
@@ -182,9 +289,8 @@ static_checks() {
     done < <(grep -rl --exclude-dir=node_modules --exclude-dir=.git --exclude-dir=.next '<h1' . 2>/dev/null || true)
   fi
 
-  # 2. transition: all / transition-all  ([[:space:]] is POSIX; \s is not portable in ERE)
-  hits="$(search 'transition:[[:space:]]*all|transition-all' 2>/dev/null || true)"
-  if [ -n "$hits" ]; then warn "transition: all / transition-all found:"; printf '%s\n' "$hits" | head -n 5; fi
+  # 2. (moved) `transition: all` is now a row in tell_table() — it is a plain pattern, so it
+  #    gets the generic mechanism and its fixture for free.
 
   # 3. hardcoded hex when a token system exists (\b is not portable in ERE; a
   #    3-8 char hex run after # is a sufficient heuristic without the boundary).
@@ -209,9 +315,7 @@ static_checks() {
     fi
   fi
 
-  # 6. ban-list marketing words in copy
-  hits="$(search 'revolutionary|game-?changer|cutting-edge|supercharge|seamless|unlock' 2>/dev/null | grep -iE '\.(tsx|jsx|html|md|mdx)' || true)"
-  if [ -n "$hits" ]; then warn "ban-list marketing words found in copy:"; printf '%s\n' "$hits" | head -n 5; fi
+  # 6. (moved) the marketing ban-list is now a row in tell_table(), same reason as #2.
 }
 
 # --- fallback manual checklist ----------------------------------------------
@@ -239,6 +343,8 @@ EOF
 # --- run --------------------------------------------------------------------
 run_lighthouse
 static_checks
+run_tell_table
+counter_checks
 [ "$LH_RAN" -eq 0 ] && print_checklist
 
 printf '\nok=%d skip=%d warn=%d fail=%d\n' "$ok_count" "$skip_count" "$warn_count" "$fail_count"

package/skills/git-workflow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: git-workflow
-description: "Use when naming or scoping a branch, writing or fixing a commit message, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers Conventional Commits, SemVer tags, branch hygiene, force-push safety and gh pr/release mechanics. NOT the land-it decision and pre-ship checklist (that is `ship`), NOT an isolated checkout before coding (that is `worktrees`), NOT CI/CD release automation (that is `deployment`)."
-tags: [git, version-control, conventional-commits, semver, pull-request]
+description: "Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene, force-push safety and gh pr/release mechanics. NOT the land-it decision and pre-ship checklist (that is `ship`), NOT an isolated checkout before coding (that is `worktrees`), NOT CI/CD release automation (that is `deployment`)."
+tags: [git, version-control, conventional-commits, gitmoji, semver, pull-request]
 recommends: [ship, worktrees, deployment, github-actions]
 origin: risco
 ---
@@ -44,12 +44,12 @@ Good  fix/expired-refresh-token-401
 Good  chore/bump-node-22
 ```
 
-## Conventional Commits grammar
+## Commit grammar — gitmoji + Conventional Commits
 
-Write every commit to **Conventional Commits 1.0.0**. The structure:
+Write every commit to **Conventional Commits 1.0.0**, opened by a **gitmoji**. The structure:
 
 ```text
-type(scope)!: subject
+<gitmoji> type(scope)!: subject
 
 body — what changed and why, wrapped, optional
 
@@ -57,6 +57,8 @@ BREAKING CHANGE: description of the incompatible change
 Fixes #123
 ```
 
+- The **gitmoji is mandatory** and comes first — the intention of the change, readable in one glyph
+  when you scan `git log --oneline`. `type` is what tooling reads; the emoji is what humans read.
 - `type` is mandatory. `scope` in parentheses is optional. `!` before the colon marks a breaking change.
 - Subject: imperative mood ("add", not "added"/"adds"), ≤72 chars, no trailing period.
 - Body explains *why*, not *what the diff already shows*. Separate from subject by a blank line.
@@ -74,23 +76,44 @@ Type → SemVer effect:
 `BREAKING CHANGE` **must be uppercase** in the footer; the type/scope units are case-insensitive but
 write them lowercase by convention.
 
+Type → gitmoji, the everyday set (the full 75-emoji table, and *why* the emoji never replaces the
+type, are in **`references/gitmoji.md`**):
+
+| Type       | gitmoji | Type       | gitmoji | Type      | gitmoji |
+|------------|---------|------------|---------|-----------|---------|
+| `feat`     | ✨      | `refactor` | ♻️      | `build`   | 📦️      |
+| `fix`      | 🐛      | `test`     | ✅      | `style`   | 🎨      |
+| `docs`     | 📝      | `perf`     | ⚡️      | `revert`  | ⏪️      |
+| `chore`    | 🔧      | `ci`       | 👷      | breaking  | 💥      |
+
+Pick by **intention**, not by which file changed, and prefer the specific one: 🚑️ for a production
+hotfix, 🩹 for a trivial non-critical fix, 🔥 for a deletion, 🚚 for a rename, ⬆️ for a dep bump,
+🔖 for a release commit.
+
 ```text
 Bad   fix stuff
 Bad   updates
 Bad   Fixed the login bug.            (past tense, capitalized, trailing period)
-Good  fix(auth): reject expired refresh tokens
-Good  feat(api): add /v2/search endpoint with cursor paging
-Good  refactor(parser): extract token scanner, no behavior change
+Bad   fix(auth): reject expired refresh tokens        (no gitmoji)
+Bad   ✨ added a search endpoint                       (gitmoji but no type → no derivable bump)
+Good  🐛 fix(auth): reject expired refresh tokens
+Good  ✨ feat(api): add /v2/search endpoint with cursor paging
+Good  ♻️ refactor(parser): extract token scanner, no behavior change
 ```
 
 A breaking change, both forms equivalent:
 
 ```text
-feat(api)!: drop the legacy /v1 search endpoint
+💥 feat(api)!: drop the legacy /v1 search endpoint
 
 BREAKING CHANGE: /v1/search is removed; callers must migrate to /v2/search.
 ```
 
+If the repo runs a **strict** conventional parser (commitlint, semantic-release) it anchors the type
+at position 0 and rejects the emoji prefix. Either widen its `headerPattern` — the config is in
+`references/gitmoji.md` — or move the emoji behind the header (`feat(api): ✨ add cursor paging`),
+which every parser accepts. Both forms satisfy this convention; dropping the gitmoji does not.
+
 **Authorship is always Eric.** Never add a `Co-Authored-By: Claude` trailer, never a
 "Generated with" footer, never any line crediting an AI tool — in a commit *or* a PR body. The work
 is Eric's; the agent is a tool, like the compiler.
@@ -103,7 +126,7 @@ Decide by who else has the commits. The lease rule below is non-negotiable.
 |------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------|
 | Private branch, only you have it, want linear history | `git rebase main`, then `git push --force-with-lease`| rebase rewrites hashes; safe because nobody built on them  |
 | Branch others have pulled / built on                  | `git merge main` — **never** rebase it               | rebase changes every hash; collaborators' work diverges    |
-| Noisy PR (many `wip` commits)                         | squash-merge into one conventional commit            | `main` gets one meaningful entry, not 9 scratch commits    |
+| Noisy PR (many `wip` commits)                         | squash-merge into one gitmoji + conventional commit            | `main` gets one meaningful entry, not 9 scratch commits    |
 | Already pushed, shared, *and* you rewrote it          | **STOP** — coordinate, or `git revert` instead       | force-pushing shared history breaks everyone downstream     |
 
 After a rebase, push with `--force-with-lease`, never bare `--force`:
@@ -168,7 +191,8 @@ enough to hand over. Setting up the isolated checkout *before* you start coding
 | Anti-pattern                                          | Why it hurts                                              | Instead                                              |
 |-------------------------------------------------------|-----------------------------------------------------------|------------------------------------------------------|
 | `git push --force` on a shared branch                 | silently erases teammates' commits                        | `--force-with-lease`, or don't rewrite shared history |
-| `git commit -m "wip"` / `"fix"` / `"updates"`         | the log carries zero signal for the next reader           | conventional `type(scope): imperative subject`        |
+| `git commit -m "wip"` / `"fix"` / `"updates"`         | the log carries zero signal for the next reader           | `<gitmoji> type(scope): imperative subject`           |
+| Commit message with no gitmoji                         | `git log --oneline` reads as a wall of undifferentiated text | pick the intention's emoji (`references/gitmoji.md`) |
 | Mixing unrelated changes in one commit                | can't revert or review one concern in isolation           | one logical change per commit                         |
 | Long-lived branch (weeks)                             | diverges from `main`, merge becomes a battle              | short-lived; rebase or merge `main` in often          |
 | Hand-computing the semver bump                        | breaking change shipped as a MINOR → broken downstream    | derive the bump from the commit log                   |
@@ -183,7 +207,7 @@ enough to hand over. Setting up the isolated checkout *before* you start coding
 
 - [ ] Working tree clean (`git status`), no stray or generated files staged.
 - [ ] Branch rebased on / merged with current `main`; no avoidable conflicts.
-- [ ] Every commit is conventional; `wip`/scratch commits squashed away.
+- [ ] Every commit carries its gitmoji **and** a conventional header; `wip`/scratch commits squashed away.
 - [ ] No secrets, no AI-attribution trailers.
 - [ ] PR body explains the why and links the issue (`Fixes #`).
 - [ ] (Release) version bump **derived from the commit log**, tag is `vX.Y.Z`, annotated.

package/skills/git-workflow/evals/cases.yaml

@@ -13,6 +13,10 @@ should_trigger:
     why: Spanish trigger covering history cleanup plus conventional-commit formatting.
   - prompt: "Name a branch for the OAuth PKCE work"
     why: Branch-naming convention — feat/ prefix plus kebab slug from intent.
+  - prompt: "Which gitmoji goes on this commit — I deleted a deprecated module"
+    why: Gitmoji selection by intention (🔥 remove code, not ♻️ refactor); the commit-grammar layer owns the emoji.
+  - prompt: "Mi commitlint rechaza el commit por el emoji delante del type"
+    why: Spanish; the strict-parser escape hatch (widen headerPattern or move the emoji behind the header) lives in this skill.
   - prompt: "Tag v2.1.0 and write the release notes"
     why: Release mechanics — annotated tag plus gh release create --generate-notes.
 
@@ -41,6 +45,7 @@ capability:
     must_include:
       - Collapses the two "wip" commits via squash or fixup and explains why (one meaningful entry in main).
       - Identifies a feat commit and a BREAKING CHANGE footer written in uppercase.
+      - Every proposed commit message opens with a gitmoji (✨ for the feature, 💥 for the breaking removal) before the conventional header.
       - Bump is MAJOR because of the breaking change, with a tag of the form vX.0.0.
       - Uses gh release create vX.0.0 --generate-notes (or an equivalent that produces notes).
       - Uses git push --force-with-lease (not bare --force) for the post-rebase push.

package/skills/git-workflow/references/gitmoji.md

@@ -0,0 +1,157 @@
+# gitmoji — the full set, and the tooling that has to accept it
+
+The commit rule lives in `../SKILL.md`: **every commit opens with a gitmoji, then the
+Conventional Commits header.** This file is the lookup table and the tooling escape hatches — read
+it when you need the right glyph for an intention, or when a parser in the repo rejects the format.
+
+```text
+<gitmoji> type(scope)!: imperative subject
+```
+
+The gitmoji says *what kind of intention* this is at a glance in `git log --oneline`; the `type`
+still drives the SemVer bump. They are two different jobs and neither replaces the other — a commit
+with 💥 but no `!`/`BREAKING CHANGE:` footer still releases as a MINOR, because tooling reads the
+type, not the picture.
+
+## Picking one
+
+Match the **intention**, not the file that changed. If two fit, take the more specific one (🚑️ over
+🐛 for a production hotfix; 🩹 over 🐛 for a trivial non-critical fix). The `semver` column is
+gitmoji's own hint, not a substitute for the type → bump table in `../SKILL.md`.
+
+The everyday dozen, mapped to the conventional types:
+
+| Type       | gitmoji | Type        | gitmoji |
+|------------|---------|-------------|---------|
+| `feat`     | ✨      | `perf`      | ⚡️      |
+| `fix`      | 🐛      | `ci`        | 👷      |
+| `docs`     | 📝      | `build`     | 📦️      |
+| `refactor` | ♻️      | `style`     | 🎨      |
+| `test`     | ✅      | `revert`    | ⏪️      |
+| `chore`    | 🔧      | breaking    | 💥      |
+
+## The full set
+
+Canonical source: <https://gitmoji.dev> (machine-readable at `https://gitmoji.dev/api/gitmojis`).
+The same 75 rows are enforced as data by the gitmoji guard, and a test compares this table against
+it — if the two ever disagree, CI says so.
+
+| Emoji | Code | SemVer | Intention |
+|-------|------|--------|-----------|
+| 🎨 | `:art:` | — | Improve structure / format of the code |
+| ⚡️ | `:zap:` | patch | Improve performance |
+| 🔥 | `:fire:` | — | Remove code or files |
+| 🐛 | `:bug:` | patch | Fix a bug |
+| 🚑️ | `:ambulance:` | patch | Critical hotfix |
+| ✨ | `:sparkles:` | minor | Introduce new features |
+| 📝 | `:memo:` | — | Add or update documentation |
+| 🚀 | `:rocket:` | — | Deploy stuff |
+| 💄 | `:lipstick:` | patch | Add or update the UI and style files |
+| 🎉 | `:tada:` | — | Begin a project |
+| ✅ | `:white_check_mark:` | — | Add, update, or pass tests |
+| 🔒️ | `:lock:` | patch | Fix security or privacy issues |
+| 🔐 | `:closed_lock_with_key:` | — | Add or update secrets |
+| 🔖 | `:bookmark:` | — | Release / Version tags |
+| 🚨 | `:rotating_light:` | — | Fix compiler / linter warnings |
+| 🚧 | `:construction:` | — | Work in progress |
+| 💚 | `:green_heart:` | — | Fix CI Build |
+| ⬇️ | `:arrow_down:` | patch | Downgrade dependencies |
+| ⬆️ | `:arrow_up:` | patch | Upgrade dependencies |
+| 📌 | `:pushpin:` | patch | Pin dependencies to specific versions |
+| 👷 | `:construction_worker:` | — | Add or update CI build system |
+| 📈 | `:chart_with_upwards_trend:` | patch | Add or update analytics or track code |
+| ♻️ | `:recycle:` | — | Refactor code |
+| ➕ | `:heavy_plus_sign:` | patch | Add a dependency |
+| ➖ | `:heavy_minus_sign:` | patch | Remove a dependency |
+| 🔧 | `:wrench:` | patch | Add or update configuration files |
+| 🔨 | `:hammer:` | — | Add or update development scripts |
+| 🌐 | `:globe_with_meridians:` | patch | Internationalization and localization |
+| ✏️ | `:pencil2:` | patch | Fix typos |
+| 💩 | `:poop:` | — | Write bad code that needs to be improved |
+| ⏪️ | `:rewind:` | patch | Revert changes |
+| 🔀 | `:twisted_rightwards_arrows:` | — | Merge branches |
+| 📦️ | `:package:` | patch | Add or update compiled files or packages |
+| 👽️ | `:alien:` | patch | Update code due to external API changes |
+| 🚚 | `:truck:` | — | Move or rename resources (e.g.: files, paths, routes) |
+| 📄 | `:page_facing_up:` | — | Add or update license |
+| 💥 | `:boom:` | major | Introduce breaking changes |
+| 🍱 | `:bento:` | patch | Add or update assets |
+| ♿️ | `:wheelchair:` | patch | Improve accessibility |
+| 💡 | `:bulb:` | — | Add or update comments in source code |
+| 🍻 | `:beers:` | — | Write code drunkenly |
+| 💬 | `:speech_balloon:` | patch | Add or update text and literals |
+| 🗃️ | `:card_file_box:` | patch | Perform database related changes |
+| 🔊 | `:loud_sound:` | — | Add or update logs |
+| 🔇 | `:mute:` | — | Remove logs |
+| 👥 | `:busts_in_silhouette:` | — | Add or update contributor(s) |
+| 🚸 | `:children_crossing:` | patch | Improve user experience / usability |
+| 🏗️ | `:building_construction:` | — | Make architectural changes |
+| 📱 | `:iphone:` | patch | Work on responsive design |
+| 🤡 | `:clown_face:` | — | Mock things |
+| 🥚 | `:egg:` | patch | Add or update an easter egg |
+| 🙈 | `:see_no_evil:` | — | Add or update a .gitignore file |
+| 📸 | `:camera_flash:` | — | Add or update snapshots |
+| ⚗️ | `:alembic:` | patch | Perform experiments |
+| 🔍️ | `:mag:` | patch | Improve SEO |
+| 🏷️ | `:label:` | patch | Add or update types |
+| 🌱 | `:seedling:` | — | Add or update seed files |
+| 🚩 | `:triangular_flag_on_post:` | patch | Add, update, or remove feature flags |
+| 🥅 | `:goal_net:` | patch | Catch errors |
+| 💫 | `:dizzy:` | patch | Add or update animations and transitions |
+| 🗑️ | `:wastebasket:` | patch | Deprecate code that needs to be cleaned up |
+| 🛂 | `:passport_control:` | patch | Work on code related to authorization, roles and permissions |
+| 🩹 | `:adhesive_bandage:` | patch | Simple fix for a non-critical issue |
+| 🧐 | `:monocle_face:` | — | Data exploration/inspection |
+| ⚰️ | `:coffin:` | — | Remove dead code |
+| 🧪 | `:test_tube:` | — | Add a failing test |
+| 👔 | `:necktie:` | patch | Add or update business logic |
+| 🩺 | `:stethoscope:` | — | Add or update healthcheck |
+| 🧱 | `:bricks:` | — | Infrastructure related changes |
+| 🧑‍💻 | `:technologist:` | — | Improve developer experience |
+| 💸 | `:money_with_wings:` | — | Add sponsorships or money related infrastructure |
+| 🧵 | `:thread:` | — | Add or update code related to multithreading or concurrency |
+| 🦺 | `:safety_vest:` | — | Add or update code related to validation |
+| ✈️ | `:airplane:` | — | Improve offline support |
+| 🦖 | `:t-rex:` | — | Code that adds backwards compatibility |
+## Tooling that has to accept the format
+
+Emoji-first is what gitmoji itself prescribes and what `gitmoji -c` writes, but a **strict
+Conventional Commits parser anchors the type at position 0** and will reject the header. Two honest
+ways out, in order of preference:
+
+**1. Teach the parser about the prefix.** commitlint, with the emoji allowed before the type:
+
+```js
+// commitlint.config.js
+export default {
+  extends: ['@commitlint/config-conventional'],
+  parserPreset: {
+    parserOpts: {
+      // <emoji> type(scope)!: subject
+      headerPattern: /^(?:\S+\s)?(\w+)(?:\(([^)]*)\))?(!)?: (.+)$/,
+      headerCorrespondence: ['type', 'scope', 'breaking', 'subject'],
+    },
+  },
+};
+```
+
+semantic-release / conventional-changelog take the same `parserOpts` under
+`@semantic-release/commit-analyzer` and `@semantic-release/release-notes-generator`. Set it in
+**both** or the bump and the changelog disagree about the same commit.
+
+**2. Put the emoji after the header** — `feat(api): ✨ add cursor paging`. Every conventional parser
+accepts it unmodified, and the guard accepts it too. Prefer this in a repo whose release pipeline
+you do not own.
+
+What **not** to do: drop the type and commit `✨ add cursor paging` (gitmoji's own minimal form).
+It is valid gitmoji and useless for releases — nothing can derive the bump, so the version has to be
+hand-picked, which `../SKILL.md` forbids for a reason.
+
+## Related
+
+- `gitmoji-cli` (`npm i -g gitmoji-cli`, then `gitmoji -c`) prompts for the emoji and writes the
+  commit. Optional — the convention is the rule, the CLI is one way to type it.
+- On Claude Code, rsc wires a `gitmoji-guard` PreToolUse hook that denies a `git commit` whose
+  message has no gitmoji, with the corrected message in the refusal. It only judges messages it can
+  actually read (`-m`, heredoc) and never blocks an editor commit, a `-F` file, or `--amend
+  --no-edit`. Opt out per project with `.rsc/.no-gitmoji`.

package/skills/ship/SKILL.md

@@ -184,7 +184,7 @@ cleanup). If a native `EnterWorktree`-style tool created it, exit through that t
 
 The commit is the durable record. Make it describe the change and tie it to the spec — and keep it Eric's.
 
-- **Subject:** `type: imperative summary (<spec-slug>)` — `feat:`, `fix:`, `refactor:`, etc. Under ~72 chars.
+- **Subject:** `<gitmoji> type: imperative summary (<spec-slug>)` — `✨ feat:`, `🐛 fix:`, `♻️ refactor:`, etc. Under ~72 chars. The gitmoji is **not optional**: on Claude Code a PreToolUse guard denies a `git commit -m` without one, and the refusal hands back the corrected message. Emoji → intention table: `../git-workflow/references/gitmoji.md`.
 - **Body:** *why*, not a restatement of the diff. Reference the spec slug and any decision logged in `decisions.md`.
 - **Footer:** issue/PR refs only. **No `Co-Authored-By` for any AI. No "generated with" line.** This is where the violation usually sneaks in — leave the footer clean.
 
@@ -212,6 +212,7 @@ Read the level from `02-DOCS/wiki/harness/user-profile.md`. It changes what you
 | "The tree has a couple of stray edits, they're harmless" | A dirty tree means the merge is not the reviewed diff. Clean it or stash it first. |
 | "`main` is protected but I'll just force-merge, I'm sure" | Protected means PR. Don't bypass the gate the repo deliberately set. |
 | "I'll rebase and resolve conflicts during the merge" | Resolve before. A conflicted merge commit hides what actually shipped. |
+| "The gitmoji is decoration, the conventional type is what matters" | Both ship or neither does. The type is for tooling, the emoji for the human scanning `git log` — and the guard denies the commit either way. |
 | "This branch is dead, I'll just delete it" | Discard is destructive — confirm with the quoted branch name and log why first. |
 | "Squash everything, history doesn't matter" | Squash noise, preserve meaning. The history is the next reader's spec. |
 | "There's a key in the diff but it's a test key" | A secret in the diff is a blocker regardless. Pull it out before landing. |

package/targets/claude.js

@@ -113,6 +113,21 @@ export function wireHook(paths) {
   );
   settings.hooks.PreToolUse.push({ matcher: 'Bash', hooks: [{ type: 'command', command: dgCmd }] });
 
+  // Gitmoji guard: a PreToolUse(Bash) hook that DENIES a `git commit` whose message
+  // carries no gitmoji (gitmoji.dev) in front of the Conventional Commits header. The
+  // convention lives in `git-workflow`; prose asks, this hook decides — at the one
+  // deterministic moment the message exists. Only fires when the message is inline and
+  // readable (-m / heredoc); editor commits, -F files and --amend --no-edit are allowed.
+  // Materialized + node-run (Windows-safe), idempotent, fail-open, opt-out via
+  // .rsc/.no-gitmoji.
+  const gmDest = join(paths.projectRoot, '.rsc', 'gitmoji-guard.mjs');
+  copyFileSync(join(HERE, 'gitmoji-guard.mjs'), gmDest);
+  const gmCmd = `node "${gmDest}" "${paths.projectRoot}"`;
+  settings.hooks.PreToolUse = settings.hooks.PreToolUse.filter(
+    (e) => !JSON.stringify(e).includes('.rsc/gitmoji-guard.'),
+  );
+  settings.hooks.PreToolUse.push({ matcher: 'Bash', hooks: [{ type: 'command', command: gmCmd }] });
+
   // New-feature gate: a UserPromptSubmit hook that re-injects the SDD new-feature gate as
   // the most-recent instruction on every user turn. SessionStart injects the full gate (the
   // `suggest` body) once; this keeps the precedence rule salient regardless of how many
@@ -132,5 +147,5 @@ export function wireHook(paths) {
 
   mkdirSync(dirname(file), { recursive: true });
   writeFileSync(file, JSON.stringify(settings, null, 2) + '\n');
-  return [file, scriptDest, wlDest, sgDest, dgDest, fgDest];
+  return [file, scriptDest, wlDest, sgDest, dgDest, gmDest, fgDest];
 }

package/targets/gitmoji-guard.mjs

@@ -0,0 +1,250 @@
+#!/usr/bin/env node
+// rsc Gitmoji guard (claude). Wired by targets/claude.js onto PreToolUse (matcher Bash)
+// as `node ...` so it runs on every platform including Windows.
+//   argv[2] = absolute project root   stdin = PreToolUse hook JSON
+//
+// Enforces one convention at the only deterministic moment it can be enforced: the
+// commit is being written. Every commit message this harness produces carries a
+// gitmoji (https://gitmoji.dev) — the intention of the change, visible in one glyph
+// in `git log --oneline`, on top of the Conventional Commits grammar that already
+// drives the semver bump. Prose in a skill asks; this hook decides.
+//
+// Accepted shapes (both are gitmoji-valid; the first is what `git-workflow` prescribes):
+//   ✨ feat(api): add cursor paging
+//   feat(api): ✨ add cursor paging
+//
+// Design (constitution P1/P2/P6/P7): deterministic, local-only, precise — it fires only
+// on a `git commit` that carries its message inline, where the message can actually be
+// read. Anything it cannot read with certainty (editor commit, -F file, --amend
+// --no-edit, an unparseable command) is ALLOWED: a guard that guesses is a guard that
+// gets turned off. Every deny names its recovery. Opt out with .rsc/.no-gitmoji.
+import { existsSync, readFileSync } from 'node:fs';
+import { join } from 'node:path';
+
+// The official gitmoji set (gitmoji.dev/api/gitmojis), as data: [emoji, code, semver, meaning].
+// A table, not a chain of ifs — so a test can iterate it and the reference doc can be
+// checked against it instead of drifting apart in prose.
+export const GITMOJIS = [
+  ['🎨', ':art:', null, "Improve structure / format of the code."],
+  ['⚡️', ':zap:', 'patch', "Improve performance."],
+  ['🔥', ':fire:', null, "Remove code or files."],
+  ['🐛', ':bug:', 'patch', "Fix a bug."],
+  ['🚑️', ':ambulance:', 'patch', "Critical hotfix."],
+  ['✨', ':sparkles:', 'minor', "Introduce new features."],
+  ['📝', ':memo:', null, "Add or update documentation."],
+  ['🚀', ':rocket:', null, "Deploy stuff."],
+  ['💄', ':lipstick:', 'patch', "Add or update the UI and style files."],
+  ['🎉', ':tada:', null, "Begin a project."],
+  ['✅', ':white_check_mark:', null, "Add, update, or pass tests."],
+  ['🔒️', ':lock:', 'patch', "Fix security or privacy issues."],
+  ['🔐', ':closed_lock_with_key:', null, "Add or update secrets."],
+  ['🔖', ':bookmark:', null, "Release / Version tags."],
+  ['🚨', ':rotating_light:', null, "Fix compiler / linter warnings."],
+  ['🚧', ':construction:', null, "Work in progress."],
+  ['💚', ':green_heart:', null, "Fix CI Build."],
+  ['⬇️', ':arrow_down:', 'patch', "Downgrade dependencies."],
+  ['⬆️', ':arrow_up:', 'patch', "Upgrade dependencies."],
+  ['📌', ':pushpin:', 'patch', "Pin dependencies to specific versions."],
+  ['👷', ':construction_worker:', null, "Add or update CI build system."],
+  ['📈', ':chart_with_upwards_trend:', 'patch', "Add or update analytics or track code."],
+  ['♻️', ':recycle:', null, "Refactor code."],
+  ['➕', ':heavy_plus_sign:', 'patch', "Add a dependency."],
+  ['➖', ':heavy_minus_sign:', 'patch', "Remove a dependency."],
+  ['🔧', ':wrench:', 'patch', "Add or update configuration files."],
+  ['🔨', ':hammer:', null, "Add or update development scripts."],
+  ['🌐', ':globe_with_meridians:', 'patch', "Internationalization and localization."],
+  ['✏️', ':pencil2:', 'patch', "Fix typos."],
+  ['💩', ':poop:', null, "Write bad code that needs to be improved."],
+  ['⏪️', ':rewind:', 'patch', "Revert changes."],
+  ['🔀', ':twisted_rightwards_arrows:', null, "Merge branches."],
+  ['📦️', ':package:', 'patch', "Add or update compiled files or packages."],
+  ['👽️', ':alien:', 'patch', "Update code due to external API changes."],
+  ['🚚', ':truck:', null, "Move or rename resources (e.g.: files, paths, routes)."],
+  ['📄', ':page_facing_up:', null, "Add or update license."],
+  ['💥', ':boom:', 'major', "Introduce breaking changes."],
+  ['🍱', ':bento:', 'patch', "Add or update assets."],
+  ['♿️', ':wheelchair:', 'patch', "Improve accessibility."],
+  ['💡', ':bulb:', null, "Add or update comments in source code."],
+  ['🍻', ':beers:', null, "Write code drunkenly."],
+  ['💬', ':speech_balloon:', 'patch', "Add or update text and literals."],
+  ['🗃️', ':card_file_box:', 'patch', "Perform database related changes."],
+  ['🔊', ':loud_sound:', null, "Add or update logs."],
+  ['🔇', ':mute:', null, "Remove logs."],
+  ['👥', ':busts_in_silhouette:', null, "Add or update contributor(s)."],
+  ['🚸', ':children_crossing:', 'patch', "Improve user experience / usability."],
+  ['🏗️', ':building_construction:', null, "Make architectural changes."],
+  ['📱', ':iphone:', 'patch', "Work on responsive design."],
+  ['🤡', ':clown_face:', null, "Mock things."],
+  ['🥚', ':egg:', 'patch', "Add or update an easter egg."],
+  ['🙈', ':see_no_evil:', null, "Add or update a .gitignore file."],
+  ['📸', ':camera_flash:', null, "Add or update snapshots."],
+  ['⚗️', ':alembic:', 'patch', "Perform experiments."],
+  ['🔍️', ':mag:', 'patch', "Improve SEO."],
+  ['🏷️', ':label:', 'patch', "Add or update types."],
+  ['🌱', ':seedling:', null, "Add or update seed files."],
+  ['🚩', ':triangular_flag_on_post:', 'patch', "Add, update, or remove feature flags."],
+  ['🥅', ':goal_net:', 'patch', "Catch errors."],
+  ['💫', ':dizzy:', 'patch', "Add or update animations and transitions."],
+  ['🗑️', ':wastebasket:', 'patch', "Deprecate code that needs to be cleaned up."],
+  ['🛂', ':passport_control:', 'patch', "Work on code related to authorization, roles and permissions."],
+  ['🩹', ':adhesive_bandage:', 'patch', "Simple fix for a non-critical issue."],
+  ['🧐', ':monocle_face:', null, "Data exploration/inspection."],
+  ['⚰️', ':coffin:', null, "Remove dead code."],
+  ['🧪', ':test_tube:', null, "Add a failing test."],
+  ['👔', ':necktie:', 'patch', "Add or update business logic."],
+  ['🩺', ':stethoscope:', null, "Add or update healthcheck."],
+  ['🧱', ':bricks:', null, "Infrastructure related changes."],
+  ['🧑‍💻', ':technologist:', null, "Improve developer experience."],
+  ['💸', ':money_with_wings:', null, "Add sponsorships or money related infrastructure."],
+  ['🧵', ':thread:', null, "Add or update code related to multithreading or concurrency."],
+  ['🦺', ':safety_vest:', null, "Add or update code related to validation."],
+  ['✈️', ':airplane:', null, "Improve offline support."],
+  ['🦖', ':t-rex:', null, "Code that adds backwards compatibility."],];
+
+// Some official gitmojis carry U+FE0F (⚡️, 🔒️, 🗑️ …). A human typing the bare
+// code point means the same emoji, so compare with the variation selector stripped —
+// otherwise the guard would reject a correct commit over an invisible byte.
+const bare = (s) => s.replace(/️/g, '');
+export const EMOJI_SET = new Set(GITMOJIS.map(([e]) => bare(e)));
+export const CODE_SET = new Set(GITMOJIS.map(([, c]) => c));
+
+// git's own functional prefixes: these messages are consumed by `rebase --autosquash`,
+// not read by humans, and the final message is the target commit's. Nothing to enforce.
+const GIT_MAGIC = /^(fixup|squash|amend)!/;
+// A Conventional Commits header, optionally present before the emoji.
+const CONVENTIONAL = /^[a-zA-Z]+(\([^)\n]*\))?!?:\s*/;
+
+// Does this subject line open with a gitmoji — either before the conventional prefix
+// or immediately after it? An emoji buried mid-sentence is not an intention marker.
+export function hasGitmoji(message) {
+  const subject = String(message ?? '').split(/\r?\n/, 1)[0].trim();
+  if (!subject) return false;
+  if (GIT_MAGIC.test(subject)) return true;
+  const candidates = [subject, subject.replace(CONVENTIONAL, '')];
+  for (const c of candidates) {
+    const head = bare(c);
+    for (const e of EMOJI_SET) if (head.startsWith(e)) return true;
+    const code = head.match(/^:[a-z0-9_+-]+:/);
+    if (code && CODE_SET.has(code[0])) return true;
+  }
+  return false;
+}
+
+// ---- reading the message out of a shell command --------------------------------
+// Shell is not parseable in a regex and we do not pretend otherwise: this recognizes
+// the forms an agent or a human actually types, and returns null ("cannot tell") for
+// everything else so the caller allows it.
+
+const COMMIT = /\bgit\b(?:\s+-{1,2}\S+(?:\s+\S+)?)*\s+commit\b/;
+const NO_MESSAGE_TO_READ = /(?:^|\s)(?:-F|--file|--template|-C\s+\S*HEAD|--reuse-message|--reedit-message)\b/;
+const AMEND_NO_EDIT = /--no-edit\b/;
+const HAS_INLINE_M = /(?:^|\s)(?:-[a-zA-Z]*m|--message)(?:=|\s|$)/;
+// `git` must be the command being RUN, not text inside someone else's argument —
+// otherwise `echo "git commit -m x"` or `grep "git commit -m"` gets denied, and a guard
+// that blocks the discussion of commits is exactly the kind that gets switched off.
+const RUNS_GIT = /^\s*(?:sudo\s+)?(?:[A-Za-z_][A-Za-z0-9_]*=\S*\s+)*git\b/;
+
+const SEPARATORS = /&&|\|\||[;\n]/;
+
+// Is this segment a `git commit` that carries its message inline and readably?
+function readableCommit(segment) {
+  return RUNS_GIT.test(segment)
+    && COMMIT.test(segment)
+    && HAS_INLINE_M.test(segment)
+    && !NO_MESSAGE_TO_READ.test(segment)
+    && !AMEND_NO_EDIT.test(segment);
+}
+
+// `-m "$(cat <<'EOF' … EOF)"` — the multi-line form. The heredoc body IS the message,
+// and it may contain && or ; so it must be lifted out before any splitting.
+function heredocBody(command) {
+  const m = command.match(/<<-?\s*['"]?([A-Za-z_][A-Za-z0-9_]*)['"]?\r?\n([\s\S]*?)\r?\n[ \t]*\1\b/);
+  return m ? m[2] : null;
+}
+
+// -m/--message value, quoted or bare.
+function inlineMessage(segment) {
+  const m = segment.match(/(?:^|\s)(?:-[a-zA-Z]*m|--message)(?:=|\s+)("([^"]*)"|'([^']*)'|([^\s'"][^\s]*))/);
+  if (!m) return null;
+  return m[2] ?? m[3] ?? m[4] ?? null;
+}
+
+// Every commit message this command would write, or null when nothing is checkable.
+export function commitMessages(command) {
+  const cmd = String(command ?? '');
+  if (!COMMIT.test(cmd)) return [];
+
+  // The heredoc form must be handled before any splitting: its body is the message and
+  // may legitimately contain && or ;. The command that owns it is whatever runs just
+  // before the `<<`.
+  const hIdx = cmd.search(/<<-?\s*['"]?[A-Za-z_]/);
+  if (hIdx !== -1) {
+    const owner = cmd.slice(0, hIdx).split(SEPARATORS).pop() || '';
+    if (!readableCommit(owner)) return [];
+    const body = heredocBody(cmd);
+    if (body === null) return [];
+    const first = body.split(/\r?\n/).find((l) => l.trim() !== '');
+    return first === undefined ? [] : [first];
+  }
+
+  const out = [];
+  for (const segment of cmd.split(SEPARATORS)) {
+    if (!readableCommit(segment)) continue;
+    const msg = inlineMessage(segment);
+    if (msg === null) continue;                       // editor commit — cannot read it here
+    if (/^\$/.test(msg.trim())) continue;             // a variable/substitution, not a literal
+    out.push(msg);
+  }
+  return out;
+}
+
+// ---- the deny message (P6: the recovery lives inside the refusal) ---------------
+
+export const SUGGESTIONS = [
+  ['feat', '✨'], ['fix', '🐛'], ['docs', '📝'], ['refactor', '♻️'], ['test', '✅'],
+  ['perf', '⚡️'], ['chore', '🔧'], ['ci', '👷'], ['style', '🎨'], ['revert', '⏪️'],
+];
+
+export function denyMessage(message) {
+  const subject = String(message ?? '').split(/\r?\n/, 1)[0].trim();
+  const type = subject.match(/^([a-zA-Z]+)(\([^)\n]*\))?!?:/)?.[1]?.toLowerCase();
+  const hit = SUGGESTIONS.find(([t]) => t === type);
+  const rewrite = hit
+    ? `${hit[1]} ${subject}`
+    : `${SUGGESTIONS.find(([t]) => t === 'chore')[1]} ${subject || '<type>(<scope>): <subject>'}`;
+  return [
+    `This commit message has no gitmoji: "${subject}".`,
+    'Every commit in this project opens with a gitmoji (gitmoji.dev) before the Conventional Commits header — the intention of the change, readable in one glyph in `git log --oneline`.',
+    `Recover: re-run the commit with the emoji in front — \`${rewrite}\` — picking the gitmoji that matches the intention (✨ feature · 🐛 fix · 📝 docs · ♻️ refactor · ✅ tests · ⚡️ perf · 🔧 config · 👷 CI · 💥 breaking · 🔖 release). The full table is in the \`git-workflow\` skill (references/gitmoji.md). To turn this guard off for this project, create .rsc/.no-gitmoji.`,
+  ].join('\n');
+}
+
+// ---- hook entrypoint -----------------------------------------------------------
+// Skipped when imported by a test (P2: the mechanism is testable without a subprocess).
+if (import.meta.url === `file://${process.argv[1]}`) {
+  const root = process.argv[2] || process.cwd();
+  const allow = () => process.exit(0);
+
+  if (existsSync(join(root, '.rsc', '.no-gitmoji'))) allow();
+
+  let input = {};
+  try { input = JSON.parse(readFileSync(0, 'utf8') || '{}'); } catch { allow(); }
+  if ((input.tool_name || input.toolName) !== 'Bash') allow();
+  const command = input.tool_input?.command || input.toolInput?.command || '';
+  if (typeof command !== 'string' || !command) allow();
+
+  let offender = null;
+  try {
+    offender = commitMessages(command).find((m) => !hasGitmoji(m)) ?? null;
+  } catch { allow(); } // any parsing surprise → allow (fail open, by design)
+  if (offender === null) allow();
+
+  process.stdout.write(JSON.stringify({
+    hookSpecificOutput: {
+      hookEventName: 'PreToolUse',
+      permissionDecision: 'deny',
+      permissionDecisionReason: denyMessage(offender),
+    },
+  }));
+  process.exit(0);
+}