Bastien ChanotandClaude Opus 4.8
3d0ee262c1
The 07-02 tightening left bare tokens common in non-UI talk (design, component, theme, transition, frontend, palette) -> ~6 false-fires/session during the ECC config audit. Dropped them; dashboard now word-boundary matched (kills the ecc_dashboard.py filename match, keeps 'admin dashboard'); kept animation; added 'front-end design' bigram. Each fire now logs time+token+excerpt to a light file so 're-firing?' is measured, not argued. Regression test 18/18, shellcheck clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XpphkdTosUzokBDNG7PToS
61 lines
4.2 KiB
Bash
Executable File
61 lines
4.2 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# design-toolchain-reminder.sh
|
|
#
|
|
# UserPromptSubmit hook. When the prompt carries a UI/design signal, inject a
|
|
# reminder to mobilize the full design toolchain (tiered by scope, per CLAUDE.md
|
|
# "Design work — full toolchain"). A UserPromptSubmit hook's stdout is appended
|
|
# to the model's context, so the cat block below becomes additional guidance.
|
|
#
|
|
# 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"
|
|
|
|
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).
|
|
pattern='redesign|refonte|refont|ui/ux|ux/ui|\bui\b|\bux\b|ui kit|design system|design-system|front-?end design|\bnavbar\b|\bsidebar\b|\bmodal\b|\bbouton\b|\bbutton\b|formulaire|\bhero\b|\bheader\b|\bfooter\b|dropdown|tooltip|\bbadge\b|\bchart\b|graphique|accordion|carousel|\bslider\b|landing|\bdashboard\b|homepage|home page|\baccueil\b|\bécran\b|\becran\b|portfolio|maquette|mockup|wireframe|prototype|\bjoli\b|\bjolie\b|\bbeau\b|\bbelle\b|esth[eé]tique|aesthetic|\bvisuel\b|\bvisual\b|embellir|fignol|peaufin|polish|styliser|styling|stylesheet|\bskin\b|charte graphique|\bbrand\b|branding|\blogo\b|favicon|ic[oô]ne|\bicon\b|\bcss\b|tailwind|shadcn|couleur|gradient|d[eé]grad[eé]|\bombre\b|spacing|espacement|\bmarge\b|\bpadding\b|\bmargin\b|\bradius\b|arrondi|\bhover\b|dark mode|light mode|typograph|\bfont\b|\bfonts\b|font pairing|\bpolice\b|animation|\bmotion\b|micro-interaction|keyframe|glassmorph|neumorph|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-toolchain] UI/design signal detected. Apply CLAUDE.md "Design work — full toolchain (tiered by scope)":
|
|
- Trivial (≤2 files, single cosmetic value, CSS tweak) → /hotfix, NO toolchain.
|
|
- Build UI (component/page/screen/redesign) → ui-ux-pro-max (plan/build) + frontend-design (anti-slop) + Magic MCP /ui (21st.dev scaffold) + emil-design-eng (polish) + design-motion-principles (if motion) + design-html (if static/Pretext).
|
|
- Design system/brand → design-consultation FIRST, then the build tools above.
|
|
- Review/audit → design-review + emil-design-eng lens + design-motion-principles (audit mode).
|
|
If genuinely trivial/non-UI, ignore this and proceed. IN DOUBT about scope (trivial vs real UI change) → do NOT silently skip: ask the user, or default to the build tier rather than /hotfix.
|
|
EOF
|
|
fi
|
|
|
|
exit 0
|