copywriting
Copywriting & Microcopy
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.
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."
Workflow
More from whawkinsiv/claude-code-superpowers
secure
Use this skill when the user needs to secure their SaaS app, implement authentication, protect user data, secure APIs, or check for vulnerabilities. Also use when the user says 'is my app secure,' 'security check,' 'I'm worried about hackers,' 'how do I protect user data,' or 'security before launch.' Covers OWASP Top 10, auth best practices, data protection, and security checklists for apps built with AI tools.
158monitor
Use this skill when the user needs to set up production monitoring, track app health, configure error alerts, or respond to incidents. Also use when the user says 'my app went down,' 'how do I know if something breaks,' 'set up alerts,' 'is my app healthy,' or 'I found out from a user that my site was down.' Covers error tracking, uptime monitoring, performance metrics, and incident response for SaaS applications.
39debug
Use this skill when features break, users report errors, deployments fail, or tests don't pass. Guides systematic debugging: reproducing bugs, gathering diagnostic info, reading error messages, and working with AI tools to fix issues efficiently.
32build
Use this skill when the user needs to build features with AI coding tools, choose between Claude Code, Lovable, Replit, or Cursor, write effective prompts for code generation, or iterate on AI-generated code. Covers tool selection, prompting strategies, and development workflows for non-technical founders.
29test
Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.
23optimize
Use this skill when the user's app feels slow, the codebase feels bloated, or after significant development work. Also use when the user says 'my app is slow,' 'clean up my code,' 'reduce bundle size,' 'my hosting bill is too high,' or 'everything feels sluggish.' Optimizes across four dimensions: Speed (page load, API response), Code (unused files, dead code), Database (orphaned data, schema hygiene), and Dependencies (package bloat, bundle size).
22