bolder · diff

git:20260418.504684e to git:20260705.37f48d9

14 added, 16 removed. Audit A to A.

---
name: bolder
- description: "Amplify an under-designed UI that's technically correct but forgettable. Invoke when the user asks for bolder on their UI, or mentions 'bolder' alongside design / UI / frontend work."
+ description: "Amplify personality — raises layout variance and motion, strengthens typography and one signature detail, without slop. Use when the UI works but feels safe, flat, or "template-y", or when the user says "bolder", "more personality", "more creative", or "make it pop" (still professional). Invoke when the user asks for bolder on their UI, or mentions 'bolder' alongside design / UI / frontend work."
---
- <!-- AUTO-GENERATED. Do not edit here. Source: skills/ui-craft/ + commands/*.md. Regenerate with `node scripts/sync-harnesses.mjs`. -->
+ <!-- HARNESS MIRROR — do not edit here. Canonical source: commands/bolder.md. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->
**Context:** this sub-skill is one lens of the broader `ui-craft` skill. If the `ui-craft` skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.
- Make the UI at the target the user described bolder. Load the `ui-craft` skill.
-
- **Pre-check — run the Craft Test from SKILL.md first**: if an accent is already overused or hierarchy is already loud, stop. You don't have a tameness problem — you have a noise problem. Route to `/quieter` instead.
+ Make the UI at `the target the user described` bolder. Load the `ui-craft` skill and read `references/craft-intent.md`.
- **Bolder is typography and hierarchy, not color or decoration.** Do not add gradients, emoji, colored borders, or new accents. Do not add "pops of color."
+ **This is amplitude, not decoration.** Increase editorial confidence while staying anti-slop clean.
- **Pick ONE element to carry signature** (never two):
+ **Apply in order (edit code directly):**
- 1. **Hero headline** — push size to 80-120px, weight to 700-800, tracking to -0.04em. Tight leading (0.95-1.0).
- 2. **Hierarchy jump** — widen the gap between H1 and body. If H1 is 48px and body is 16px, the ratio is fine; if H1 is 32px and body is 16px, the UI is whispering.
- 3. **Micro-motif** — one custom detail that repeats: a hand-drawn underline, numeric counters (`01`, `02`), an asymmetric supporting element, a distinctive list marker.
+ 1. **Declare an updated Craft Read** — one line: what changed (variance, motion, signature).
+ 2. **Raise DESIGN_VARIANCE** by +1–2 (cap 10). Product surfaces: asymmetric offset, stronger metric hierarchy, or display moment in shell. Marketing: stronger hero composition, section rhythm break, or typographic scale — per `references/craft-intent.md` variance table.
+ 3. **Raise MOTION_INTENSITY** by +1 (cap 10) if below 8 — add one purposeful entrance or hover choreography on the focal element only. Honor `prefers-reduced-motion`.
+ 4. **Typography** — increase display weight or size one step; tighten tracking on headlines; ensure numbers stay `tabular-nums`.
+ 5. **Accent** — strengthen focal accent placement (within 3–5 viewport budget); tint primary card or CTA — never add a second accent hue.
+ 6. **Signature** — add or strengthen the one signature bet if missing or weak (see craft-intent §3).
- **Knob gating (CRAFT_LEVEL):**
- - `≤ 4` → skip. Boldness is a craft layer, not a baseline. Ask the user before running.
- - `5-7` → apply the type amplification. No signature motif unless asked.
- - `8+` → type amplification + one signature detail (see `/polish`).
+ **Never add:** purple-cyan gradients, bounce easing, glassmorphism stacks, emoji, ALL CAPS headings, three equal icon-card grids, confetti.
- **References to read**: `references/typography.md` (size + weight + tracking), `references/layout.md` (hierarchy ratios), `references/inspiration.md` (what signature looks like on real sites).
+ **Knob gating:** if already at variance ≥9 or MOTION ≥9, strengthen signature and typography instead of pushing further.
- **Output**: edit code directly. Print the Review Format table from SKILL.md. One row per change. Flag any element you considered amplifying but left alone, and why.
+ **Output:** edit code. Print Review Format table. End with the updated Craft Read line.