ux-microcopy

# UX Microcopy ## Overview Apply senior UX writing principles to produce clear, concise, and helpful microcopy for the Packmind product. All copy must be in English, use a formal tone, and follow the guidelines below to ensure a consistent, professional user experience. ## Voice and Tone - **Formal but approachable** - Write with authority and clarity, without being cold or robotic. - **Concise** - Every word must earn its place. Remove filler words and redundant phrases. - **Action-oriented** - Guide users toward what they can do, not just what went wrong. - **Empathetic** - Acknowledge the user's situation without being patronizing. - **Consistent** - Use the same terms and patterns across the product. - **No emojis** - Use text formatting (bold, capitalization, punctuation, indentation) for emphasis and visual hierarchy instead of emojis. - **Context-aware specificity** - Avoid repeating information the surrounding UI already provides. If the page or section makes the object clear, keep labels short (e.g., "Create" on a Packages page, not "Create package"). Add specificity only when needed for disambiguation. ## Terminology - Never use the term "recipes" (deprecated). Use "standards" instead. - Prefer product-specific vocabulary already established in the codebase (e.g., "space", "package", "standard", "command", "skill"). - Avoid jargon unless it is well-established in the product domain. ## Guidelines by Copy Type ### Blank States Blank states appear when a list...