forked from bchanot/claude
chore(hooks): retire the design-toolchain reminder hook
59 fires, 0 Reads of web-building.md (2026-10-31); the path rule and the CLAUDE.global.md pointer carry design routing. Hook, its test and its UserPromptSubmit entry removed; doctrine-citers T7c becomes T8i on a synthetic one-line fixture (quoted label kept whole).
This commit is contained in:
1 parent
97780b5f46
commit
9c038fd22b
5 files changed
+6
-152
No files matched your search
@@ -1,82 +0,0 @@
|
||||
#!/usr/bin/env bash
|
||||
# design-toolchain-reminder.sh
|
||||
#
|
||||
# UserPromptSubmit hook. When the prompt carries a UI/design signal, point the
|
||||
# model at the design toolchain section (tiered by scope). Since BDR-125
|
||||
# phase 1 it lives in rules/web-building.md § "Design work — full toolchain",
|
||||
# not in CLAUDE.global.md: it loads by itself on a UI file Read, and a
|
||||
# chat-only design request needs this pointer. A UserPromptSubmit hook's
|
||||
# stdout is appended to the model's context.
|
||||
#
|
||||
# This is a soft nudge: the tiered rule itself says trivial work uses NO
|
||||
# toolchain, so a false positive (e.g. "API design") costs only a reminder the
|
||||
# model can disregard. Always exits 0 so it never blocks prompt submission.
|
||||
#
|
||||
# Every fire appends one line (time, matched token, prompt excerpt) to
|
||||
# ~/.claude/logs/design-toolchain-fires.log — a counter so the next "is it
|
||||
# over-firing?" decision is measured, not anecdotal.
|
||||
|
||||
set -euo pipefail
|
||||
|
||||
input="$(cat)"
|
||||
|
||||
# Extract the user's prompt from the hook JSON; fall back to the raw stdin if
|
||||
# python or the expected field is unavailable.
|
||||
prompt="$(printf '%s' "$input" \
|
||||
| python3 -c 'import sys, json; print(json.load(sys.stdin).get("prompt", ""))' \
|
||||
2>/dev/null || true)"
|
||||
[ -z "$prompt" ] && prompt="$input"
|
||||
|
||||
# Harness-generated turns (task notifications, sub-agent hand-backs: 857 of
|
||||
# 2,779 logged fires on 2026-10-28) are not user requests — never fire on
|
||||
# them (the Design work trigger = a design/UI *request*).
|
||||
case "$prompt" in
|
||||
'<task-notification>'*|'<agent-message'*) exit 0 ;;
|
||||
esac
|
||||
|
||||
lc="$(printf '%s' "$prompt" | tr '[:upper:]' '[:lower:]')"
|
||||
|
||||
# UI/design build and review signals (FR + EN). Word boundaries (\b) avoid
|
||||
# substring false matches like perform/platform/information.
|
||||
# Tightened 2026-07-02: dropped ultra-generic tokens (page, form, menu, card,
|
||||
# style, look, screen, interface, color) that fired on non-UI prompts.
|
||||
# Tightened again 2026-07-03: dropped bare design|component|composant|theme|
|
||||
# thème|transition|frontend|front-end|palette — all common in non-UI technical
|
||||
# talk (a design decision, a system component, the theme of a discussion, a
|
||||
# state transition, frontend architecture). Kept as UI-specific compounds:
|
||||
# "design system", "redesign", "front-?end design". dashboard -> \bdashboard\b
|
||||
# so a filename like ecc_dashboard.py no longer matches while "admin dashboard"
|
||||
# still does. animation kept (rarely non-UI).
|
||||
# Tightened 2026-07-30 (3rd pass): dropped \bux\b — bare "ux" matched inside
|
||||
# French prose ("changement ux vu…"; 2 logged FPs, both FR). \bui\b KEPT
|
||||
# (zero logged FP, one logged true positive). NB: the log records only the
|
||||
# FIRST match per fire (head -1), so per-token FP rates aren't derivable.
|
||||
pattern='redesign|refonte|refont|ui/ux|ux/ui|\bui\b|ui kit|design system'
|
||||
pattern+='|design-system|front-?end design|\bnavbar\b|\bsidebar\b|\bmodal\b'
|
||||
pattern+='|\bbouton\b|\bbutton\b|formulaire|\bhero\b|\bheader\b|\bfooter\b'
|
||||
pattern+='|dropdown|tooltip|\bbadge\b|\bchart\b|graphique|accordion|carousel'
|
||||
pattern+='|\bslider\b|landing|\bdashboard\b|homepage|home page|\baccueil\b'
|
||||
pattern+='|\bécran\b|\becran\b|portfolio|maquette|mockup|wireframe|prototype'
|
||||
pattern+='|\bjoli\b|\bjolie\b|\bbeau\b|\bbelle\b|esth[eé]tique|aesthetic'
|
||||
pattern+='|\bvisuel\b|\bvisual\b|embellir|fignol|peaufin|polish|styliser'
|
||||
pattern+='|styling|stylesheet|\bskin\b|charte graphique|\bbrand\b|branding'
|
||||
pattern+='|\blogo\b|favicon|ic[oô]ne|\bicon\b|\bcss\b|tailwind|shadcn|couleur'
|
||||
pattern+='|gradient|d[eé]grad[eé]|\bombre\b|spacing|espacement|\bmarge\b'
|
||||
pattern+='|\bpadding\b|\bmargin\b|\bradius\b|arrondi|\bhover\b|dark mode'
|
||||
pattern+='|light mode|typograph|\bfont\b|\bfonts\b|font pairing|\bpolice\b'
|
||||
pattern+='|animation|\bmotion\b|micro-interaction|keyframe|glassmorph|neumorph'
|
||||
pattern+='|claymorph|skeuomorph|brutalis|bento|minimalis|responsive|figma'
|
||||
|
||||
if printf '%s' "$lc" | grep -Eq "$pattern"; then
|
||||
# Counter: log the fire (time, matched token, excerpt) — best-effort, never blocks.
|
||||
logf="${HOME}/.claude/logs/design-toolchain-fires.log"
|
||||
mkdir -p "$(dirname "$logf")" 2>/dev/null || true
|
||||
printf '%s\t%s\t%s\n' "$(date -Iseconds)" \
|
||||
"$(printf '%s' "$lc" | grep -oiE "$pattern" | head -1 || true)" \
|
||||
"$(printf '%s' "$prompt" | tr '\n\t' ' ' | cut -c1-100)" >> "$logf" 2>/dev/null || true
|
||||
cat <<'EOF'
|
||||
Design work detected → Read ~/.claude/rules/web-building.md § "Design work — full toolchain" first. Trivial (≤2 files, cosmetic) → /hotfix.
|
||||
EOF
|
||||
fi
|
||||
|
||||
exit 0
|
||||
Reference in new issue
Block a user