articulate

Write and review UX copy, error messages, empty states, and voice frameworks for product interfaces.

Updated May 5, 2026
One-click install
npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill articulate-thegeekosaurus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: articulate
Source: https://github.com/TheGeekosaurus/blogging-platform-2/tree/main/.agents/skills/articulate
Command: npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill articulate-thegeekosaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams ship interfaces with inconsistent, confusing, or generic copy because no one owns the words. This Skill provides a systematic discipline for UX writing and content strategy, turning ad-hoc strings into a coherent, maintainable system of labels, errors, empty states, and microcopy. ## Core Features & Use Cases - Voice and Tone Frameworks: Translate brand attributes into actionable voice principles with boundaries, tone spectrums across contexts, and do/don't examples any writer can apply. - Error Messages and Empty States: Design three-part error messages (what happened, why it matters, what to do) and empty states that onboard rather than dead-end users. - Microcopy and Content Models: Build reusable patterns for tooltips, placeholders, confirmations, and CTAs, plus structured content models that are localization-ready and inclusive. - Use Case: A team preparing a new onboarding flow brings their screens and asks what each step should say; the Skill produces a copy deck with primary messages, CTA text, error copy, and empty states, flagged for localization concerns. ## Quick Start Ask the AI to review the copy on your signup flow screens and rewrite the error messages, button labels, and empty states using clear, user-centered language.

Frequently Asked Questions about articulate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write better error messages for my product?▼

Structure every error message with three components: what happened specifically, why it matters to the user, and what to do next. Scale tone with severity, avoid blame language and jargon, and always provide a recovery action or an honest statement when none exists.

What is a voice and tone framework in UX writing?▼

A voice and tone framework translates 3-5 brand attributes into voice principles with clear boundaries, then maps how tone shifts across contexts like onboarding, errors, and success states. It includes do/don't examples so any writer can make consistent copy decisions.

How should empty states be designed in a UI?▼

Empty states should explain why the screen is empty and what to do next, with the approach varying by type: first-use states onboard, no-results states suggest adjustments, cleared states celebrate briefly, and error-caused states explain the failure and recovery path.

Does this Skill handle marketing copy or brand naming?▼

No. The Skill covers UX copy inside product interfaces only, such as labels, errors, tooltips, and confirmations. Marketing copy, advertising, brand naming, taglines, and editorial content are explicitly outside its scope.

How do I make product copy localization-ready?▼

Avoid concatenated strings, idioms, culturally specific humor, and date-relative phrases, and never embed text in images. Plan for 20-35% text expansion in languages like German and support right-to-left layouts in your content models.