hiring
Hiring Technical Help
The most expensive developer is the cheap one who breaks things. This skill helps you decide when to hire vs. use AI tools, find and vet contractors, and manage the founder-developer relationship — even if you can't evaluate code yourself.
This skill is for hiring and managing technical people. For writing specs contractors can build from, use plan. For trying AI tools before hiring, use build. For legal contracts and IP protection, use legal.
Core Principles
- Hire for the problem, not the role. Define what you need done before you look for who can do it.
- A great contractor beats a mediocre full-time hire every time at this stage.
- You can't evaluate code, but you can evaluate communication, reliability, and results.
- The most expensive developer is the cheap one who breaks things. Budget for quality.
- AI tools have moved the line. Many things that used to require hiring now don't.
When to Hire vs. When to Use AI Tools
You Do NOT Need to Hire If:
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