Skip to content

2104178150-ai/megaphone / skills/launch-posts

launch-posts

Verified

Pick the channels where a project's audience actually is — developer communities for developer tools, the platforms end users already browse for apps, plugin directories for extensions — and prepare a rule-checked draft for each, or, where the platform wants the author's own words (Show HN, a DEV launch article, Lobsters, V2EX, 掘金 articles and 沸点, awesome lists that refuse LLM-written entries), a fact sheet the author writes from: Show HN, Reddit, Product Hunt, X/Twitter, DEV, Lobsters, awesome lists, newsletters, V2EX, HelloGitHub, 阮一峰科技爱好者周刊, 即刻, 小红书, 掘金, 知乎, B 站 and more. Use when the user wants to announce or promote a project or app, write a Show HN / Reddit / Product Hunt post, or says 写推广文案 / 发帖推广 / 发 V2EX / 投稿 HelloGitHub / 小红书怎么发.

FileKindSize
SKILL.mdskill md13.3 KB
channels/README.mdmarkdown7.1 KB
channels/awesome-lists.mdmarkdown4.4 KB
channels/china-other.mdmarkdown10.2 KB
channels/dev-blogs.mdmarkdown3.6 KB
channels/ecosystems.mdmarkdown14.8 KB
channels/github-native.mdmarkdown4.8 KB
channels/hacker-news.mdmarkdown7.4 KB
channels/hellogithub.mdmarkdown4.4 KB
channels/jike.mdmarkdown3.0 KB
channels/juejin.mdmarkdown6.0 KB
channels/lobsters.mdmarkdown3.1 KB
channels/newsletters.mdmarkdown5.1 KB
channels/product-hunt.mdmarkdown4.5 KB
channels/reddit.mdmarkdown6.1 KB
channels/ruanyf-weekly.mdmarkdown3.0 KB
channels/v2ex.mdmarkdown8.4 KB
channels/x-twitter.mdmarkdown4.1 KB
channels/xiaohongshu.mdmarkdown7.8 KB

channels/lobsters.md

View on GitHub
# Lobsters

> Last checked: 2026-10-18 against the [about page](https://lobste.rs/about), the
> [tag list](https://lobste.rs/tags) and the submit form in Lobsters' source
> ([`_form.html.erb`](https://github.com/lobsters/lobsters/blob/main/app/views/stories/_form.html.erb),
> [`story.rb`](https://github.com/lobsters/lobsters/blob/main/app/models/story.rb)).
> Lobsters is invite-only; you need an existing member to invite you.

## Fit

A small, highly technical community focused narrowly on computing. Deep technical
write-ups, programming-language and systems work do well. Marketing and product
announcements do badly. The about page's test for a good story: "Will this improve the
reader's next program?"

## Rules (from the about page)

- **Topicality**: computing only. Entrepreneurship, management and company news are off
  topic.
- **Tags** are required, from a predefined list. Your own project goes under `show`
  ("Show Lobsters / Projects"); a release under `release`; plus one or two topic tags.
- **Self-promotion is limited.** Authors are welcome, but not "as a write-only tool for
  product announcements or driving traffic to their work". Rule of thumb: self-promo
  should be **less than a quarter** of your stories and comments. Tick "I am the author of
  the story at this URL (or this text)" when submitting your own work.
- **New users** (first 70 days) can't send invites, can't submit links to domains the
  site hasn't seen before, and **can't use some tags, including `show`**. A new account
  can't post a Show Lobsters.
- **Spam flag**: for content "designed to promote a commercial service" or "created
  without meaningful human authorship". Write the title and comment yourself.
- **Invitations**: the quickest way is to talk to someone you recognise from the site; if
  something you wrote was posted there, the about page asks you to reach out in chat.
  Inviters are accountable for the people they invite — don't put a friend in a spot by
  spamming.

## Format

- Link to a technical article or the repo.
- Title: plain and descriptive, 150 characters at most; the form asks you to remove site
  and author names.
- If you're the author, a short comment explaining the motivation and the interesting
  technical part is welcome.

## Timing

No official guidance and no reliable data; it's a small site. Post when you can answer
comments for a few hours, and not on the same day as your Show HN if you can't follow
both (heuristic).

## Template

```
URL:    <technical write-up, or the repo>
Title:  <Name>: <what it does, plainly>        (≤ 150 chars, no site/author name)
Tags:   show + 1–2 topic tags (e.g. rust, go, unix)
[x] I am the author of the story at this URL (or this text)

Comment (the author's own words, optional):
Why you built it, the interesting technical decision, what you'd like feedback on.
```

## Pitfalls

- Posting a product launch rather than something technically interesting.
- Asking for an invite just to promote your project.
- Expecting to post `show` from a new account → not allowed for the first 70 days.
- An account whose activity is mostly your own links → over the quarter rule of thumb.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall