撰写开源项目发布介绍
根据项目资料撰写面向目标读者的发布文章,呈现项目用途、示例、成熟度、维护安排和发布准备情况。
完整提示词
<context>
A launch post is the one long piece that introduces a project to strangers. Readers decide within the first screen whether to try it. Launch posts lose them in a few common ways. Some open with the author's journey. Some pile up adjectives instead of showing code. Some hide what is unstable until a reader runs into it, or compare unfairly with alternatives. Some never say who maintains the project or for how long, and some send readers to a repository that is not ready for visitors, with an empty README, no license file and no issue templates. A project released by a company faces harder questions: why release it now, what was removed, whether the company will keep investing, and who decides what gets merged. Release announcements for later versions and per-network social posts are separate jobs; this prompt writes the first introduction.
</context>
<task>
Write the launch post for this project, aimed at {{audience}}. Origin: {{origin}}.
<project>
{{project}}
</project>
1. Open with the problem as {{audience}} experiences it, in one or two sentences. Follow with one sentence on what the project does about it.
2. Show it working within the first screen: the install command and the shortest real snippet that shows the core value, with its output where useful. Use only commands and APIs found in the project details. If there are none, put a clearly marked placeholder and list it under Facts to confirm.
3. Explain in a short paragraph how it works or what it does differently. Compare with named alternatives only where the details support it. Keep the comparison specific and fair, and say when an alternative is the better choice.
4. State maturity honestly: what is stable, what is experimental, known limits, supported versions or platforms, and the license in plain words (for example "MIT: use it commercially, keep the notice").
5. Say who maintains the project and what they can commit to, such as response times, release rhythm or "maintained in spare time". If the details do not say, add a placeholder and list it under Facts to confirm. A launch that implies support nobody will give does lasting damage.
6. Address what the origin raises:
- new-project: why it exists alongside what is already out there, and what feedback you most want.
- company-internal-tool: why the company is releasing it, what was removed or changed for the public version, how internal and public development stay in sync, and who reviews outside contributions.
- formerly-closed-product: exactly what is open and what stays proprietary, the license and whether contributions need a CLA or DCO, and what existing customers should expect. Do not call the project open source if the license in the details is not an open-source license. Say "source-available" and flag it.
7. End with how to take part: try it, report issues, good first issues or the contributing guide, and where discussion happens.
8. Write a reusable summary in two or three plain sentences. The author can reuse it in social or community posts.
9. Check launch readiness against the details: the README's first screen matches the post's example, a license file exists, contribution and conduct guidelines exist, issue templates and good-first-issue labels are set up, the discussion channel exists, and there is a security contact. Mark each item ready, missing or unknown.
10. Before answering, check every claim in the post against the project details. This covers numbers, benchmarks, compatibility, adopters and comparisons. Move anything unsupported to Facts to confirm and keep it out of the text.
</task>
<constraints>
- No hype adjectives or superlatives without evidence, and no emoji.
- Never invent benchmarks, adopters, quotes, stars, download numbers or maintainer commitments. If the author asks for them, leave them out and say why in Facts to confirm.
- The launch post should take about three to four minutes to read, roughly 600 to 900 words.
- Do not write per-network social posts or a changelog. Say in one line that they belong in separate pieces.
</constraints>
<output_format>
## Title options
Three titles: plain, problem-led and example-led. No clickbait.
## Launch post
The post in Markdown with short sections, ready to publish once the placeholders are filled.
## Reusable summary
Two or three sentences.
## Launch readiness
| Item | Status (ready, missing, unknown) | What to do |
## Facts to confirm
Claims, placeholders and requests the author must settle before publishing, or "None".
</output_format>可替换内容
- {{audience}}
- {{origin}}
- {{project}}
分类与标签
内容创作、开源发布、项目介绍、技术写作