返回提示词目录第 1484 页

项目目录收录筛选与投稿规划

核对项目资质与各类目录的收录规则,筛选合适渠道,整理投稿文案、提交顺序和跟进安排。

完整提示词

<context>
Curated lists and directories bring a slow, steady stream of qualified visitors and links, but only when the project fits and the submission follows the rules. Awesome lists usually require a specific line format, alphabetical or category placement, a description that is not marketing, and often a minimum age, activity level or star count; many lint submissions automatically, and some accept only projects under OSI-approved licenses. Package managers have their own bars (Homebrew, for example, has notability criteria; Flathub and winget have manifest and review requirements). Self-hosting and "alternatives" directories check license and hosting model. Several lists and package repositories now ban machine-generated submissions, so the maintainer should write the final entry text themselves. Maintainers of these lists are volunteers; a submission that ignores their template, duplicates an entry or oversells the project is closed and remembered.
</context>

<task>
<project>
{{project}}
</project>
{{#known_targets}}
Already known or submitted:
{{known_targets}}
{{/known_targets}}

If you cannot tell the project's category, license and platforms, ask and stop.

1. **Qualification facts.** List the facts that decide eligibility: license and whether it is OSI-approved, first release date, latest release, stars, platforms, packaging status, docs, and whether the project is a library, app, CLI or service.
2. **Find targets.** Search for up to {{max_targets}} relevant targets across: awesome lists for the category, language, framework and platform; package registries and app stores the project could be in; developer-tool directories and alternatives sites; ecosystem showcases (a framework's showcase page, a marketplace). For each, open the list itself and its contributing guide. Record the URL, the maintainer activity (last merged submission), the inclusion criteria quoted from the guide, and the required format.
3. **Qualify.** Mark each target qualifies, not yet (and what is missing, such as age or stars) or no (such as license). Never mark one as qualifying on a guess; if you could not read the rules, mark it UNVERIFIED.
4. **Entry lines.** For each qualifying target, write the exact line or form text in that target's format: name, link, and a plain, factual description in the list's style and length, with no superlatives.
5. **Order of work.** Sequence the submissions: package managers and registries first (they make installs easier), then the most relevant and active lists, then directories. One submission per target; note how to follow up politely once if there is no response after the time the guide states, or after a month.
6. **Skipped.** Targets you found but excluded, and why.
</task>

<constraints>
- Never suggest submitting to lists the project does not qualify for, re-submitting after a rejection without changes, or asking others to submit on the project's behalf to look independent.
- Quote inclusion criteria from the source; mark anything not read as UNVERIFIED.
- Do not open pull requests or submit forms; produce the plan and texts for the maintainer.
- Disclose in each submission that the submitter maintains the project when the list asks or the format allows.
- Where a target bans AI-generated submissions, present the entry line as a draft for the maintainer to rewrite and check, not as final text.
</constraints>

<output_format>
## Qualification facts
## Targets
| Target | URL | Type | Criteria (quoted) | Format | Activity | Verdict |
## Entry lines
One block per qualifying target.
## Order of work
| # | Target | Action | Follow-up date |
## Skipped
</output_format>

可替换内容

  • {{project}}
  • {{#known_targets}}
  • {{known_targets}}
  • {{/known_targets}}
  • {{max_targets}}

分类与标签

商业营销、项目推广、目录收录、开源清单、投稿规划

前往 AI 图片创作