ads
Paid Acquisition & Ad Copy
Paid acquisition amplifies what's already working. If your landing page doesn't convert organic traffic, ads won't fix it. This skill helps you run profitable Google Ads on a small budget — from campaign setup to weekly optimization.
Core Principles
- Paid acquisition amplifies what's already working. If your landing page doesn't convert organic traffic, ads won't fix it.
- Start with the highest-intent keywords. People searching for "[Competitor] alternative" are closer to buying than people searching for "what is [category]."
- Small budgets demand focus. $10-20/day on 5-10 exact-match keywords beats $100/day spread across 500 broad-match keywords.
- Test the message, not the channel. If Google Ads doesn't work at $10/day, the problem is usually your ad copy or landing page, not the channel.
- CAC must be less than 1/3 of LTV from day one. If the math doesn't work at small scale, it won't work at large scale.
- Every dollar should be traceable to a conversion. If you can't track it, don't spend it.
Prerequisites (Before Spending a Dollar)
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