Describe the project and who it is for. You get a launch plan built for it: what to fix first, which communities fit and which to skip, a dated checklist, draft outlines for each channel and what to measure instead of stars. No signup, and nothing is posted for you.
By published rules, not a language model, so the same answers always produce the same plan and nothing is invented about your project.
Start from the people, not the platforms. Write down who has the problem your project solves and where they already ask about it: the forum or chat of the language or framework you build on, the subreddit where the problem comes up, the newsletter they read. A small community where the problem is discussed every week is worth more than a large general one.
Then read each one before posting. Look at the rules, the posts that did well and the ones that were removed. The planner suggests where to look for your category and audience; it does not know any community's current rules, so it always tells you to check them.
Post where the project genuinely fits, one community at a time, written for that community, and stay to answer questions. Share the problem and what you learned, not only a link. Take part in a community before you post your own work there, and never ask for upvotes.
Use several signals, because no single one measures use. Package downloads and dependents show installs, GitHub's traffic page shows which sites sent visitors, and issues and discussions opened by people you do not know show someone tried it. Stars are a cheap bookmark: worth watching as a trend, not as the goal.
From fixed rules, not a language model. Each channel has a rule that rates its fit for your category, audience and objective as strong, later, or not recommended, and the readiness list, checklist and measurements change with your objective. If you give a public repository, its README is checked with the README quality checker and readiness items are marked done or to do from what it actually contains.
No to both. It never posts: drafts are outlines for you to finish, check and post yourself. What you enter is used to build the plan and is not saved.
Related: the best communities for open-source projects · the open-source launch checklist · GitHub stars vs active users · check readiness locally with your coding agent (Orviqa Lite)