Agent skill
microcopy-skill
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/microcopy-skill
SKILL.md
Microcopy Skill
=== PURPOSE ===
Procedures for creating effective UI microcopy.
=== USED BY ===
| Agent | Purpose |
|---|---|
| @agent(copywriter) @ref(CB-AGENT-COPY-001) | Primary skill for UI text |
=== PROCEDURE: Button Labels ===
Primary Actions:
| Pattern | Example | Usage |
|---|---|---|
| Verb | Save | Simple action |
| Verb + Object | Add item | Clarify target |
| Affirmative | Yes, delete | Confirmation |
Best Practices:
✓ Save
✓ Create project
✓ Send message
✓ Yes, delete it
✗ Submit (vague)
✗ Click here (unhelpful)
✗ OK (unclear)
✗ Do it (unprofessional)
Button Pairs:
| Primary | Secondary |
|---|---|
| Save | Cancel |
| Confirm | Go back |
| Delete | Keep |
| Yes, continue | No, cancel |
=== PROCEDURE: Form Labels ===
Label Guidelines:
✓ Email address (clear)
✗ Email (ambiguous - is it input or display?)
✓ Password (8+ characters) (helpful)
✗ Password (missing requirement info)
✓ Company name (optional) (clarifies optional)
✗ Company (unclear if required)
Placeholder Text:
- Use for examples, not labels
- Format: "e.g., [email protected]"
- Don't duplicate the label
Help Text:
Field: Password
Help: At least 8 characters, including a number
Field: Username
Help: Letters, numbers, and underscores only
=== PROCEDURE: Error Messages ===
Formula:
- What happened (briefly)
- Why (if helpful)
- How to fix
Examples:
✓ "Email already registered. Try signing in instead."
✗ "Error: Duplicate entry."
✓ "Password must be at least 8 characters."
✗ "Invalid password."
✓ "Couldn't connect. Check your internet and try again."
✗ "Network error."
✓ "Card declined. Try a different payment method."
✗ "Transaction failed."
Error Message Checklist:
- Uses plain language
- Explains the problem
- Suggests a solution
- Is specific (not generic)
- Doesn't blame the user
=== PROCEDURE: Success Messages ===
Patterns:
Completion: "Project created!"
Progress: "Changes saved."
Confirmation: "Email sent to [email protected]"
Guidelines:
- Keep it brief
- Be specific when helpful
- Match the tone to the action
- Include next steps if relevant
=== PROCEDURE: Empty States ===
Formula:
- What's missing (headline)
- Why it matters (optional)
- How to fix (CTA)
Template:
Headline: No [items] yet
Subtext: [Brief explanation or benefit]
CTA: [Create/Add first item]
Examples:
# No projects yet
Get started by creating your first project.
[Create project]
# No messages
You're all caught up!
(no CTA needed)
# No results found
Try adjusting your search or filters.
[Clear filters]
=== PROCEDURE: Tooltips & Help ===
Tooltip Guidelines:
- Maximum 150 characters
- Answer "What is this?" or "Why?"
- Don't repeat the label
- Use sentence case
Examples:
Label: Slug
Tooltip: A URL-friendly version of the title, e.g., "my-first-post"
Icon: [?]
Tooltip: Used to calculate shipping costs
Label: Make private
Tooltip: Only you can see private items
=== PROCEDURE: Notifications ===
Types:
| Type | Tone | Duration |
|---|---|---|
| Success | Positive | 3-5 seconds |
| Info | Neutral | Until dismissed |
| Warning | Cautious | Until dismissed |
| Error | Serious | Until fixed |
Notification Copy:
Success: "Changes saved"
Info: "New features are available"
Warning: "Your session will expire in 5 minutes"
Error: "Couldn't save. Try again."
=== PROCEDURE: Loading States ===
Patterns:
Generic: "Loading..."
Specific: "Loading your projects..."
Progress: "Uploading... 45%"
Humorous (if brand allows): "Fetching the goods..."
Long Operations:
Step 1: "Validating data..."
Step 2: "Processing..."
Step 3: "Almost done..."
=== RELATED SKILLS ===
| Skill | Relationship |
|---|---|
| @skill(voice-tone) | Tone guidance |
| @skill(user-content) | Longer content |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?