Vibecode SuperX

You are building a lean indie version of SuperX.

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

## Goal

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

## Scope

Compose posts and threads with an LLM prompted on samples of your own writing, queue them into weekday time slots, publish via the X API, and pull your post metrics into a local dashboard.

## 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:
- the 10M+ viral post library and niche inspiration feed
- algorithm-aware optimal posting times
- signal agents and lead generation
- auto-DM and engagement automation
- the in-feed Chrome extension analytics
- multi-account management

If those capabilities are essential, use postiz-app 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 personal X posting cockpit inspired by SuperX. Requirements:

- Node + Express + better-sqlite3, one localhost web app; no accounts, no
  telemetry, all keys in .env.
- A composer with an AI draft panel: send my topic plus 20 of my own past
  posts (pasted once into voice.txt) to an LLM API so drafts sound like me,
  with tone buttons for punchier, shorter, thread.
- Slot-based queue: weekday posting times in my timezone from a config
  file; drafts fill the next free slot, drag to reorder, pin to exact
  datetimes. Thread support with per-post character counters.
- Publish via the X API v2 with node-cron, marking rows sent or failed
  before posting so nothing double-posts. Be blunt in the README: posting
  needs a paid X API tier, and that bill exists before the first post.
- Pull my recent post metrics (impressions, likes, replies) on a daily
  cron into SQLite and render a simple dashboard: per-post table plus a
  30-day sparkline drawn as inline SVG.
- A fallback copy-to-clipboard button per queued post so the tool stays
  useful without paying X anything.
- Out of scope, and say so in the README: viral post libraries, optimal
  timing models, auto-DMs, lead generation, and multi-account. Those are
  data and ToS problems, not code.
- README: X developer app setup, which paid tier posting needs, and the
  LLM key.

## Required capabilities

- paid X API tier for posting
- LLM API key for voice-matched drafts
- always-on box for the scheduler

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

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

## Goal

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

## Scope

Compose posts and threads with an LLM prompted on samples of your own writing, queue them into weekday time slots, publish via the X API, and pull your post metrics into a local dashboard.

## 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:
- the 10M+ viral post library and niche inspiration feed
- algorithm-aware optimal posting times
- signal agents and lead generation
- auto-DM and engagement automation
- the in-feed Chrome extension analytics
- multi-account management

If those capabilities are essential, use postiz-app 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 personal X posting cockpit inspired by SuperX. Requirements:

- Node + Express + better-sqlite3, one localhost web app; no accounts, no
  telemetry, all keys in .env.
- A composer with an AI draft panel: send my topic plus 20 of my own past
  posts (pasted once into voice.txt) to an LLM API so drafts sound like me,
  with tone buttons for punchier, shorter, thread.
- Slot-based queue: weekday posting times in my timezone from a config
  file; drafts fill the next free slot, drag to reorder, pin to exact
  datetimes. Thread support with per-post character counters.
- Publish via the X API v2 with node-cron, marking rows sent or failed
  before posting so nothing double-posts. Be blunt in the README: posting
  needs a paid X API tier, and that bill exists before the first post.
- Pull my recent post metrics (impressions, likes, replies) on a daily
  cron into SQLite and render a simple dashboard: per-post table plus a
  30-day sparkline drawn as inline SVG.
- A fallback copy-to-clipboard button per queued post so the tool stays
  useful without paying X anything.
- Out of scope, and say so in the README: viral post libraries, optimal
  timing models, auto-DMs, lead generation, and multi-account. Those are
  data and ToS problems, not code.
- README: X developer app setup, which paid tier posting needs, and the
  LLM key.

## Required capabilities

- paid X API tier for posting
- LLM API key for voice-matched drafts
- always-on box for the scheduler

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

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

## Problem

The personal core (a composer with an LLM writing in your voice, a slot-based scheduler, and basic analytics) is a weekend build, exactly like every scheduler on this list. What you cannot one-shot: X's write API costs real money before your first post goes out, the 10M-post viral library and timing models are proprietary data collected over years, and the engagement automations live in rate-limit and ToS territory that a personal script will get wrong. Full disclosure: SuperX is built by the person who runs this site. The verdict got no mercy anyway.

## Product outcome

Compose posts and threads with an LLM prompted on samples of your own writing, queue them into weekday time slots, publish via the X API, and pull your post metrics into a local dashboard.

## Target user

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

## Required capabilities

- paid X API tier for posting
- LLM API key for voice-matched drafts
- always-on box for the scheduler

## Explicit non-goals for v1

- the 10M+ viral post library and niche inspiration feed
- algorithm-aware optimal posting times
- signal agents and lead generation
- auto-DM and engagement automation
- the in-feed Chrome extension analytics
- multi-account management

## 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 personal X posting cockpit inspired by SuperX. Requirements:

- Node + Express + better-sqlite3, one localhost web app; no accounts, no
  telemetry, all keys in .env.
- A composer with an AI draft panel: send my topic plus 20 of my own past
  posts (pasted once into voice.txt) to an LLM API so drafts sound like me,
  with tone buttons for punchier, shorter, thread.
