14건 · 관련도순
Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use `ux-writing` (designer-toolkit); for structural hierarchy use `information-architecture`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write interface copy — microcopy, error messages, empty states, and CTAs. Use when the words are the deliverable. For content structure and ownership, use `content-strategy` (ux-strategy).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use `ux-writing` (designer-toolkit).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write or review UI copy — buttons, errors, empty states, microcopy, notifications, labels — using the voice & tone system (clear, concise, useful, human, honest) with the what→why→how error formula and inclusive-language rules. Use when the user needs interface copy, error messages, empty-state text, or a copy review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (grammar, capitalisation, formatting), terminology/word list, and accessibility/inclusivity rules — that a team can actually apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interface copy that works — voice/tone, the PACE framework, alert anatomy, naming features, empty states, error messages, and the small-word edits that measurably improve UX. Distilled from Apple's writing sessions (2017–2026). Use when writing or reviewing any user-facing text — labels, alerts, onboarding, notifications, empty states, paywalls — or naming a feature.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Judgment rules for user-facing text and docs: CLI and diagnostic output, error and help text, README and docs structure, code comments, titles, and generated reports, decks, or exports. Use when writing or changing any user-visible string, when adding or restructuring docs or deciding which page owns a fact, when a page is about to record a version, a deployment state, or a value the code already owns, when a comment, title, or artifact could carry the reasoning or an abandoned option behind the change, when a behavior change needs its copy sites swept, or when reviewing a diff that touches copy or docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
World-class copywriting expertise combining the persuasive clarity of David Ogilvy, the conversational warmth of Ann Handley, and the conversion science of modern growth marketers. Copywriting is where brand voice becomes words that move people. Great copy doesn't just communicate—it persuades, connects, and converts. The best copywriters understand that every word earns its place, that benefits beat features, that clarity trumps cleverness, and that the reader's problem is the only starting point that matters. Use when "copywriting, write copy, headlines, taglines, email copy, ad copy, landing page copy, product copy, UX writing, CTAs, value proposition, microcopy, sales copy, conversion copy, writing, copy, headlines, conversion, persuasion, messaging, UX-writing, emails" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write effective UI copy including microcopy, error messages, empty states, and CTAs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit UX copy in a product or codebase — find passive errors, generic labels, missing states. Use when asked to "audit our UX copy", "our error messages are bad", or "review the microcopy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Survey all user-facing strings in a codebase — map coverage and find gaps. Use when asked "what user-facing strings do we have", "map our copy coverage", or "find hardcoded strings".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write UX copy for a feature, flow, or component — buttons, errors, empty states, tooltips. Use when asked to "write the copy for this flow", "word this error message", or "write empty state copy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Escreve microcopy de interface — mensagens de erro, estados vazios, tooltips, rótulos de botão, onboarding e notificações. Use quando o usuário disser "UX writing", "microcopy", "mensagem de erro", "empty state", "texto do botão", "texto da interface", "onboarding do sistema".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.