How Claude got its users

Anthropic's way into dev rooms was free forkable repos with no signup: anthropics/claude-cookbooks (runnable notebooks for real tasks) and anthropics/prompt-eng-interactive-tutorial (nine chapters, as Jupyter or Google Sheets). People paste those links into Discords and subreddits because they answer the exact question in the thread. Make one runnable file for the question your niche keeps re-asking, put your product link inside the repo README, and let other people do the linking.

done whenA stranger forks your file and posts their result in a thread you did not start. If traffic to the repo comes only from links you posted yourself, it answers your question, not the room's.

github.com/anthropics/claude-code ships no product source. It is a README, a CHANGELOG.md, examples, and a public issue queue, and the /bug command inside the CLI files straight into it. Users report, then watch the changelog for their own fix. Copy the shape: a public repo for a closed product, one in-product command that files the report for the user, and changelog entries that name the issue they close.

done whenBug reports start arriving with version numbers and repro steps without you asking for them. If you are still getting 'it's broken' in DMs, the in-product report path does not exist yet.

The biggest Claude room, r/ClaudeAI, is community-run, and Anthropic neither operates nor moderates it. Its rules route account problems to support.anthropic.com instead of dumping them on the mods. That is what a moderator tolerates: a vendor who supplies release notes worth linking and absorbs the support load somewhere else. Show up in the technical threads, post the changelog, and never make the mod your front line.

done whenA moderator links your changelog or docs on their own initiative. If every mention of you in that room is a post you wrote, you are a marketer in there, not a resident.

Anthropic published MCP as a spec plus SDKs plus reference servers, so anyone could ship a connector under their own name, then donated the protocol to the Agentic AI Foundation. Claude Code repeats the pattern: submit at clau.de/plugin-directory-submission, pass automated security scanning, land in anthropics/claude-plugins-community, which syncs nightly and auto-closes direct PRs. Publish your format and one reference build, then one submission door with one automated check.

done whenExtensions built by other people outnumber the ones you built, and your review queue contains at least one rejection. Zero submissions means the format is too hard to build against; zero rejections means nobody is trying.

Claude Builder Clubs are student-led chapters where the lead runs workshops with Anthropic guest speakers, plus hackathons and demo nights, hands API credits to members, and takes a paid stipend from Anthropic. The stipend and the credits need money you may not have. The no-budget version: find the one person already answering questions about your category in a room, give them early access plus a workshop outline, and let the event run under their name, not yours.

done whenSomeone runs a session about your product in a room you are not in and tells you after the fact. If nothing happens unless you are present, you have attendees, not organizers.