Vibecode TradingWizard

You are building a lean indie version of TradingWizard.

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 =====
# TradingWizard indie build

## Goal

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

## Scope

Monitor a small watchlist, score transparent setups from current candles, explain the levels, and journal paper trades without connecting a broker.

## 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:
- maintained coverage across thousands of markets and data providers
- always-on bot scans, stale-data guards, and reliable alert delivery
- filings, news, sentiment, research, and broker-context integrations
- synced history, mobile access, chat controls, and account security
- the maintained bot proof trail and production operations

If those capabilities are essential, use OpenBB Platform 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 local personal market-analysis bot inspired by TradingWizard. Requirements:

- Node 22, TypeScript, Next.js App Router, better-sqlite3, technicalindicators,
  and node-cron. Bind to localhost only.
- watchlist.json holds up to 10 stock or crypto symbols plus a 15m, 1h, or 1d
  timeframe. Fetch candles from Twelve Data with the key in .env.local.
- Cache responses, respect provider limits, and show source plus last-updated time.
  Stale or missing candles must block a new setup.
- Calculate EMA 20/50, RSI 14, ATR 14, recent support and resistance, and volume
  change. Keep every setup rule in one documented rules.ts file.
- For each symbol return WAIT, LONG SETUP, or SHORT SETUP with entry zone, stop,
  target, invalidation, confidence, and the exact rule hits behind the result.
- Use an OpenAI-compatible API only to turn the calculated facts into two plain
  sentences. The model cannot change levels or invent facts. Work without it too.
- Add a paper journal. Confirm each simulated entry manually, size by a fixed risk
  percentage, and update open trades from fresh candles. Never connect a broker.
- Dashboard: watchlist state, latest setup, stale-data warning, open paper trades,
  closed results, and a per-symbol timeline. No profit promises.
- SQLite tables: candles, analyses, paper_trades, and scan_runs. Keep immutable scan
  facts so every result can be explained later.
- Add npm run scan and a configurable cron. One failed symbol must not stop the rest.
- No accounts, cloud sync, telemetry, payments, live orders, or investment advice.
  Do not scrape consumer websites.
- Include seeded fixtures and tests for stale-data blocking, rule calculations, risk
  sizing, manual confirmation, and duplicate-scan idempotency.
- README with setup, API limits, backup/restore, cron examples, and the exact limits
  of a personal build compared with a maintained multi-market service.

## Required capabilities

- Node 22
- Twelve Data API key
- OpenAI-compatible API key
- local SQLite database
- scheduled background process

## 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 TradingWizard.

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 =====
# TradingWizard indie build

## Goal

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

## Scope

Monitor a small watchlist, score transparent setups from current candles, explain the levels, and journal paper trades without connecting a broker.

## 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:
- maintained coverage across thousands of markets and data providers
- always-on bot scans, stale-data guards, and reliable alert delivery
- filings, news, sentiment, research, and broker-context integrations
- synced history, mobile access, chat controls, and account security
- the maintained bot proof trail and production operations

If those capabilities are essential, use OpenBB Platform 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 local personal market-analysis bot inspired by TradingWizard. Requirements:

- Node 22, TypeScript, Next.js App Router, better-sqlite3, technicalindicators,
  and node-cron. Bind to localhost only.
- watchlist.json holds up to 10 stock or crypto symbols plus a 15m, 1h, or 1d
  timeframe. Fetch candles from Twelve Data with the key in .env.local.
- Cache responses, respect provider limits, and show source plus last-updated time.
  Stale or missing candles must block a new setup.
- Calculate EMA 20/50, RSI 14, ATR 14, recent support and resistance, and volume
  change. Keep every setup rule in one documented rules.ts file.
- For each symbol return WAIT, LONG SETUP, or SHORT SETUP with entry zone, stop,
  target, invalidation, confidence, and the exact rule hits behind the result.
- Use an OpenAI-compatible API only to turn the calculated facts into two plain
  sentences. The model cannot change levels or invent facts. Work without it too.
- Add a paper journal. Confirm each simulated entry manually, size by a fixed risk
  percentage, and update open trades from fresh candles. Never connect a broker.
- Dashboard: watchlist state, latest setup, stale-data warning, open paper trades,
  closed results, and a per-symbol timeline. No profit promises.
