返回提示词目录第 1310 页

开发者社区项目推广发帖规划

按项目受众筛选社区并核查推广规则,准备差异化帖子或提纲,安排分日发布与互动。

完整提示词

<context>
Developer communities welcome makers who participate and remove those who only drop links. Each community writes its own rules: some ban self-promotion outright, some allow it only on a set day or in a weekly thread, some require a flair, a minimum account age or karma, or a ratio of other participation to self-promotion, and some (such as Lobsters) are invite-only and expect authors to tag their own work. By 2026 many developer subreddits also ban AI-written post text, set a minimum project age (30 days or three months), require disclosed affiliation, or push project posts into a weekly thread or a set day; Reddit's own help pages give no fixed ratio, so the ratio rules that exist are per community. Reddit's site-wide rules forbid spam, vote manipulation and ban evasion, and posting the same link to many subreddits at once looks like spam to both moderators and filters. The communities that work best are the narrow ones where the project solves a problem people there actually have. A post that teaches something or tells a real build story does better than an announcement.
</context>

<task>
<project>
{{project}}
</project>
{{#candidate_communities}}
Candidate communities and rules:
{{candidate_communities}}
{{/candidate_communities}}
Post in at most {{max_communities}} communities.

If you cannot tell who the project is for, ask and stop.

1. **Shortlist.** Propose up to ten communities where this audience gathers (subreddits, Lobsters, language or framework forums, official Discord or Slack showcase channels, mailing lists), ranked by fit. For each, say who is there and why they would care. Prefer narrow, relevant communities over large general ones.
2. **Rules check.** For each shortlisted community, list what its rules say about self-promotion, required flairs, days or threads, minimum project age, account requirements (karma, age, prior participation), AI-written text and link versus text posts. Quote rules the user pasted. For rules you have not seen, write "UNVERIFIED: read the sidebar and rules page" and never guess them. Drop any community where self-promotion is banned or the user has no history and the rules require it.
3. **Posts.** For the top {{max_communities}}, write a post tailored to that community: a title in its style, a body that leads with the problem or a lesson, what the project does, honest limits, the license, the link, and a question that invites real discussion. Disclose "I built this" in the first lines. Vary the angle per community; never paste the same text twice. Where a community bans AI-written text, give the maker an outline with the facts and angle instead of finished prose, and say they must write it themselves.
4. **Schedule.** Space posts over one to two weeks, respecting any set days, with the best slot for each community's main time zones, and no more than one community per day so the maker can answer every comment.
5. **Do not post.** List communities that look tempting but would be a mistake, and why.
</task>

<constraints>
- Never suggest vote manipulation, asking friends to upvote, alternate accounts, posting as a "happy user", or cross-posting the same link to many communities at once.
- Never invent a community's rules; mark unverified rules clearly.
- Use only facts from the input; no invented users or numbers.
- If the license is not OSI-approved, do not call the project open source.
</constraints>

<output_format>
## Community shortlist
| Community | Audience | Why they would care | Fit |
## Rules check
| Community | Self-promotion rule | Flair, day or thread | Project age and account needs | AI text allowed? | Verdict |
## Posts
One section per community: title, body.
## Schedule
| Day | Community | Slot (time zone) |
## Do not post
</output_format>

可替换内容

  • {{project}}
  • {{#candidate_communities}}
  • {{candidate_communities}}
  • {{/candidate_communities}}
  • {{max_communities}}

分类与标签

商业营销、项目推广、开发者社区、社区规则、发帖排期

前往 AI 图片创作