support
Customer Support & Documentation
The best support interaction is the one that never happens. This skill helps you build self-serve documentation that eliminates tickets, set up efficient support workflows, and scale from 10 to 10,000 customers without a support team.
Core Principles
- The best support interaction is the one that never happens. Invest in self-serve before staffing.
- Documentation is not a chore — it's the highest-leverage support tool you have. One good help article prevents thousands of tickets.
- Support is research. Every ticket reveals a product flaw, a UX failure, or a documentation gap. Track and fix the root cause, not just the symptom.
- Tone matters more than speed. A warm, helpful reply in 4 hours beats a robotic auto-response in 4 seconds.
- A solo founder can support 500+ customers if the product, docs, and onboarding are good. If support is crushing you at 50 customers, the product has problems.
Minimal Support Setup
What You Need at Launch
Tier 1: Absolute minimum (launch day)
- Contact email (support@yourdomain.com) routed to your inbox
- 5-10 FAQ entries on a /help or /faq page
- In-app "need help?" link that opens email compose
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