菜单
Write ui microcopy including button labels, empty states, error messages, tooltips, form labels, and onboarding strings. Use whenever the user mentions microcopy, ui strings, button text, error messages, empty states, tooltips, form labels, or any short interface text.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit a brand's full identity (logo, typography, color, voice, visual language) for consistency, distinctiveness, and gap. Use when the user asks for a brand audit, identity review, brand health check, or wants to evaluate how a brand shows up across surfaces.
Plan a content calendar tied to product, brand, or marketing goals. Use when the user asks for a content plan, editorial calendar, content strategy, posting schedule, or wants to map content to themes and audiences over a period of time.
Write a sequence of emails for onboarding, nurture, sales, lifecycle, or launch. Use when the user asks for a drip campaign, email sequence, welcome series, onboarding emails, sales cadence, or any multi-email flow tied to a goal.
Design an a/b test or experiment including hypothesis, metrics, sample size, and analysis plan. Use whenever the user mentions a/b test, experiment, split test, multivariate test, or needs to design a test that produces a decision-quality result.
Audit a design or component for WCAG accessibility compliance. Use whenever the user mentions a11y, accessibility audit, WCAG check, contrast issues, keyboard navigation, screen reader support, focus order, or asks if a design is accessible.
Extract a brand voice guide from existing copy samples. Use whenever the user shares past copy and asks to define a voice, document a voice, create voice guidelines, or wants to make their existing voice teachable and repeatable.
| name | microcopy-writing |
| description | Write ui microcopy including button labels, empty states, error messages, tooltips, form labels, and onboarding strings. Use whenever the user mentions microcopy, ui strings, button text, error messages, empty states, tooltips, form labels, or any short interface text. |
microcopy is the text inside a ui. it's read in the moment of doing something, not in the moment of being marketed to. write accordingly.
what's the action? lead with that.
errors should tell the user what happened and how to recover. not what the code did.
empty states are an onboarding moment. tell the user what to do to fill the space.
decide patterns and follow them across the product:
context: [where it appears in the ui]
purpose: [what it tells the user]
constraints: [character limit, tone, voice match]
audience: [who reads this]
drafts
a: [version 1]
b: [version 2]
c: [version 3]
recommendation: [a / b / c with one-sentence rationale]