- Slot-based queue: weekday posting times in my timezone from a config
  file; drafts fill the next free slot, drag to reorder, pin to exact
  datetimes. Thread support with per-post character counters.
- Publish via the X API v2 with node-cron, marking rows sent or failed
  before posting so nothing double-posts. Be blunt in the README: posting
  needs a paid X API tier, and that bill exists before the first post.
- Pull my recent post metrics (impressions, likes, replies) on a daily
  cron into SQLite and render a simple dashboard: per-post table plus a
  30-day sparkline drawn as inline SVG.
- A fallback copy-to-clipboard button per queued post so the tool stays
  useful without paying X anything.
- Out of scope, and say so in the README: viral post libraries, optimal
  timing models, auto-DMs, lead generation, and multi-account. Those are
  data and ToS problems, not code.
- README: X developer app setup, which paid tier posting needs, and the
  LLM key.

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

# SuperX indie build

## Goal

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

## Scope

Compose posts and threads with an LLM prompted on samples of your own writing, queue them into weekday time slots, publish via the X API, and pull your post metrics into a local dashboard.

## 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:
- the 10M+ viral post library and niche inspiration feed
- algorithm-aware optimal posting times
- signal agents and lead generation
- auto-DM and engagement automation
- the in-feed Chrome extension analytics
- multi-account management

If those capabilities are essential, use postiz-app 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 personal X posting cockpit inspired by SuperX. Requirements:

- Node + Express + better-sqlite3, one localhost web app; no accounts, no
  telemetry, all keys in .env.
- A composer with an AI draft panel: send my topic plus 20 of my own past
  posts (pasted once into voice.txt) to an LLM API so drafts sound like me,
  with tone buttons for punchier, shorter, thread.
- Slot-based queue: weekday posting times in my timezone from a config
  file; drafts fill the next free slot, drag to reorder, pin to exact
  datetimes. Thread support with per-post character counters.
- Publish via the X API v2 with node-cron, marking rows sent or failed
  before posting so nothing double-posts. Be blunt in the README: posting
  needs a paid X API tier, and that bill exists before the first post.
- Pull my recent post metrics (impressions, likes, replies) on a daily
  cron into SQLite and render a simple dashboard: per-post table plus a
  30-day sparkline drawn as inline SVG.
- A fallback copy-to-clipboard button per queued post so the tool stays
  useful without paying X anything.
- Out of scope, and say so in the README: viral post libraries, optimal
  timing models, auto-DMs, lead generation, and multi-account. Those are
  data and ToS problems, not code.
- README: X developer app setup, which paid tier posting needs, and the
  LLM key.

## Required capabilities

- paid X API tier for posting
- LLM API key for voice-matched drafts
- always-on box for the scheduler

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

# SuperX product brief

## Problem

The personal core (a composer with an LLM writing in your voice, a slot-based scheduler, and basic analytics) is a weekend build, exactly like every scheduler on this list. What you cannot one-shot: X's write API costs real money before your first post goes out, the 10M-post viral library and timing models are proprietary data collected over years, and the engagement automations live in rate-limit and ToS territory that a personal script will get wrong. Full disclosure: SuperX is built by the person who runs this site. The verdict got no mercy anyway.

## Product outcome

Compose posts and threads with an LLM prompted on samples of your own writing, queue them into weekday time slots, publish via the X API, and pull your post metrics into a local dashboard.

## Target user

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

## Required capabilities

- paid X API tier for posting
- LLM API key for voice-matched drafts
- always-on box for the scheduler

## Explicit non-goals for v1

- the 10M+ viral post library and niche inspiration feed
- algorithm-aware optimal posting times
- signal agents and lead generation
- auto-DM and engagement automation
- the in-feed Chrome extension analytics
- multi-account management

## 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 personal X posting cockpit inspired by SuperX. Requirements:

- Node + Express + better-sqlite3, one localhost web app; no accounts, no
  telemetry, all keys in .env.
- A composer with an AI draft panel: send my topic plus 20 of my own past
  posts (pasted once into voice.txt) to an LLM API so drafts sound like me,
  with tone buttons for punchier, shorter, thread.
- Slot-based queue: weekday posting times in my timezone from a config
  file; drafts fill the next free slot, drag to reorder, pin to exact
  datetimes. Thread support with per-post character counters.
- Publish via the X API v2 with node-cron, marking rows sent or failed
  before posting so nothing double-posts. Be blunt in the README: posting
  needs a paid X API tier, and that bill exists before the first post.
- Pull my recent post metrics (impressions, likes, replies) on a daily
  cron into SQLite and render a simple dashboard: per-post table plus a
  30-day sparkline drawn as inline SVG.
- A fallback copy-to-clipboard button per queued post so the tool stays
  useful without paying X anything.
- Out of scope, and say so in the README: viral post libraries, optimal
  timing models, auto-DMs, lead generation, and multi-account. Those are
  data and ToS problems, not code.
- README: X developer app setup, which paid tier posting needs, and the
  LLM key.

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