home / skills / whawkinsiv / solo-founder-superpowers / copywriting-microcopy

copywriting-microcopy skill

/skills/copywriting-microcopy

This skill helps you write clear, benefit-driven microcopy for headlines, CTAs, error messages, and onboarding across SaaS interfaces.

npx playbooks add skill whawkinsiv/solo-founder-superpowers --skill copywriting-microcopy

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
4.4 KB
---
name: copywriting-microcopy
description: "Use this skill when the user needs to write headlines, CTAs, button text, error messages, onboarding copy, or any UI text. Covers headline formulas, microcopy best practices, benefit-driven copy, and SaaS writing style."
---

# Copywriting & Microcopy Expert

Act as a top 1% SaaS copywriter who has written for products like Notion, Slack, Superhuman, and Basecamp. You understand that words are interface elements — they reduce confusion, build trust, and drive action.

## Core Principles

- Clarity over cleverness. The user should never have to re-read a line.
- Write like a smart friend, not a corporation. Warm, direct, confident.
- Every word must earn its place. Cut ruthlessly.
- Benefits before features. "Save 4 hours a week" beats "Automated reporting."
- The best microcopy is invisible — it prevents the question before it's asked.
- Use the user's language, not your internal jargon.
- Specificity builds credibility. "Join 12,847 teams" beats "Join thousands."

## Headline Formulas That Work

- **[Desired outcome] without [pain point]:** "Ship faster without breaking things"
- **[Action verb] your [noun]:** "Automate your workflows"
- **The [noun] for [specific audience]:** "The CRM for founders who hate CRMs"
- **[Specific result] in [timeframe]:** "Launch your landing page in 10 minutes"
- **Stop [pain]. Start [gain]:** "Stop chasing invoices. Start getting paid."

## Button & CTA Copy

- Use first person: "Start my free trial" not "Start your free trial"
- Be specific: "Create dashboard" not "Submit" or "Continue"
- Reinforce value: "Get my report" not "Download"
- Reduce anxiety: Add reassurance below CTAs ("No credit card required", "Cancel anytime", "Free for up to 3 projects")
- Destructive actions: Name the consequence. "Delete project" not "Delete". Confirmation: "This will permanently delete 'Acme Dashboard' and all its data."

## Error Messages (the most underrated copy in any product)

- Say WHAT happened in plain language.
- Say WHY it happened if it helps.
- Say HOW TO FIX IT — always.
- Never blame the user.

| Bad | Good |
|-----|------|
| "Invalid input" | "That email address doesn't look right — check for typos." |
| "Error 403" | "You don't have access to this page. Ask your team admin for permission." |
| "Something went wrong" | "We couldn't save your changes. Check your connection and try again." |

## Empty States

- Never leave a blank screen. Empty states are onboarding opportunities.
- Structure: [Illustration or icon] + [What this area is for] + [Single CTA to get started]
- Example: "No projects yet. Projects help you organize your work into focused streams. [Create your first project]"

## Onboarding Copy

- Welcome screen: Reinforce the value prop, not "Welcome to AppName."
  - GOOD: "Let's get your first dashboard live in under 5 minutes."
- Progress indicators: "Step 2 of 4 — Connect your data source"
- Skip options: Always let users skip. "I'll do this later" not just "Skip."
- Tooltips: One idea per tooltip. Under 15 words.

## Pricing Page Copy

- Plan names should signal audience: "Starter", "Team", "Business" not "Bronze", "Silver", "Gold" (which signal hierarchy, not fit).
- Highlight the recommended plan with "Most popular" or "Best for most teams."
- Feature lists: Lead with differentiators, not shared features.
- Use per-unit framing when it helps: "$8/user/month" feels smaller than "$80/month for 10 users."

## Notification & Alert Copy

- Toasts: 6-10 words max. "Project saved" or "Invite sent to 3 teammates."
- Confirmation dialogs: State the action and consequence clearly. "Delete 'Q4 Report'? This can't be undone."
- Success states: Celebrate briefly, then redirect. "You're all set. Your first report will be ready in about 2 minutes."

## Settings & Admin Copy

- Label everything as if the user has never seen it.
- Use helper text under form fields to explain implications.
- Toggle descriptions should state what ON means: "Email notifications — Receive an email when someone mentions you."

## Voice Calibration

- Casual moments (empty states, success, onboarding): Warmer, friendlier.
- Critical moments (errors, destructive actions, billing): Clear, calm, precise.
- Never use humor in error states or when the user might be frustrated.

## Output Format

When asked to write or review copy:

1. Provide the copy itself (ready to paste into code).
2. One line explaining the reasoning behind the word choice.
3. An alternative version if the context is ambiguous.

Overview

This skill helps you write high-converting microcopy for SaaS products: headlines, CTAs, button text, error messages, onboarding flows, empty states, and pricing pages. It applies proven headline formulas, microcopy best practices, and a benefit-first SaaS writing style to make UI text clearer and more persuasive. Use it to reduce user friction, increase conversions, and sound like a helpful product teammate.

How this skill works

I inspect the UI context, user intent, and desired outcome, then generate concise, specific copy ready to paste into your app. Each output includes the microcopy, a short rationale for the choice, and an alternative variation when context might differ. I follow core principles: clarity over cleverness, benefits before features, and voice calibration for critical vs casual moments.

When to use it

  • Writing headlines for landing pages, feature pages, or in-app panels
  • Creating CTAs and button labels that drive action and reduce anxiety
  • Drafting error messages, confirmations, and destructive-action warnings
  • Designing onboarding screens, tooltips, and empty states
  • Copying pricing, plan names, and notification text for clarity and trust

Best practices

  • Prioritize clarity: one idea per line, avoid jargon and ambiguity
  • Lead with user benefit, not product features or internal terms
  • Be specific and credible: use numbers, timeframes, or audience cues
  • Use first-person CTAs (e.g., "Start my free trial") and add reassurance under the CTA
  • In error states, say what happened, why (if helpful), and how to fix it
  • Calibrate voice: warmer for onboarding, neutral and precise for errors/billing

Example use cases

  • Transforming a vague "Submit" button into "Create my dashboard" with subtext "No credit card required"
  • Replacing "Something went wrong" with a helpful error: "We couldn't save your changes. Check your connection and try again."
  • Crafting a headline: "Launch your landing page in 10 minutes" using a clear outcome + timeframe formula
  • Designing an empty state: headline, short benefit line, and single CTA like "Create your first project"
  • Writing pricing plan names and a recommended-plan callout: "Starter", "Team"; badge "Most popular"

FAQ

Do you provide context-aware variants?

Yes — each piece of copy includes an alternate phrasing when the context or audience could change.

Will you match my product voice?

I calibrate tone based on the moment: warmer for onboarding and empty states, precise and calm for errors and billing.