Vibecode Lovable

You are building a lean indie version of Lovable.

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

## Goal

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

## Scope

Send a plain-language brief to a model API, have it write a small React app into a local folder, run it, and keep iterating in the same conversation.

## 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 frontier model, which is the actual product
- hosted preview URLs and one-click deploy
- a database and auth wired up for you
- a non-developer being able to ship anything at all

If those capabilities are essential, use bolt.diy 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 brief-to-app generator to replace Lovable. Requirements:

- A Node 22 CLI: `vibe new "a habit tracker with a weekly grid"` scaffolds a Vite +
  React + TypeScript app into ./apps/<slug>, then edits it in a loop. Generated apps
  persist to plain JSON or SQLite via better-sqlite3.
- Call the Anthropic or OpenAI API with the key from .env and ask for whole files
  back as JSON, path plus contents, never prose I have to dig out of a code fence.
- Every round is a git commit on a branch and prints the diff first. `vibe undo` is
  a git revert, so nothing the model does is unrecoverable.
- After each round run `npm run build` and `tsc --noEmit`, feed failures back, retry
  three times, then stop and show me the error instead of looping.
- `vibe preview` runs the Vite dev server on localhost:5173. No accounts, no
  telemetry, nothing leaves my machine except the model calls.
- Keep the transcript, file tree, and last diff in .vibe/session.json inside the app,
  resend only the files I named, and print tokens and cost per round.
- Out of scope: hosted previews, one-click deploy, and team collaboration. Do not
  build a web UI, the terminal is the interface.
- README: which key to set, what a typical app costs, and the honest warning that the
  output is only as good as the model behind it.

## Required capabilities

- Node 22
- Anthropic or OpenAI API key
- git

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

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

## Goal

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

## Scope

Send a plain-language brief to a model API, have it write a small React app into a local folder, run it, and keep iterating in the same conversation.

## 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 frontier model, which is the actual product
- hosted preview URLs and one-click deploy
- a database and auth wired up for you
- a non-developer being able to ship anything at all

If those capabilities are essential, use bolt.diy 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 brief-to-app generator to replace Lovable. Requirements:

- A Node 22 CLI: `vibe new "a habit tracker with a weekly grid"` scaffolds a Vite +
  React + TypeScript app into ./apps/<slug>, then edits it in a loop. Generated apps
  persist to plain JSON or SQLite via better-sqlite3.
- Call the Anthropic or OpenAI API with the key from .env and ask for whole files
  back as JSON, path plus contents, never prose I have to dig out of a code fence.
- Every round is a git commit on a branch and prints the diff first. `vibe undo` is
  a git revert, so nothing the model does is unrecoverable.
- After each round run `npm run build` and `tsc --noEmit`, feed failures back, retry
  three times, then stop and show me the error instead of looping.
- `vibe preview` runs the Vite dev server on localhost:5173. No accounts, no
  telemetry, nothing leaves my machine except the model calls.
- Keep the transcript, file tree, and last diff in .vibe/session.json inside the app,
  resend only the files I named, and print tokens and cost per round.
- Out of scope: hosted previews, one-click deploy, and team collaboration. Do not
  build a web UI, the terminal is the interface.
- README: which key to set, what a typical app costs, and the honest warning that the
  output is only as good as the model behind it.

## Required capabilities

- Node 22
- Anthropic or OpenAI API key
- git

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

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

## Problem

The wrapper is easy: a CLI that sends your brief to a model, writes the files, and starts the dev server is one sitting of work. The model doing the writing is the actual product, and you cannot rebuild that. Everything Lovable puts around it, the hosted preview, the deploy, the database wired up for you, and a non-developer being able to use any of it, goes with the subscription.

## Product outcome

Send a plain-language brief to a model API, have it write a small React app into a local folder, run it, and keep iterating in the same conversation.

## Target user

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

## Required capabilities

- Node 22
- Anthropic or OpenAI API key
- git

## Explicit non-goals for v1

- the frontier model, which is the actual product
- hosted preview URLs and one-click deploy
- a database and auth wired up for you
- a non-developer being able to ship anything at all

## 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 brief-to-app generator to replace Lovable. Requirements:

- A Node 22 CLI: `vibe new "a habit tracker with a weekly grid"` scaffolds a Vite +
  React + TypeScript app into ./apps/<slug>, then edits it in a loop. Generated apps
  persist to plain JSON or SQLite via better-sqlite3.
