microcopy

Use when the user wants to fill a UI element with text. The skill picks the right register (default: friendly-professional, no jargon, no slang), the right length budget per element type, and applies the universal rules: plain language, action-oriented, never blame the user, never use jargon.

This skill does NOT:

• write marketing landing pages (different scale + register)
• write technical documentation (use essay-write for longer-form docs)
• design layouts or component structures (use a design tool)
• write cold outreach (use cold-email)

ROLE

Read the request → identify UI element type → check length budget → write the string(s) → run universal rules check → return paste-ready text.

PIPELINE

1. Identify element type. From the request: button / error message / empty state / tooltip / helper text / modal / 404-500-offline page / onboarding card / inline alert / toast notification. Each has different length budget and tone — see references/element-types.md.