Use this skill when the user wants to write long-form prose — blog posts, founder essays, build-in-public posts, About pages, newsletter intros, or origin stories. Also use when the user mentions 'blog post,' 'essay,' 'long-form,' 'founder voice,' 'build in public,' 'BIP post,' 'About page,' 'origin story,' or 'newsletter copy.' For microcopy and CTAs, see copywriting. For removing AI patterns from existing text, see humanize. For SEO articles, see seo-content. For content strategy and distribution, see content.
Use this skill when the user doesn't know what to work on next, asks 'what should I do?', wants to find high-value opportunities, or needs help deciding where to spend their time. Also use when the user mentions 'what should I do next,' 'what should I work on,' 'where should I focus,' 'find low-hanging fruit,' 'what's the most valuable thing I could do,' or 'I don't know what to do.' Scans the full project — code, infrastructure, marketing, growth, business — and surfaces 3-5 high-impact, low-effort opportunities ranked by value. Routes each recommendation to the right skill.
Use this skill to find and eliminate duplication across your codebase — UI components, database schema, and workflow logic. Also use when the codebase feels bloated, features take longer to build, changes break in unexpected places, or after significant AI-assisted development. Covers code deduplication, component reuse, database normalization, and modular architecture.
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).
Use this skill when the user is building software for a regulated industry and needs to understand compliance requirements. Also use when the user mentions 'HIPAA,' 'FERPA,' 'SOC 2,' 'PCI,' 'GDPR,' 'compliance,' 'regulated industry,' 'healthcare app,' 'fintech,' 'edtech,' or asks 'do I need to worry about [regulation]?' Covers what regulations mean for your tech stack — not legal theory, but concrete technical requirements.
Use this skill when the user needs to hire a developer, find a technical contractor, vet engineering talent, manage freelancers, write a job brief, decide between hiring and contracting, or bring on their first technical team member. Also use when the user says 'I need a developer,' 'should I hire someone,' 'how do I find a contractor,' 'I need technical help I can't do myself,' or 'AI keeps getting this wrong, I need a human.' Covers contractor sourcing, vetting, management, and the founder-developer working relationship for non-technical founders.
Use this skill to autonomously improve any other skill in solo-founder-superpowers. Point it at a skill (e.g., 'improve the seo skill') and it runs an autoresearch-style loop: diagnoses weaknesses, experiments with improvements, evaluates each change via A/B comparison, keeps winners, discards regressions, and reports results. Originals are always preserved — nothing changes until you approve.
Use this skill when the user needs to form a business entity, choose between LLC and C-Corp, create Terms of Service, write a Privacy Policy, or handle legal compliance. Covers entity selection, legal documents, contracts, and compliance for solo-founded SaaS.