- Call the Anthropic or OpenAI API with the key from .env and ask for whole files
  back as JSON, path plus contents, never prose I have to dig out of a code fence.
- Every round is a git commit on a branch and prints the diff first. `vibe undo` is
  a git revert, so nothing the model does is unrecoverable.
- After each round run `npm run build` and `tsc --noEmit`, feed failures back, retry
  three times, then stop and show me the error instead of looping.
- `vibe preview` runs the Vite dev server on localhost:5173. No accounts, no
  telemetry, nothing leaves my machine except the model calls.
- Keep the transcript, file tree, and last diff in .vibe/session.json inside the app,
  resend only the files I named, and print tokens and cost per round.
- Out of scope: hosted previews, one-click deploy, and team collaboration. Do not
  build a web UI, the terminal is the interface.
- README: which key to set, what a typical app costs, and the honest warning that the
  output is only as good as the model behind it.

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

# Lovable indie build

## Goal

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

## Scope

Send a plain-language brief to a model API, have it write a small React app into a local folder, run it, and keep iterating in the same conversation.

## 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 frontier model, which is the actual product
- hosted preview URLs and one-click deploy
- a database and auth wired up for you
- a non-developer being able to ship anything at all

If those capabilities are essential, use bolt.diy 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 brief-to-app generator to replace Lovable. Requirements:

- A Node 22 CLI: `vibe new "a habit tracker with a weekly grid"` scaffolds a Vite +
  React + TypeScript app into ./apps/<slug>, then edits it in a loop. Generated apps
  persist to plain JSON or SQLite via better-sqlite3.
- Call the Anthropic or OpenAI API with the key from .env and ask for whole files
  back as JSON, path plus contents, never prose I have to dig out of a code fence.
- Every round is a git commit on a branch and prints the diff first. `vibe undo` is
  a git revert, so nothing the model does is unrecoverable.
- After each round run `npm run build` and `tsc --noEmit`, feed failures back, retry
  three times, then stop and show me the error instead of looping.
- `vibe preview` runs the Vite dev server on localhost:5173. No accounts, no
  telemetry, nothing leaves my machine except the model calls.
- Keep the transcript, file tree, and last diff in .vibe/session.json inside the app,
  resend only the files I named, and print tokens and cost per round.
- Out of scope: hosted previews, one-click deploy, and team collaboration. Do not
  build a web UI, the terminal is the interface.
- README: which key to set, what a typical app costs, and the honest warning that the
  output is only as good as the model behind it.

## Required capabilities

- Node 22
- Anthropic or OpenAI API key
- git

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

# Lovable product brief

## Problem

The wrapper is easy: a CLI that sends your brief to a model, writes the files, and starts the dev server is one sitting of work. The model doing the writing is the actual product, and you cannot rebuild that. Everything Lovable puts around it, the hosted preview, the deploy, the database wired up for you, and a non-developer being able to use any of it, goes with the subscription.

## Product outcome

Send a plain-language brief to a model API, have it write a small React app into a local folder, run it, and keep iterating in the same conversation.

## Target user

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

## Required capabilities

- Node 22
- Anthropic or OpenAI API key
- git

## Explicit non-goals for v1

- the frontier model, which is the actual product
- hosted preview URLs and one-click deploy
- a database and auth wired up for you
- a non-developer being able to ship anything at all

## 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 brief-to-app generator to replace Lovable. Requirements:

- A Node 22 CLI: `vibe new "a habit tracker with a weekly grid"` scaffolds a Vite +
  React + TypeScript app into ./apps/<slug>, then edits it in a loop. Generated apps
  persist to plain JSON or SQLite via better-sqlite3.
- Call the Anthropic or OpenAI API with the key from .env and ask for whole files
  back as JSON, path plus contents, never prose I have to dig out of a code fence.
- Every round is a git commit on a branch and prints the diff first. `vibe undo` is
  a git revert, so nothing the model does is unrecoverable.
- After each round run `npm run build` and `tsc --noEmit`, feed failures back, retry
  three times, then stop and show me the error instead of looping.
- `vibe preview` runs the Vite dev server on localhost:5173. No accounts, no
  telemetry, nothing leaves my machine except the model calls.
- Keep the transcript, file tree, and last diff in .vibe/session.json inside the app,
  resend only the files I named, and print tokens and cost per round.
- Out of scope: hosted previews, one-click deploy, and team collaboration. Do not
  build a web UI, the terminal is the interface.
- README: which key to set, what a typical app costs, and the honest warning that the
  output is only as good as the model behind it.

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