articulate

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill articulate-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: articulate
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/articulate
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill articulate-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams 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 message, and empty state is clear, consistent, and actionable. ## Core Features & Use Cases - Voice and Tone Frameworks: Build actionable voice principles with boundaries, tone spectrums across contexts, and do/don't examples any writer can apply. - Error Messages, Empty States & Microcopy: Design structured error messages (what happened, why it matters, what to do), four types of empty states, CTAs, tooltips, placeholders, and confirmation dialogs. - Content Models & Inclusive Language: Define structured content types with truncation and localization rules, plus readability and inclusive language guidelines. - Use Case: A team preparing a product launch uses this Skill to audit every screen's copy, produce a copy deck with error message inventory, and establish a voice framework so future releases stay tonally consistent. ## Quick Start Ask the AI to review the error messages and empty states in your onboarding flow and rewrite them following UX writing best practices.

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 by severity, avoid blame language and jargon, and always provide a recovery path or honestly state when none exists.

How do I create a voice and tone framework for a product?

Identify 3-5 product attributes, translate each into a voice principle with clear boundaries on both sides, then map how tone shifts across 4-6 contexts like onboarding versus destructive confirmations. Document everything with real product copy examples, not abstract rules.

What should an empty state say in a UI?

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

Does UX writing need to account for localization?

Yes. Avoid idioms, concatenated strings, date-relative phrases, and text embedded in images. Plan for 20-35% text expansion in languages like German and support right-to-left layouts so copy translates cleanly.

What are the limits of a UX writing skill versus flow design?

UX writing owns what screens say, not how users move between them. Flow sequencing and task design belong to journey mapping, navigation taxonomy is shared with information architecture, and marketing or brand campaign copy is out of scope.