jaimejunr/claude-code-frontend-skills

ux-copy

Write or review UX copy — microcopy, error messages, empty states, CTAs.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/jaimejunr/claude-code-frontend-skills --skill ux-copy

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

/ux-copy

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Write or review UX copy for any interface context.

Usage

/ux-copy $ARGUMENTS

What I Need From You

  • Context: What screen, flow, or feature?
  • User state: What is the user trying to do? How are they feeling?
  • Tone: Formal, friendly, playful, reassuring?
  • Constraints: Character limits, platform guidelines?

Principles

  1. Clear: Say exactly what you mean. No jargon, no ambiguity.
  2. Concise: Use the fewest words that convey the full meaning.
  3. Consistent: Same terms for the same things everywhere.
  4. Useful: Every word should help the user accomplish their goal.
  5. Human: Write like a helpful person, not a robot.

Copy Patterns

CTAs

  • Start with a verb: "Start free trial", "Save changes", "Download report"
  • Be specific: "Create account" not "Submit"
  • Match the outcome to the label

Error Messages

Structure: What happened + Why + How to fix

  • "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."

Empty States

Structure: What this is + Why it's empty + How to start

  • "No projects yet. Create your first project to start collaborating with your team."

Confirmation Dialogs

  • Make the action clear: "Delete 3 files?" not "Are you sure?"
  • Describe consequences: "This can't be undone"
  • Label buttons with the action: "Delete files" / "Keep files" not "OK" / "Cancel"

Tooltips

  • Concise, helpful, never obvious

Loading States

  • Set expectations, reduce anxiety

Onboarding

  • Progressive disclosure, one concept at a time

Voice and Tone

Adapt tone to context:

  • Success: Celebratory but not over the top
  • Error: Empathetic and helpful
  • Warning: Clear and actionable
  • Neutral: Informative and concise

Output

markdown
## UX Copy: [Context]

### Recommended Copy
**[Element]**: [Copy]

### Alternatives
| Option | Copy | Tone | Best For |
|--------|------|------|----------|
| A | [Copy] | [Tone] | [When to use] |
| B | [Copy] | [Tone] | [When to use] |
| C | [Copy] | [Tone] | [When to use] |

### Rationale
[Why this copy works — user context, clarity, action-orientation]

### Localization Notes
[Anything translators should know — idioms to avoid, character expansion, cultural context]

If Connectors Available

If ~~knowledge base is connected:

  • Pull your brand voice guidelines and content style guide
  • Check for existing copy patterns and terminology standards

If ~~design tool is connected:

  • View the screen context in Figma to understand the full user flow
  • Check character limits and layout constraints from the design

Tips

  1. Be specific about context — "Error message when payment fails" is better than "error message."
  2. Share your brand voice — "We're professional but warm" helps me match your tone.
  3. Consider the user's emotional state — Error messages need empathy. Success messages can celebrate.
来自同一仓库

更多 Skills

全部 Skills
jaimejunr
社区

brandkit

Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.

1小时安装量
1
GitHub Stars
9
最近更新
11月16日
jaimejunr
社区

animate

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.

1小时安装量
1
GitHub Stars
8
最近更新
11月16日
jaimejunr
社区

animate-expo

Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web a

1小时安装量
1
GitHub Stars
8
最近更新
11月16日
jaimejunr
社区

animation-vocabulary

Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

1小时安装量
1
GitHub Stars
8
最近更新
11月16日