ux-brief
UX Brief
This skill exists to stop: ambiguous design handoffs and repeated approval of directions the user already accepted.
🤖 0. HOW TO USE
BUILD produces a focused component/page brief; ARCHITECT covers the full redesign. Use evaluation findings and accepted decisions from the conversation, supplied documents, or .jimmy/work/<feature>/design-evaluation.md. Missing filenames do not require repeating research. Output .jimmy/work/<feature>/design-brief.md, scoped to the accepted change, for ux-specify and the development plan.
Translate evaluation findings into a design brief that the spec and plan skills can execute against. This is where analysis becomes direction.
Core Principle: A design brief bridges the gap between "what's wrong" (evaluation) and "what to build" (spec + plan). Without it, the developer interprets the evaluation themselves — and developers optimize for code elegance, not user experience. The brief makes design decisions explicit so implementation follows design intent.