UI Brief

Tradeoff: Biases toward design opinionation. For greenfield work where the user wants exploration, use claude-design-brief instead.

Produce opinionated, design-leading UI briefs that survive contact with implementation.

The default failure mode for LLM-driven UI work is converging on the same shadcn-default-card-grid for every product. This skill exists to write a brief so opinion-dense and reference-specific that the implementing agent cannot drift back into that default. The output is a standalone Markdown file the user (or an orchestrator + frontend-agent) can paste into a fresh Claude Code session and execute against.

ui-brief vs its siblings. Reach for ui-brief when the deliverable is a written spec to hand to a Claude Code production build; use claude-design-brief instead when you want hi-fi mockups or A/B/C directions drawn on the Claude Design canvas at claude.ai, and frontend-design (or frontend-agent) when you want the UI actually built rather than briefed.

Announce at start: "Using ui-brief to write an opinionated design brief for [project]."

Two Modes — Greenfield vs Rebuild

The skill produces both flavors. Pick the right entry path:

Greenfield (no UI exists yet)

The user is building from scratch. Examples: a new product, a fresh app, a feature with no prior UI surface. The brief sets target style references and primitives upfront — there is nothing to diagnose, only failure modes to anticipate.