- SQLite tables: candles, analyses, paper_trades, and scan_runs. Keep immutable scan
  facts so every result can be explained later.
- Add npm run scan and a configurable cron. One failed symbol must not stop the rest.
- No accounts, cloud sync, telemetry, payments, live orders, or investment advice.
  Do not scrape consumer websites.
- Include seeded fixtures and tests for stale-data blocking, rule calculations, risk
  sizing, manual confirmation, and duplicate-scan idempotency.
- README with setup, API limits, backup/restore, cron examples, and the exact limits
  of a personal build compared with a maintained multi-market service.

## Required capabilities

- Node 22
- Twelve Data API key
- OpenAI-compatible API key
- local SQLite database
- scheduled background process

## 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 TradingWizard.

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 =====
# TradingWizard product brief

## Problem

A personal version is a fair weekend build: watch a short list, calculate indicators, explain a setup, and journal simulated trades. Replacing the full service is different. Broad market coverage, current prices, filings and news, continuous bot jobs, stale-data guards, alerts, synced history, and a maintained proof trail are ongoing data and operations work.

## Product outcome

Monitor a small watchlist, score transparent setups from current candles, explain the levels, and journal paper trades without connecting a broker.

## Target user

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

## Required capabilities

- Node 22
- Twelve Data API key
- OpenAI-compatible API key
- local SQLite database
- scheduled background process

## Explicit non-goals for v1

- maintained coverage across thousands of markets and data providers
- always-on bot scans, stale-data guards, and reliable alert delivery
- filings, news, sentiment, research, and broker-context integrations
- synced history, mobile access, chat controls, and account security
- the maintained bot proof trail and production operations

## 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 local personal market-analysis bot inspired by TradingWizard. Requirements:

- Node 22, TypeScript, Next.js App Router, better-sqlite3, technicalindicators,
  and node-cron. Bind to localhost only.
- watchlist.json holds up to 10 stock or crypto symbols plus a 15m, 1h, or 1d
  timeframe. Fetch candles from Twelve Data with the key in .env.local.
- Cache responses, respect provider limits, and show source plus last-updated time.
  Stale or missing candles must block a new setup.
- Calculate EMA 20/50, RSI 14, ATR 14, recent support and resistance, and volume
  change. Keep every setup rule in one documented rules.ts file.
- For each symbol return WAIT, LONG SETUP, or SHORT SETUP with entry zone, stop,
  target, invalidation, confidence, and the exact rule hits behind the result.
- Use an OpenAI-compatible API only to turn the calculated facts into two plain
  sentences. The model cannot change levels or invent facts. Work without it too.
- Add a paper journal. Confirm each simulated entry manually, size by a fixed risk
  percentage, and update open trades from fresh candles. Never connect a broker.
- Dashboard: watchlist state, latest setup, stale-data warning, open paper trades,
  closed results, and a per-symbol timeline. No profit promises.
- SQLite tables: candles, analyses, paper_trades, and scan_runs. Keep immutable scan
  facts so every result can be explained later.
- Add npm run scan and a configurable cron. One failed symbol must not stop the rest.
- No accounts, cloud sync, telemetry, payments, live orders, or investment advice.
  Do not scrape consumer websites.
- Include seeded fixtures and tests for stale-data blocking, rule calculations, risk
  sizing, manual confirmation, and duplicate-scan idempotency.
- README with setup, API limits, backup/restore, cron examples, and the exact limits
  of a personal build compared with a maintained multi-market service.

## 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 TradingWizard capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# TradingWizard indie build

## Goal

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

## Scope

Monitor a small watchlist, score transparent setups from current candles, explain the levels, and journal paper trades without connecting a broker.

## 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:
- maintained coverage across thousands of markets and data providers
- always-on bot scans, stale-data guards, and reliable alert delivery
- filings, news, sentiment, research, and broker-context integrations
- synced history, mobile access, chat controls, and account security
- the maintained bot proof trail and production operations

If those capabilities are essential, use OpenBB Platform 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 local personal market-analysis bot inspired by TradingWizard. Requirements:

- Node 22, TypeScript, Next.js App Router, better-sqlite3, technicalindicators,
  and node-cron. Bind to localhost only.
- watchlist.json holds up to 10 stock or crypto symbols plus a 15m, 1h, or 1d
  timeframe. Fetch candles from Twelve Data with the key in .env.local.
