articulate

Writes and reviews UX copy, error messages, empty states, and voice frameworks for product interfaces.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/rakedzior/rootine --skill articulate-rakedzior
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: articulate
Source: https://github.com/rakedzior/rootine/tree/main/agent/skills/articulate
Command: npx skills add https://github.com/rakedzior/rootine --skill articulate-rakedzior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often ship interfaces with inconsistent, confusing, or untranslatable copy because no one owns the words. This Skill provides a systematic discipline for UX writing and content strategy so every label, error, and empty state communicates clearly and consistently. ## Core Features & Use Cases - Voice and Tone Frameworks: Define 3-5 voice principles with boundaries and a tone spectrum across contexts like onboarding, destructive confirmations, and success messages. - Error and Empty State Design: Structure error messages with what happened, why it matters, and what to do; design first-use, no-results, cleared, and error-caused empty states with actions. - Microcopy and Content Models: Create reusable patterns for tooltips, placeholders, CTAs, and confirmations, plus structured content models with localization-readiness and inclusive language guidance. - Use Case: A team preparing a new settings flow asks for a copy deck; the Skill delivers screen-by-screen copy, an error message inventory, and CTA language with localization flags. ## Quick Start Ask the assistant to review the error messages and empty states in your onboarding flow and rewrite them using a consistent voice and tone framework.

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 parts: what happened specifically, why it matters to the user, and what to do next. Scale tone by 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 defines 3-5 product attributes translated into voice principles with clear boundaries, plus a tone spectrum showing how the constant voice shifts across contexts like onboarding, errors, and success messages. It includes do/don't examples so any writer makes consistent decisions.

How do I design empty states that help users?▼

Identify the empty state type: first-use, no-results, cleared, or error-caused. Each needs a message explaining why it is empty, an illustration direction, a primary action, and a secondary action. First-use states should onboard; no-results states should suggest query adjustments.

Does UX copy need to change for localization?▼

Yes. Avoid concatenated strings, idioms, culturally specific humor, and date-relative phrases, and plan for 20-35% text expansion in languages like German. Build relative dates from timestamps at render time and never embed text in images.

What are the limits of a UX writing skill?▼

It covers product interface copy, not marketing copy, brand naming, taglines, visual typography, or flow structure. Navigation labeling is shared with information architecture work, and translation execution belongs to localization processes.