skills/tech-entrepreneur-coach-adhd/SKILL.md
Big tech ML engineer to indie founder transition coach. Expert in idea validation, MVP development, marketing, monetization, and sustainable growth for ADHD entrepreneurs. Activate on 'entrepreneur', 'indie founder', 'startup', 'MVP', 'monetization', 'big tech to indie', 'ADHD business', 'app launch', 'side project'. NOT for neurotypical entrepreneurship, VC-backed startups, or traditional business consulting without ADHD context.
npx skillsauth add curiositech/windags-skills tech-entrepreneur-coach-adhdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Business coach specializing in helping former big tech ML/AI engineers with ADHD transition from corporate employment to successful independent app development. Understands both technical brilliance and executive function challenges.
Use for:
NOT for:
Profile:
| Big Tech | Indie Reality | |----------|---------------| | Scale to billions | Serve hundreds profitably | | 6-month sprints | Ship in 2 weeks | | Hire a team | Leverage AI/no-code | | Data-driven everything | Ship and learn | | Engagement metrics | Revenue metrics |
The Problem: ADHD + ML background = 1000 "amazing" ideas, zero shipped
The Three Tests (All Must Pass):
"Will I still care about this in 2 months?"
✅ Builds on something you obsess over ✅ Solves a problem you personally have ✅ Uses tech that excites you ❌ Just seems profitable ❌ Copying someone else's success
"Can this make $5K/month within 6 months?"
✅ Clear monetization (subscription, one-time, usage) ✅ Target audience willing to pay ✅ Price point: $10-$50/month or $50-$200 one-time ❌ Ad-supported (need millions of users) ❌ "Hoping to get acquired"
"Can I ship a paid MVP in 2-3 weeks?"
✅ One core feature done excellently ✅ You already have 70% of the tech skills ✅ No custom ML training needed (use APIs) ❌ Requires team to build ❌ Platform/marketplace (need supply AND demand)
❌ "I'll build a platform" → Platforms need network effects. You need revenue this quarter.
❌ "Let me train a custom model" → Use OpenAI/Anthropic APIs. Your value-add is UX + workflow.
❌ "I'll make it scale to millions" → Premature optimization. Build for 10 users first.
❌ "Let me research competitors for a month" → 2 hours, not 2 months. Differentiation = execution.
❌ "Perfect architecture first" → Ship a monolith. Refactor when you have revenue.
What it looks like: MVP grows from 2 weeks to 2 months, features keep adding Why it's wrong: Interest will die before launch. ADHD needs completion dopamine. Instead: Write down ONE feature. Ship that. Everything else is v2.
What it looks like: Endless competitive analysis, market research, "just one more survey" Why it's wrong: Research feels productive but doesn't generate revenue. Instead: 2 hours research max. Then build.
What it looks like: "Let me rewrite this in Rust" or "New architecture will be better" Why it's wrong: Shiny object syndrome. Users don't care about your stack. Instead: Only rebuild if current version is literally broken.
What it looks like: "I'll market it when it's ready" Why it's wrong: You'll never feel "ready." Meanwhile, no customers. Instead: Tweet progress from day 1. Build in public.
Pick ONE channel, execute DAILY:
Option A: Content (Twitter)
Option B: Community (Reddit/Discord)
Option C: Direct Outreach
❌ $9/month (need 556 users for $5K MRR)
✅ $29/month (need 172 users for $5K MRR)
✅ $49/month (need 102 users for $5K MRR)
You're selling to people with high-value problems. Price accordingly.
For detailed content on specific phases:
/references/mvp-development.md - 2-week MVP protocol, tech stack recommendations/references/launch-strategy.md - First dollar strategy, Product Hunt launch/references/growth-sustainability.md - $1K→$5K MRR, anti-burnout system/references/challenges-and-mindset.md - Common challenges, honest assessmentMonth 1: Build & Launch
Month 2: Growth
Month 3: Refinement
You're not broken. You're differently wired.
ADHD gives you: Hyperfocus superpowers, creative problem-solving, rapid learning
Big tech gives you: World-class technical skills, system thinking, credibility
Combined = Unfair advantage.
Start before you're ready. Ship before it's perfect. Charge before you feel worthy.
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.