Generates headlines, CTAs, button text, error messages, onboarding copy, and UI text using headline formulas, microcopy best practices, benefit-driven writing, and SaaS styles. Activates for copy requests or UI text needs.
npx claudepluginhub whawkinsiv/solo-founder-superpowers --plugin solo-founder-superpowersThis skill uses the workspace's default tool permissions.
Words are interface elements. They reduce confusion, build trust, and drive action. This skill helps you write copy for every surface of your product — from headlines to error messages.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Words are interface elements. They reduce confusion, build trust, and drive action. This skill helps you write copy for every surface of your product — from headlines to error messages.
If
ABOUT-ME.mdand/orMY-ICP.mdexist in the project root, read them before writing. Use ABOUT-ME.md for voice and tone — write like the founder. Use MY-ICP.md for message framing — speak to the customer's pain in their language. When both exist: the founder's voice delivers the customer's message.
- [ ] Identify what you're writing (headline, CTA, error, empty state, etc.)
- [ ] Define the ONE job this copy has (inform, persuade, reassure, guide)
- [ ] Write a draft using the patterns below
- [ ] Review against the voice checklist
- [ ] Test: read it aloud. If it sounds stiff, rewrite.
Formulas that work:
Tell AI:
Write 5 headline options for our [page type]:
- Product: [what it does]
- Audience: [who it's for]
- Main benefit: [what they get]
- Use these formulas: outcome without pain, specific result in timeframe, the X for Y
- Make each under 10 words
- Show the strongest option first with reasoning
Tell AI:
Write CTA copy for our [signup / pricing / feature] page:
- Primary action: [what the user does]
- Current CTA text: [what it says now]
- Anxiety reducers needed: [credit card concern, commitment concern, etc.]
- Give me 3 options: safe, bold, and playful
- Include the helper text that goes below the button
The most underrated copy in any product.
| 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." |
Tell AI:
Write error messages for these scenarios in our app:
1. [Form validation failure — what field, what's wrong]
2. [API/network error — what the user was trying to do]
3. [Permission error — what they tried to access]
4. [Not found — what they were looking for]
For each: plain language, no blame, include how to fix it.
Follow this pattern: What happened + Why (if helpful) + How to fix it.
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]"
Tell AI:
Write empty state copy for these screens:
1. [Screen name — what it shows when populated]
2. [Screen name — what it shows when populated]
3. [Screen name — what it shows when populated]
For each: one sentence explaining what this area is for + one CTA button text.
Keep it encouraging, not sad. The user just got here — show them the path forward.
Tell AI:
Write onboarding copy for our setup wizard:
- Product: [what it does]
- Steps: [list 3-5 setup steps]
- Aha moment: [when the user first gets value]
For each step: headline (under 8 words), description (under 25 words), button text.
Welcome screen should promise a quick win, not just say "Welcome."
Include skip option text for optional steps.
See pricing skill for tier design and pricing strategy.
Before shipping any copy:
- [ ] Can a stranger understand this without context?
- [ ] Is every word earning its place? (cut filler)
- [ ] Benefits before features?
- [ ] Specific rather than vague?
- [ ] Active voice, not passive?
- [ ] Reads naturally aloud?
- [ ] Matches the moment's tone (casual vs. critical)?
| Mistake | Fix |
|---|---|
| "Get started" on every button | Name the specific action: "Create project", "Send invite" |
| Clever headline nobody understands | Test: would a stranger get it in 5 seconds? |
| "Something went wrong" errors | Say what happened and how to fix it |
| Empty screens with no guidance | Every empty state is an onboarding opportunity |
| Corporate voice ("We are pleased to...") | Write like a human. "Here's what happened." |
| Same CTA copy everywhere | Match CTA to the specific value of each page |