Pot să vibecodez SubSignal?

Ce construiești

Poll a list of subreddits on a schedule, filter new posts by keyword, ask one model whether each is a buying signal for your product, and send the hits to Slack or email.

ce îți trebuie

• Reddit API credentials, within Reddit's terms of use
• OpenAI or Anthropic API key in .env
• Node.js 22 and a scheduler such as cron
• SQLite to remember what you have already seen

The polling loop is an evening of code. The moat is a years-deep Reddit archive you cannot backfill from the live API.

Promptul

Verdictul e NU CHIAR, iar promptul rămâne oricum: nu înlocuiește aplicația, reconstruiește partea care chiar e cod. Restul e moat-ul.

Build a Reddit buying-signal monitor inspired by SubSignal.
Use exactly this stack: Node.js 22 + TypeScript + SQLite.
Primary job: on a schedule, fetch new posts and comments from a configured list of subreddits, ask one language model whether each one describes a problem the user's product solves, and deliver the matches to Slack or email with a link and a one-line reason.
Start from an empty folder and create the complete working project.
Use the official Reddit API with credentials from .env and respect its rate limits and terms of use; never scrape around them.
Store every item you have seen in SQLite so the same thread is never delivered twice, including across restarts.
Let the user describe their product in plain language in a config file, and build the classification prompt from that rather than from a hardcoded keyword list.
Score each match and let the user set a threshold, so the digest can be tightened without code changes.
Send a digest rather than one alert per hit, and make the schedule configurable.
Alert the user when a run fails or returns nothing for several consecutive runs - a silent crawler is the main failure mode of this kind of tool.
Put every secret in .env and provide .env.example.
Deliberately exclude these paid-product advantages: a curated subreddit and keyword set, accumulated cross-customer history, managed uptime.
Do not fake integrations, deliverability or data you do not have.
Write unit tests for deduplication and scoring, and one end-to-end smoke test against recorded fixtures rather than the live API.
Create a README with setup, Reddit API terms, cost estimate, architecture and limitations.
Run the tests and build before finishing, then fix what fails.

Ce pierzi

• a historical archive you cannot backfill from the live API
• ranking a lead against everything seen before, instead of judging it alone
• a curated subreddit and keyword set you did not have to discover
• deduplication and history across runs
• someone tracking Reddit API terms and rate-limit changes for you

De ce se plătește în continuare

Because relevance comes from history. Judging a single post in isolation is what a prompt does; knowing that this complaint has surfaced eleven times this quarter and twice from the same team requires an archive. You can start collecting today and be useful in a year, or pay for the year someone else already spent.

moat: Date proprietare Scara infrastructurii ce e un moat

accumulated historical corpus at terabyte scale

Alternative gratuite

N-ai chef să ți-o construiești? Astea există deja, sunt gratuite sau open source, și le-am verificat una câte una.

Cine l-a construit deja

Să pornești de aici e tot vibecoding: promptul e pentru când o vrei exact în felul tău.

• PRAW (se deschide într-o filă nouă) — Python Reddit API wrapper; the standard way to poll subreddits.
• Huginn (se deschide într-o filă nouă) — Self-hosted agents that watch feeds and act on events.
• changedetection.io (se deschide într-o filă nouă) — Self-hosted change monitoring with notifications.

Ești de acord?