A Claude Code skill + field guide
Get your first 100 users
You shipped it. Nobody came. Six Claude Code skills install into your repo, read what you actually built, and take you from “who is this even for” to the posts written — in order, one step at a time.
One-time·instant download·14-day refund, no questions
100 Users
Product Context
Step one reads a repo it has never seen — and tells you what it thinks you built.
- 1. Has anyone outside you uploaded a real file?
- 2. Why did you build this over a spreadsheet?
It isn’t a marketing problem.
It’s an ordering problem.
You’ve half-heard about fifteen things. Product Hunt, Reddit, SEO, cold DMs, build in public, Show HN. Every one sounds plausible, so you do none of them — or you do all of them badly for a week and decide you’re bad at this.
You are not bad at this. You just have no sequence.
Six steps, in order
Each one reads what the last wrote and adds a file to a distribution/ folder in your repo. Step 4 ranks channels properly because it’s reading a real audience, not guessing at one.
Product context
Reads your repo — routes, schema, landing copy, recent commits — and writes down what your product actually is.
The specific person
Narrows to one group so specific you can name three real places they already gather.
Positioning
The sentence someone can repeat. The wedge. The one number that means it’s working.
The channel test
Three channels to test — and every other one ruled out, with a reason specific to your app.
The assets
Drafts the actual posts. Show HN, Reddit, build-in-public, outreach DMs. Publishable, not templated.
The weekly read
Every Friday, thirty minutes. Keep, kill, or double down. Then one action for next week.
It tells you no
Anything can generate a list of marketing ideas. The useful part is being told which ones are wrong for your app, before you spend three weeks finding out.
Step 4 rules channels out with reasons drawn from your own repo and your own constraints. Step 6 will tell you a week was a dud rather than calling it “early signal.”
A tool that agrees with everything you already wanted to do was free.
The Channel Test
Three channels to test — and the rest ruled out, with a reason from your own repo.
People post this exact problem weekly. Your wedge is one sentence and needs no demo.
Kill criteria: no real upload in a week → move to test 2.
A guide, and a kit that does the work
The guide is the thinking — why this order, what a real signal looks like. The skills are the doing. Here’s what they actually do for you.
It reads before it asks
Your routes, your schema, your landing copy, your last few weeks of commits. Then it tells you what it thinks you built and asks you to correct it — instead of making you describe your own app.
It finds people you can reach
Not “developers.” One group so specific you can name three real places they already gather. Reachable by one person with no budget and no audience.
It tells you no
Step 4 rules channels out with reasons from your own repo. Step 6 calls a dud a dud. A tool that agrees with everything you already wanted was free.
It writes the actual posts
Show HN, Reddit, build-in-public, outreach DMs — drafted from what you shipped, ready to edit and post. Not templates with brackets to fill in.
100 Users
Everything you need to get to a hundred
A 21-page field guide
One section per step. The thinking behind the order, and how to read a channel test honestly.
Six Claude Code skills
Install into your repo. Each reads what the last wrote and adds a file to distribution/.
For apps you’ve already shipped
It starts from a working repo and real commits — not a blank page or a business plan.
Instant, one-time download
Open it and start in minutes. No subscription, no login, no seat you have to keep paying for.
Don’t buy this if
- You haven’t shipped anything yet. There’d be no repo to read, and the sequence starts from a working app.
- You don’t use an agentic coding tool. The skills need something that can read files in your project.
- You want a growth-hacking playbook. There’s no chapter on viral loops, because you don’t have one yet.
- You want someone to do it for you. This tells you what to do and drafts it. You still have to press post.
Questions
A 21-page PDF guide and six skills you copy into your repo. The guide is the thinking — why this order, what a real signal looks like. The skills do the work.
An agentic coding tool that reads instruction files from your repo — Claude Code, Cursor, or similar — and an app you’ve already shipped. If you haven’t shipped yet, this is the wrong time to buy it.
A blank chat gives you fifteen channels and no order. This gives you a sequence, constraints baked into every step (solo, no budget, no audience), and a step built to tell you a channel is wrong for you. That last part is what you’re paying for.
Yes — and it will say so plainly rather than inventing users to fill the gap. Your positioning gets marked unvalidated, and the first channel test becomes a test of your sentence as much as your channel.
Steps 1 to 3 take an afternoon. Step 4 takes an hour. Step 5 an hour per channel. Then thirty minutes every Friday, which is the part that actually gets you to a hundred.
14 days, no questions. Email us and it’s done. You keep the files.
Start with step one
It reads your repo and tells you what it thinks you built. You’ll know within two minutes whether this is worth the $29.
Instant download · 14-day refund, no questions
