Vibecode Postiz

You are building a lean indie version of Postiz.

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

## Goal

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

## Scope

Compose posts into a slot-based queue, publish them on schedule to open-API networks via per-network adapters, and log outcomes.

## 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:
- 28+ maintained channel integrations
- pre-approved platform OAuth apps (Instagram, LinkedIn, TikTok)
- per-network post previews
- analytics
- team approvals and collaboration
- AI content assistance

If those capabilities are essential, use Postiz (open source) 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 social post scheduler to replace Postiz. Requirements:

- Node + Express + better-sqlite3; a localhost page with a compose box,
  image attach, and the queue ordered by send time.
- Three targets: Mastodon (access token), Bluesky (app password via
  @atproto/api), and a Telegram channel (bot token). Creds in .env, one
  small adapter file per network so a fourth is addable later.
- Slot-based queueing: I define posting times per weekday in my timezone
  and new posts fill the next free slot; a post can also be pinned to an
  exact datetime or duplicated across networks with per-network text.
- A node-cron tick every minute publishes due posts, marks each row sent
  or failed, retries failures 3 times with backoff, and marks before
  sending so nothing ever double-posts.
- Per-network character counter in the composer; attached images stored
  in media/ next to the database, resized to each network's limits with
  sharp.
- A history page of the last 100 sent posts linking to the live posts.
- Runs on my always-on box; localhost only, no accounts, no telemetry.
- Out of scope: Instagram, LinkedIn, TikTok, and X (approval-gated or
  paid APIs, say so in the README), analytics, teams, and AI features.
- README: getting a Mastodon token, a Bluesky app password, and a
  Telegram bot token.

## Required capabilities

- OAuth/API access per social network
- always-on box for the scheduler
- database
- media storage

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

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

## Goal

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

## Scope

Compose posts into a slot-based queue, publish them on schedule to open-API networks via per-network adapters, and log outcomes.

## 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:
- 28+ maintained channel integrations
- pre-approved platform OAuth apps (Instagram, LinkedIn, TikTok)
- per-network post previews
- analytics
- team approvals and collaboration
- AI content assistance

If those capabilities are essential, use Postiz (open source) 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 social post scheduler to replace Postiz. Requirements:

- Node + Express + better-sqlite3; a localhost page with a compose box,
  image attach, and the queue ordered by send time.
- Three targets: Mastodon (access token), Bluesky (app password via
  @atproto/api), and a Telegram channel (bot token). Creds in .env, one
  small adapter file per network so a fourth is addable later.
- Slot-based queueing: I define posting times per weekday in my timezone
  and new posts fill the next free slot; a post can also be pinned to an
  exact datetime or duplicated across networks with per-network text.
- A node-cron tick every minute publishes due posts, marks each row sent
  or failed, retries failures 3 times with backoff, and marks before
  sending so nothing ever double-posts.
- Per-network character counter in the composer; attached images stored
  in media/ next to the database, resized to each network's limits with
  sharp.
- A history page of the last 100 sent posts linking to the live posts.
- Runs on my always-on box; localhost only, no accounts, no telemetry.
- Out of scope: Instagram, LinkedIn, TikTok, and X (approval-gated or
  paid APIs, say so in the README), analytics, teams, and AI features.
- README: getting a Mastodon token, a Bluesky app password, and a
  Telegram bot token.

## Required capabilities

- OAuth/API access per social network
- always-on box for the scheduler
- database
- media storage

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

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

## Problem

The core loop (compose, queue, cron tick, publish) is one-shottable for networks with open APIs like Mastodon, Bluesky, and Telegram. What you cannot one-shot is the reason schedulers exist as products: OAuth apps for Instagram, LinkedIn, TikTok, and X are approval-gated or paid, and keeping 28+ integrations alive as platforms change policies is permanent maintenance. Postiz is also fully open source, so the honest DIY move for the full feature set is self-hosting it rather than rebuilding it.

## Product outcome

Compose posts into a slot-based queue, publish them on schedule to open-API networks via per-network adapters, and log outcomes.

## Target user

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

## Required capabilities

- OAuth/API access per social network
- always-on box for the scheduler
- database
- media storage

## Explicit non-goals for v1

- 28+ maintained channel integrations
- pre-approved platform OAuth apps (Instagram, LinkedIn, TikTok)
- per-network post previews
- analytics
- team approvals and collaboration
- AI content assistance

## 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 social post scheduler to replace Postiz. Requirements:

- Node + Express + better-sqlite3; a localhost page with a compose box,
  image attach, and the queue ordered by send time.
- Three targets: Mastodon (access token), Bluesky (app password via
  @atproto/api), and a Telegram channel (bot token). Creds in .env, one
  small adapter file per network so a fourth is addable later.
