Vibecode IdeaFast

You are building a lean indie version of IdeaFast.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# IdeaFast indie build

## Goal

Build the smallest trustworthy replacement for the core IdeaFast workflow for one developer or a tiny team.

## Scope

Pull posts and comments from a handful of public subreddits, classify complaints with an LLM, cluster them into named pain themes, and rank them with clickable quote evidence.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- community discovery, you can only scan subreddits you already thought of
- cross-scan dedupe, so repeat runs resurface the same pains as if they were new
- a warmed corpus, every fresh scan pays the full ingestion wait
- cost control, naive LLM classification of a busy subreddit gets expensive fast
- the idea generation and validation layer on top of the raw clusters

If those capabilities are essential, use PRAW instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a Reddit pain finder: a local CLI plus a small dashboard that reads public
Reddit and turns complaints into ranked pain themes with clickable evidence.

- TypeScript on Node 22, SQLite via better-sqlite3, Hono for the dashboard. One
  repo, one `npm run scan` entrypoint. No accounts, no cloud, no telemetry.
- Input: subreddits.txt plus a timeframe flag (default 90 days). Fetch posts and
  top level comments from Reddit's public JSON endpoints, for example
  https://www.reddit.com/r/<sub>/top.json?t=year. One request every 2 seconds, a
  real descriptive User-Agent, and cache every raw response in SQLite so re-runs
  cost nothing. No OAuth, no logged-in scraping.
