UI copy and microcopy guidelines
Align button verbs, empty states, and error voice (apology vs direct vs playful boundaries); list banned terms and sensitive words; stay consistent with accessibility and design-system copy slots.
Case category · Product & UX
Product & UX
5 cases Category 3 of 20
This band supports product, design, and frontend collaboration: PRDs and acceptance, UI copy and empty/error states, visual and illustration briefs, and consistent brand tone across languages. Chain with frontend, UX, and documentation skills so agents draft and cross-check against your design system.
In the case hub it is Product & UX (#cat-design), complementing Creative & planning: this band emphasizes deliverable structure and standards; the ideation band leans toward divergent marketing-style drafts.
Quick links
UI copy and microcopy guidelines
Buttons, empty states, errors, voice.
Product PRD structuring
Context, scope, acceptance, dependencies.
User stories and acceptance criteria
Given/When/Then, boundaries, acceptance.
Visual specs and illustration briefs
Sizes, style, brand, deliverables.
Brand tone and multilingual style
Terminology, tone, banned words, localization.
In depth
Product PRD structuring
Organize PRDs with context, goals, non-goals, scope, dependencies, risks, and acceptance; call out metrics and instrumentation needs so prioritization and scheduling stay grounded.
User stories and acceptance criteria
Use Given/When/Then or scenario tables for user value and edge conditions; state out-of-scope paths explicitly to reduce dev/test mismatch.
Visual specs and illustration briefs
Specify canvas, safe areas, references, and brand color usage; list deliverable formats (SVG/PNG), motion level, and rights—so design and frontend can hand off cleanly.
Brand tone and multilingual style
Maintain glossaries and register preferences; handle gender-neutral phrasing and locale formats; note copy expansion per language so layouts do not assume English string lengths.