- Cache responses, respect provider limits, and show source plus last-updated time.
  Stale or missing candles must block a new setup.
- Calculate EMA 20/50, RSI 14, ATR 14, recent support and resistance, and volume
  change. Keep every setup rule in one documented rules.ts file.
- For each symbol return WAIT, LONG SETUP, or SHORT SETUP with entry zone, stop,
  target, invalidation, confidence, and the exact rule hits behind the result.
- Use an OpenAI-compatible API only to turn the calculated facts into two plain
  sentences. The model cannot change levels or invent facts. Work without it too.
- Add a paper journal. Confirm each simulated entry manually, size by a fixed risk
  percentage, and update open trades from fresh candles. Never connect a broker.
- Dashboard: watchlist state, latest setup, stale-data warning, open paper trades,
  closed results, and a per-symbol timeline. No profit promises.
- SQLite tables: candles, analyses, paper_trades, and scan_runs. Keep immutable scan
  facts so every result can be explained later.
- Add npm run scan and a configurable cron. One failed symbol must not stop the rest.
- No accounts, cloud sync, telemetry, payments, live orders, or investment advice.
  Do not scrape consumer websites.
- Include seeded fixtures and tests for stale-data blocking, rule calculations, risk
  sizing, manual confirmation, and duplicate-scan idempotency.
- README with setup, API limits, backup/restore, cron examples, and the exact limits
  of a personal build compared with a maintained multi-market service.

## Required capabilities

- Node 22
- Twelve Data API key
- OpenAI-compatible API key
- local SQLite database
- scheduled background process

## 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.

# TradingWizard product brief

## Problem

A personal version is a fair weekend build: watch a short list, calculate indicators, explain a setup, and journal simulated trades. Replacing the full service is different. Broad market coverage, current prices, filings and news, continuous bot jobs, stale-data guards, alerts, synced history, and a maintained proof trail are ongoing data and operations work.

## Product outcome

Monitor a small watchlist, score transparent setups from current candles, explain the levels, and journal paper trades without connecting a broker.

## Target user

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

## Required capabilities

- Node 22
- Twelve Data API key
- OpenAI-compatible API key
- local SQLite database
- scheduled background process

## Explicit non-goals for v1

- maintained coverage across thousands of markets and data providers
- always-on bot scans, stale-data guards, and reliable alert delivery
- filings, news, sentiment, research, and broker-context integrations
- synced history, mobile access, chat controls, and account security
- the maintained bot proof trail and production operations

## 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 local personal market-analysis bot inspired by TradingWizard. Requirements:

- Node 22, TypeScript, Next.js App Router, better-sqlite3, technicalindicators,
  and node-cron. Bind to localhost only.
- watchlist.json holds up to 10 stock or crypto symbols plus a 15m, 1h, or 1d
  timeframe. Fetch candles from Twelve Data with the key in .env.local.
- Cache responses, respect provider limits, and show source plus last-updated time.
  Stale or missing candles must block a new setup.
- Calculate EMA 20/50, RSI 14, ATR 14, recent support and resistance, and volume
  change. Keep every setup rule in one documented rules.ts file.
- For each symbol return WAIT, LONG SETUP, or SHORT SETUP with entry zone, stop,
  target, invalidation, confidence, and the exact rule hits behind the result.
- Use an OpenAI-compatible API only to turn the calculated facts into two plain
  sentences. The model cannot change levels or invent facts. Work without it too.
- Add a paper journal. Confirm each simulated entry manually, size by a fixed risk
  percentage, and update open trades from fresh candles. Never connect a broker.
- Dashboard: watchlist state, latest setup, stale-data warning, open paper trades,
  closed results, and a per-symbol timeline. No profit promises.
- SQLite tables: candles, analyses, paper_trades, and scan_runs. Keep immutable scan
  facts so every result can be explained later.
- Add npm run scan and a configurable cron. One failed symbol must not stop the rest.
- No accounts, cloud sync, telemetry, payments, live orders, or investment advice.
  Do not scrape consumer websites.
- Include seeded fixtures and tests for stale-data blocking, rule calculations, risk
  sizing, manual confirmation, and duplicate-scan idempotency.
- README with setup, API limits, backup/restore, cron examples, and the exact limits
  of a personal build compared with a maintained multi-market service.

## 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 TradingWizard 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