- Prefilter to complaint-shaped text with cheap regexes ("I hate", "why is there
  no", "wasted hours", "workaround", "gave up on") before spending a single
  token. This is the whole cost story, do it first.
- Classify survivors with Claude (ANTHROPIC_API_KEY in .env, batched, cached by
  content hash) into: is_pain, severity 1 to 5, one line summary.
- Cluster: embed the summaries, group at cosine similarity above 0.82, then have
  Claude name each cluster and pick its 5 strongest verbatim quotes with
  permalinks. Never paraphrase a quote, evidence has to be clickable or it is
  worthless.
- Score each cluster as frequency x mean severity x recency decay, and persist
  scores per run so a later scan can show what moved.
- Dashboard on localhost:3000: ranked clusters, expandable quotes with permalinks,
  filter by subreddit, CSV export.
- README: how to choose subreddits, the rate limit rule and why breaking it gets
  you blocked, and rough token cost per 1000 comments.
- Out of scope: sources other than Reddit, idea generation, and cross-scan dedupe.
  Get one subreddit list producing clusters you actually trust first.

## Required capabilities

- Anthropic or OpenAI API key
- embedding model
- SQLite
- patience with Reddit rate limits

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of IdeaFast.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# IdeaFast indie build

## Goal

Build the smallest trustworthy replacement for the core IdeaFast workflow for one developer or a tiny team.

## Scope

Pull posts and comments from a handful of public subreddits, classify complaints with an LLM, cluster them into named pain themes, and rank them with clickable quote evidence.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- community discovery, you can only scan subreddits you already thought of
- cross-scan dedupe, so repeat runs resurface the same pains as if they were new
- a warmed corpus, every fresh scan pays the full ingestion wait
- cost control, naive LLM classification of a busy subreddit gets expensive fast
- the idea generation and validation layer on top of the raw clusters

If those capabilities are essential, use PRAW instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a Reddit pain finder: a local CLI plus a small dashboard that reads public
Reddit and turns complaints into ranked pain themes with clickable evidence.

- TypeScript on Node 22, SQLite via better-sqlite3, Hono for the dashboard. One
  repo, one `npm run scan` entrypoint. No accounts, no cloud, no telemetry.
- Input: subreddits.txt plus a timeframe flag (default 90 days). Fetch posts and
  top level comments from Reddit's public JSON endpoints, for example
  https://www.reddit.com/r/<sub>/top.json?t=year. One request every 2 seconds, a
  real descriptive User-Agent, and cache every raw response in SQLite so re-runs
  cost nothing. No OAuth, no logged-in scraping.
- Prefilter to complaint-shaped text with cheap regexes ("I hate", "why is there
  no", "wasted hours", "workaround", "gave up on") before spending a single
  token. This is the whole cost story, do it first.
- Classify survivors with Claude (ANTHROPIC_API_KEY in .env, batched, cached by
  content hash) into: is_pain, severity 1 to 5, one line summary.
- Cluster: embed the summaries, group at cosine similarity above 0.82, then have
  Claude name each cluster and pick its 5 strongest verbatim quotes with
  permalinks. Never paraphrase a quote, evidence has to be clickable or it is
  worthless.
- Score each cluster as frequency x mean severity x recency decay, and persist
  scores per run so a later scan can show what moved.
- Dashboard on localhost:3000: ranked clusters, expandable quotes with permalinks,
  filter by subreddit, CSV export.
- README: how to choose subreddits, the rate limit rule and why breaking it gets
  you blocked, and rough token cost per 1000 comments.
- Out of scope: sources other than Reddit, idea generation, and cross-scan dedupe.
  Get one subreddit list producing clusters you actually trust first.

## Required capabilities

- Anthropic or OpenAI API key
- embedding model
- SQLite
- patience with Reddit rate limits

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of IdeaFast.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# IdeaFast product brief

## Problem

The pipeline is honest work an agent can do: pull public Reddit JSON, prefilter complaint-shaped text, classify with an LLM, embed and cluster, rank by frequency times severity times recency. A weekend gets you ranked pain themes with real permalinks for two or three subreddits you already know. What does not fall out of one session is everything after the demo: staying inside Reddit's rate limits at scale, picking which communities are worth scanning when you do not already know, deduping the same pain across runs so week two is not week one again, and keeping the LLM bill under the price of the subscription. Verdict is kinda, not yes, because the first run is easy and the tenth is where the product actually lives.

## Product outcome

Pull posts and comments from a handful of public subreddits, classify complaints with an LLM, cluster them into named pain themes, and rank them with clickable quote evidence.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Anthropic or OpenAI API key
- embedding model
- SQLite
- patience with Reddit rate limits

## Explicit non-goals for v1

- community discovery, you can only scan subreddits you already thought of
- cross-scan dedupe, so repeat runs resurface the same pains as if they were new
- a warmed corpus, every fresh scan pays the full ingestion wait
- cost control, naive LLM classification of a busy subreddit gets expensive fast
- the idea generation and validation layer on top of the raw clusters

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build me a Reddit pain finder: a local CLI plus a small dashboard that reads public
Reddit and turns complaints into ranked pain themes with clickable evidence.

- TypeScript on Node 22, SQLite via better-sqlite3, Hono for the dashboard. One
  repo, one `npm run scan` entrypoint. No accounts, no cloud, no telemetry.
- Input: subreddits.txt plus a timeframe flag (default 90 days). Fetch posts and
  top level comments from Reddit's public JSON endpoints, for example
  https://www.reddit.com/r/<sub>/top.json?t=year. One request every 2 seconds, a
  real descriptive User-Agent, and cache every raw response in SQLite so re-runs
  cost nothing. No OAuth, no logged-in scraping.
- Prefilter to complaint-shaped text with cheap regexes ("I hate", "why is there
  no", "wasted hours", "workaround", "gave up on") before spending a single
  token. This is the whole cost story, do it first.
- Classify survivors with Claude (ANTHROPIC_API_KEY in .env, batched, cached by
  content hash) into: is_pain, severity 1 to 5, one line summary.
- Cluster: embed the summaries, group at cosine similarity above 0.82, then have
  Claude name each cluster and pick its 5 strongest verbatim quotes with
  permalinks. Never paraphrase a quote, evidence has to be clickable or it is
  worthless.
- Score each cluster as frequency x mean severity x recency decay, and persist
  scores per run so a later scan can show what moved.
- Dashboard on localhost:3000: ranked clusters, expandable quotes with permalinks,
  filter by subreddit, CSV export.
- README: how to choose subreddits, the rate limit rule and why breaking it gets
  you blocked, and rough token cost per 1000 comments.
- Out of scope: sources other than Reddit, idea generation, and cross-scan dedupe.
  Get one subreddit list producing clusters you actually trust first.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted IdeaFast capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# IdeaFast indie build

## Goal

Build the smallest trustworthy replacement for the core IdeaFast workflow for one developer or a tiny team.

## Scope

Pull posts and comments from a handful of public subreddits, classify complaints with an LLM, cluster them into named pain themes, and rank them with clickable quote evidence.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- community discovery, you can only scan subreddits you already thought of
- cross-scan dedupe, so repeat runs resurface the same pains as if they were new
- a warmed corpus, every fresh scan pays the full ingestion wait
- cost control, naive LLM classification of a busy subreddit gets expensive fast
- the idea generation and validation layer on top of the raw clusters

If those capabilities are essential, use PRAW instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build me a Reddit pain finder: a local CLI plus a small dashboard that reads public
Reddit and turns complaints into ranked pain themes with clickable evidence.

- TypeScript on Node 22, SQLite via better-sqlite3, Hono for the dashboard. One
  repo, one `npm run scan` entrypoint. No accounts, no cloud, no telemetry.
- Input: subreddits.txt plus a timeframe flag (default 90 days). Fetch posts and
  top level comments from Reddit's public JSON endpoints, for example
  https://www.reddit.com/r/<sub>/top.json?t=year. One request every 2 seconds, a
  real descriptive User-Agent, and cache every raw response in SQLite so re-runs
  cost nothing. No OAuth, no logged-in scraping.
- Prefilter to complaint-shaped text with cheap regexes ("I hate", "why is there
  no", "wasted hours", "workaround", "gave up on") before spending a single
  token. This is the whole cost story, do it first.
- Classify survivors with Claude (ANTHROPIC_API_KEY in .env, batched, cached by
  content hash) into: is_pain, severity 1 to 5, one line summary.
- Cluster: embed the summaries, group at cosine similarity above 0.82, then have
  Claude name each cluster and pick its 5 strongest verbatim quotes with
  permalinks. Never paraphrase a quote, evidence has to be clickable or it is
  worthless.
- Score each cluster as frequency x mean severity x recency decay, and persist
  scores per run so a later scan can show what moved.
- Dashboard on localhost:3000: ranked clusters, expandable quotes with permalinks,
  filter by subreddit, CSV export.
- README: how to choose subreddits, the rate limit rule and why breaking it gets
  you blocked, and rough token cost per 1000 comments.
- Out of scope: sources other than Reddit, idea generation, and cross-scan dedupe.
  Get one subreddit list producing clusters you actually trust first.

## Required capabilities

- Anthropic or OpenAI API key
- embedding model
- SQLite
- patience with Reddit rate limits

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# IdeaFast product brief

## Problem

The pipeline is honest work an agent can do: pull public Reddit JSON, prefilter complaint-shaped text, classify with an LLM, embed and cluster, rank by frequency times severity times recency. A weekend gets you ranked pain themes with real permalinks for two or three subreddits you already know. What does not fall out of one session is everything after the demo: staying inside Reddit's rate limits at scale, picking which communities are worth scanning when you do not already know, deduping the same pain across runs so week two is not week one again, and keeping the LLM bill under the price of the subscription. Verdict is kinda, not yes, because the first run is easy and the tenth is where the product actually lives.

## Product outcome

Pull posts and comments from a handful of public subreddits, classify complaints with an LLM, cluster them into named pain themes, and rank them with clickable quote evidence.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Anthropic or OpenAI API key
- embedding model
- SQLite
- patience with Reddit rate limits

## Explicit non-goals for v1

- community discovery, you can only scan subreddits you already thought of
- cross-scan dedupe, so repeat runs resurface the same pains as if they were new
- a warmed corpus, every fresh scan pays the full ingestion wait
- cost control, naive LLM classification of a busy subreddit gets expensive fast
- the idea generation and validation layer on top of the raw clusters

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build me a Reddit pain finder: a local CLI plus a small dashboard that reads public
Reddit and turns complaints into ranked pain themes with clickable evidence.

- TypeScript on Node 22, SQLite via better-sqlite3, Hono for the dashboard. One
  repo, one `npm run scan` entrypoint. No accounts, no cloud, no telemetry.
- Input: subreddits.txt plus a timeframe flag (default 90 days). Fetch posts and
  top level comments from Reddit's public JSON endpoints, for example
  https://www.reddit.com/r/<sub>/top.json?t=year. One request every 2 seconds, a
  real descriptive User-Agent, and cache every raw response in SQLite so re-runs
  cost nothing. No OAuth, no logged-in scraping.
- Prefilter to complaint-shaped text with cheap regexes ("I hate", "why is there
  no", "wasted hours", "workaround", "gave up on") before spending a single
  token. This is the whole cost story, do it first.
- Classify survivors with Claude (ANTHROPIC_API_KEY in .env, batched, cached by
  content hash) into: is_pain, severity 1 to 5, one line summary.
- Cluster: embed the summaries, group at cosine similarity above 0.82, then have
  Claude name each cluster and pick its 5 strongest verbatim quotes with
  permalinks. Never paraphrase a quote, evidence has to be clickable or it is
  worthless.
- Score each cluster as frequency x mean severity x recency decay, and persist
  scores per run so a later scan can show what moved.
- Dashboard on localhost:3000: ranked clusters, expandable quotes with permalinks,
  filter by subreddit, CSV export.
- README: how to choose subreddits, the rate limit rule and why breaking it gets
  you blocked, and rough token cost per 1000 comments.
- Out of scope: sources other than Reddit, idea generation, and cross-scan dedupe.
  Get one subreddit list producing clusters you actually trust first.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted IdeaFast capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent