Skills on AI 459 skills

Active theme: Light

Microcopy

Use when asked to write small, functional interface text — labels, instructions, error messages, tooltips, button text — clarity, contextual relevance, user-focused language, tone/voice, error handling — as distinct from copywriting's longer, persuasion-focused content.

Microcopy is the small, concise blocks of text used throughout digital interfaces to guide and assist users in their interactions — labels, instructions, error messages, tooltips, button text, and other short snippets providing clarity, direction, and feedback.

Key aspects

  • Clarity — microcopy should be clear, concise, and easy to understand, communicating information straightforwardly without ambiguity or jargon.
  • Contextual relevance — microcopy should align with the user's current situation, providing guidance or information directly applicable to their needs at that moment.
  • User-focused language — written in user-centric language speaking directly to the user, matching the target audience's preferences, knowledge level, and language proficiency.
  • Tone and voice — microcopy should reflect the brand's tone and voice (see Branding) consistently, whether formal, friendly, professional, or playful.
  • Help and guidance — microcopy can act as a helpful assistant, preemptively answering potential questions or addressing common issues.
  • Error handling — microcopy plays a crucial role in communicating errors and guiding recovery; error messages should be concise, specific, and give an actionable next step.

Microcopy vs. copywriting

Microcopy is short, functional, and embedded in the moment of an interaction a user is already having — helping them complete a task correctly. Copywriting is longer-form and persuasion-focused — aimed at motivating a reader toward a decision they haven't made yet. The skills overlap (both need audience understanding and clear language), but microcopy is judged by whether it helps a user succeed at a task, not by whether it persuades.

Common pitfalls

  • Vague error messages — "Something went wrong" gives a user no actionable path forward; a good error message says what happened and what to do about it.
  • Jargon or system-internal language — exposing technical or backend terminology (error codes with no explanation, internal status names) to end users who have no context for it.
  • Inconsistent tone across the interface — microcopy that's playful in one part of the product and formal in another undermines a consistent brand experience.
  • Writing microcopy as an afterthought — adding button labels and error text at the end of a design process, rather than as part of it, tends to produce generic, unhelpful text disconnected from the actual user context.

Learn more

  • Copywriting for the longer-form, persuasion-focused counterpart.
  • Branding for the tone/voice consistency microcopy should maintain.
  • Inclusive Language for writing microcopy that doesn't exclude or demean.

View microcopy/SKILL.md on GitHub