Visual design
The Towles Tool desktop app's visual design language (apps/client), app-wide — color tokens, agent-status semantics, the identity wash (per-repo/checkout accent), folder/session hierarchy, spacing, glyphs, Tailwind recipes. Use when adding a new screen/component, restyling an existing one, or the user asks about the app's look, visual design, the rail, status dots/colors, the identity wash / repo colors, or the repo→folder→session hierarchy. Not needed for logic-only changes to already-styled components.From its SKILL.md
npx -y skills add ChrisTowles/towles-tool --skill visual-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.3 KB, as published. Nobody here has run it
Visual design — the app-wide language
Neutral grayscale shadcn base; hue is a budget spent on exactly three things: status, attention, identity. Everything else is type, spacing, and restraint. The full rendition — Agentboard anatomy (the named UI parts), live specimens, token/recipe tables, the ΔE rationale — is visual-design.html; read it before styling anything new.
The rules that bite
- Status dots mirror
statusColor()(lib/agentboard.ts) exactly; a new color implies a new state. Busy is cyan (never amber/yellow — that's the needs-you accent); interrupted is orange-800 (orange-500 sits inside both amber's and red's confusion radius). Before adding/tuning any hue, check OKLab ΔE by hand against every color it can sit next to; under ~15 between co-occurring colors is a real risk, not a nitpick. - Amber = needs-you, violet = agent-ness/focus. A needs-you row gets the
full treatment —
border-l-2 border-l-amber-500, row-widebg-amber-500/10(/15hover), flag dot beside the status dot; a thin border alone was tested and rejected. When a row is both active and needs-you, amber wins the border and fill; violet stays on the glyph. - Identity wash (
identityColor(),lib/identity-color.ts): a surface that is one repo/checkout wears its hashed accent as a /10 wash. Key by what the surface identifies — checkout for the app header, repo for the working-context band — and never mix keys on one surface. Absence is a state: an unwashed header means main checkout. Status and attention always render unchanged on top. - A box is a control or an alert, never a fact. Rail facts (diff counts,
branch, base-moved) are bare
font-mono; the box arrives on hover. Only needs-you, port drift, safe-to-delete and deleting keep a resting box. A pane header (one toolbar, room to spare) keeps the bordered, worded form. - Hierarchy: repo → folder → session (
✦agent /❯shell); attention bubbles up, and a deeper level never outranks its parent. - Type: sans (Geist, 13px base) for chrome;
font-monofor everything git/shell-owned — branches, ±diff stats, timestamps, counts, glyphs. - Don't animate resting UI —
animate-pulseis only a live, currently-true nudge (the busy dot), never a passive fact or rollup. - Tailwind + shadcn tokens only — no raw colors, no hand-written CSS, so light and dark both work.
Source of truth
lib/agentboard.ts (statusColor()) · lib/identity-color.ts (identity
wash) · components/app-header.tsx · the agentboard-* row files ·
components/header-status.tsx (needs-you math) · src/index.css (tokens).
Behavior/flow rules (confirmations, error copy, settings) are the ui-rules
skill, not here.