- Slot-based queueing: I define posting times per weekday in my timezone
  and new posts fill the next free slot; a post can also be pinned to an
  exact datetime or duplicated across networks with per-network text.
- A node-cron tick every minute publishes due posts, marks each row sent
  or failed, retries failures 3 times with backoff, and marks before
  sending so nothing ever double-posts.
- Per-network character counter in the composer; attached images stored
  in media/ next to the database, resized to each network's limits with
  sharp.
- A history page of the last 100 sent posts linking to the live posts.
- Runs on my always-on box; localhost only, no accounts, no telemetry.
- Out of scope: Instagram, LinkedIn, TikTok, and X (approval-gated or
  paid APIs, say so in the README), analytics, teams, and AI features.
- README: getting a Mastodon token, a Bluesky app password, and a
  Telegram bot token.

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

# Postiz indie build

## Goal

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

## Scope

Compose posts into a slot-based queue, publish them on schedule to open-API networks via per-network adapters, and log outcomes.

## 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:
- 28+ maintained channel integrations
- pre-approved platform OAuth apps (Instagram, LinkedIn, TikTok)
- per-network post previews
- analytics
- team approvals and collaboration
- AI content assistance

If those capabilities are essential, use Postiz (open source) 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 social post scheduler to replace Postiz. Requirements:

- Node + Express + better-sqlite3; a localhost page with a compose box,
  image attach, and the queue ordered by send time.
- Three targets: Mastodon (access token), Bluesky (app password via
  @atproto/api), and a Telegram channel (bot token). Creds in .env, one
  small adapter file per network so a fourth is addable later.
- Slot-based queueing: I define posting times per weekday in my timezone
  and new posts fill the next free slot; a post can also be pinned to an
  exact datetime or duplicated across networks with per-network text.
- A node-cron tick every minute publishes due posts, marks each row sent
  or failed, retries failures 3 times with backoff, and marks before
  sending so nothing ever double-posts.
- Per-network character counter in the composer; attached images stored
  in media/ next to the database, resized to each network's limits with
  sharp.
- A history page of the last 100 sent posts linking to the live posts.
- Runs on my always-on box; localhost only, no accounts, no telemetry.
- Out of scope: Instagram, LinkedIn, TikTok, and X (approval-gated or
  paid APIs, say so in the README), analytics, teams, and AI features.
- README: getting a Mastodon token, a Bluesky app password, and a
  Telegram bot token.

## Required capabilities

- OAuth/API access per social network
- always-on box for the scheduler
- database
- media storage

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

# Postiz product brief

## Problem

The core loop (compose, queue, cron tick, publish) is one-shottable for networks with open APIs like Mastodon, Bluesky, and Telegram. What you cannot one-shot is the reason schedulers exist as products: OAuth apps for Instagram, LinkedIn, TikTok, and X are approval-gated or paid, and keeping 28+ integrations alive as platforms change policies is permanent maintenance. Postiz is also fully open source, so the honest DIY move for the full feature set is self-hosting it rather than rebuilding it.

## Product outcome

Compose posts into a slot-based queue, publish them on schedule to open-API networks via per-network adapters, and log outcomes.

## Target user

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

## Required capabilities

- OAuth/API access per social network
- always-on box for the scheduler
- database
- media storage

## Explicit non-goals for v1

- 28+ maintained channel integrations
- pre-approved platform OAuth apps (Instagram, LinkedIn, TikTok)
- per-network post previews
- analytics
- team approvals and collaboration
- AI content assistance

## 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 social post scheduler to replace Postiz. Requirements:

- Node + Express + better-sqlite3; a localhost page with a compose box,
  image attach, and the queue ordered by send time.
- Three targets: Mastodon (access token), Bluesky (app password via
  @atproto/api), and a Telegram channel (bot token). Creds in .env, one
  small adapter file per network so a fourth is addable later.
- Slot-based queueing: I define posting times per weekday in my timezone
  and new posts fill the next free slot; a post can also be pinned to an
  exact datetime or duplicated across networks with per-network text.
- A node-cron tick every minute publishes due posts, marks each row sent
  or failed, retries failures 3 times with backoff, and marks before
  sending so nothing ever double-posts.
- Per-network character counter in the composer; attached images stored
  in media/ next to the database, resized to each network's limits with
  sharp.
- A history page of the last 100 sent posts linking to the live posts.
- Runs on my always-on box; localhost only, no accounts, no telemetry.
- Out of scope: Instagram, LinkedIn, TikTok, and X (approval-gated or
  paid APIs, say so in the README), analytics, teams, and AI features.
- README: getting a Mastodon token, a Bluesky app password, and a
  Telegram bot token.

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