Vibecode Fomr

You are building a lean indie version of Fomr.

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

## Goal

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

## Scope

Create a single-owner form builder with live preview, publishable links, response storage, email notifications, and CSV export.

## 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:
- real-time team collaboration
- custom domains and managed TLS
- managed uptime, backups, and abuse controls
- integration catalog
- template and theme depth

If those capabilities are essential, use HeyForm 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 a deliberately narrow personal form builder inspired by Fomr, starting from an empty repository.
Use exactly this stack: Next.js 16, TypeScript, Tailwind CSS, SQLite, and Drizzle ORM.
The core loop is create a form, preview it, publish it, collect responses, and export them.
Make it single-owner and protect the admin area with an ADMIN_PASSWORD from .env.
Create an admin form editor with a reorderable field list and a live respondent preview.
Support short text, long text, email, number, select, radio, checkbox, rating, date, and content blocks.
Allow required fields, labels, help text, placeholders, choices, and basic min/max validation.
Support one simple conditional rule per field: show it when another answer equals a configured value.
Add form-level colors, font choices, logo upload, cover image, spacing, and light or dark appearance.
Publish each form at /s/<slug> with accessible labels, keyboard navigation, and mobile layouts.
Validate every submission on the server against the saved form schema.
Store forms, immutable schema versions, responses, and timestamps in SQLite.
Provide a private response table with search, detail view, deletion, and CSV export.
Send optional owner notifications through SMTP, but keep collection working when SMTP is absent.
Add a honeypot, per-IP rate limiting, request-size limits, and safe upload handling for branding assets.
Include a configurable thank-you message and optional redirect URL.
Handle empty, loading, validation, success, not-found, and recoverable failure states.
Keep user data local and add JSON export and import for forms.
Do not add analytics, telemetry, ads, billing, or third-party accounts.
Put every secret in .env and include a complete .env.example.
Write unit tests for schema validation and branching plus one end-to-end publish-and-submit test.
Create a README covering setup, deployment, data location, backups, SMTP, security limits, and recovery.
Deliberately exclude custom domains, team collaboration, OAuth integrations, payments, and enterprise compliance.
Deliberately exclude a marketplace-sized template library and promise only personal-scale reliability.
Run tests and a production build before finishing, fixing failures instead of merely describing them.

## Required capabilities

- Node.js 22 or newer
- self-hosted deployment target
- SMTP credentials in .env for optional notifications

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

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

## Goal

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

## Scope

Create a single-owner form builder with live preview, publishable links, response storage, email notifications, and CSV export.

## 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:
- real-time team collaboration
- custom domains and managed TLS
- managed uptime, backups, and abuse controls
- integration catalog
- template and theme depth

If those capabilities are essential, use HeyForm 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 a deliberately narrow personal form builder inspired by Fomr, starting from an empty repository.
Use exactly this stack: Next.js 16, TypeScript, Tailwind CSS, SQLite, and Drizzle ORM.
The core loop is create a form, preview it, publish it, collect responses, and export them.
Make it single-owner and protect the admin area with an ADMIN_PASSWORD from .env.
Create an admin form editor with a reorderable field list and a live respondent preview.
Support short text, long text, email, number, select, radio, checkbox, rating, date, and content blocks.
Allow required fields, labels, help text, placeholders, choices, and basic min/max validation.
Support one simple conditional rule per field: show it when another answer equals a configured value.
Add form-level colors, font choices, logo upload, cover image, spacing, and light or dark appearance.
Publish each form at /s/<slug> with accessible labels, keyboard navigation, and mobile layouts.
Validate every submission on the server against the saved form schema.
Store forms, immutable schema versions, responses, and timestamps in SQLite.
Provide a private response table with search, detail view, deletion, and CSV export.
Send optional owner notifications through SMTP, but keep collection working when SMTP is absent.
Add a honeypot, per-IP rate limiting, request-size limits, and safe upload handling for branding assets.
Include a configurable thank-you message and optional redirect URL.
Handle empty, loading, validation, success, not-found, and recoverable failure states.
Keep user data local and add JSON export and import for forms.
Do not add analytics, telemetry, ads, billing, or third-party accounts.
Put every secret in .env and include a complete .env.example.
Write unit tests for schema validation and branching plus one end-to-end publish-and-submit test.
Create a README covering setup, deployment, data location, backups, SMTP, security limits, and recovery.
Deliberately exclude custom domains, team collaboration, OAuth integrations, payments, and enterprise compliance.
Deliberately exclude a marketplace-sized template library and promise only personal-scale reliability.
Run tests and a production build before finishing, fixing failures instead of merely describing them.

## Required capabilities

- Node.js 22 or newer
- self-hosted deployment target
- SMTP credentials in .env for optional notifications

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

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

## Problem

A useful single-owner form builder is a realistic weekend project. Matching Fomr's visual editor, design depth, managed delivery, collaboration, integrations, and confidence that every public submission arrives turns it into an ongoing product rather than a one-shot clone.

## Product outcome

Create a single-owner form builder with live preview, publishable links, response storage, email notifications, and CSV export.

## Target user

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

## Required capabilities

- Node.js 22 or newer
- self-hosted deployment target
- SMTP credentials in .env for optional notifications

## Explicit non-goals for v1

- real-time team collaboration
- custom domains and managed TLS
- managed uptime, backups, and abuse controls
- integration catalog
- template and theme depth

## 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 a deliberately narrow personal form builder inspired by Fomr, starting from an empty repository.
Use exactly this stack: Next.js 16, TypeScript, Tailwind CSS, SQLite, and Drizzle ORM.
The core loop is create a form, preview it, publish it, collect responses, and export them.
Make it single-owner and protect the admin area with an ADMIN_PASSWORD from .env.
Create an admin form editor with a reorderable field list and a live respondent preview.
Support short text, long text, email, number, select, radio, checkbox, rating, date, and content blocks.
Allow required fields, labels, help text, placeholders, choices, and basic min/max validation.
Support one simple conditional rule per field: show it when another answer equals a configured value.
Add form-level colors, font choices, logo upload, cover image, spacing, and light or dark appearance.
Publish each form at /s/<slug> with accessible labels, keyboard navigation, and mobile layouts.
Validate every submission on the server against the saved form schema.
Store forms, immutable schema versions, responses, and timestamps in SQLite.
Provide a private response table with search, detail view, deletion, and CSV export.
Send optional owner notifications through SMTP, but keep collection working when SMTP is absent.
Add a honeypot, per-IP rate limiting, request-size limits, and safe upload handling for branding assets.
Include a configurable thank-you message and optional redirect URL.
Handle empty, loading, validation, success, not-found, and recoverable failure states.
Keep user data local and add JSON export and import for forms.
Do not add analytics, telemetry, ads, billing, or third-party accounts.
Put every secret in .env and include a complete .env.example.
Write unit tests for schema validation and branching plus one end-to-end publish-and-submit test.
Create a README covering setup, deployment, data location, backups, SMTP, security limits, and recovery.
Deliberately exclude custom domains, team collaboration, OAuth integrations, payments, and enterprise compliance.
Deliberately exclude a marketplace-sized template library and promise only personal-scale reliability.
Run tests and a production build before finishing, fixing failures instead of merely describing them.

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

# Fomr indie build

## Goal

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

## Scope

Create a single-owner form builder with live preview, publishable links, response storage, email notifications, and CSV export.

## 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:
- real-time team collaboration
- custom domains and managed TLS
- managed uptime, backups, and abuse controls
- integration catalog
- template and theme depth

If those capabilities are essential, use HeyForm 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 a deliberately narrow personal form builder inspired by Fomr, starting from an empty repository.
Use exactly this stack: Next.js 16, TypeScript, Tailwind CSS, SQLite, and Drizzle ORM.
The core loop is create a form, preview it, publish it, collect responses, and export them.
Make it single-owner and protect the admin area with an ADMIN_PASSWORD from .env.
Create an admin form editor with a reorderable field list and a live respondent preview.
Support short text, long text, email, number, select, radio, checkbox, rating, date, and content blocks.
Allow required fields, labels, help text, placeholders, choices, and basic min/max validation.
Support one simple conditional rule per field: show it when another answer equals a configured value.
Add form-level colors, font choices, logo upload, cover image, spacing, and light or dark appearance.
Publish each form at /s/<slug> with accessible labels, keyboard navigation, and mobile layouts.
Validate every submission on the server against the saved form schema.
Store forms, immutable schema versions, responses, and timestamps in SQLite.
Provide a private response table with search, detail view, deletion, and CSV export.
Send optional owner notifications through SMTP, but keep collection working when SMTP is absent.
Add a honeypot, per-IP rate limiting, request-size limits, and safe upload handling for branding assets.
Include a configurable thank-you message and optional redirect URL.
Handle empty, loading, validation, success, not-found, and recoverable failure states.
Keep user data local and add JSON export and import for forms.
Do not add analytics, telemetry, ads, billing, or third-party accounts.
Put every secret in .env and include a complete .env.example.
Write unit tests for schema validation and branching plus one end-to-end publish-and-submit test.
Create a README covering setup, deployment, data location, backups, SMTP, security limits, and recovery.
Deliberately exclude custom domains, team collaboration, OAuth integrations, payments, and enterprise compliance.
Deliberately exclude a marketplace-sized template library and promise only personal-scale reliability.
Run tests and a production build before finishing, fixing failures instead of merely describing them.

## Required capabilities

- Node.js 22 or newer
- self-hosted deployment target
- SMTP credentials in .env for optional notifications

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

# Fomr product brief

## Problem

A useful single-owner form builder is a realistic weekend project. Matching Fomr's visual editor, design depth, managed delivery, collaboration, integrations, and confidence that every public submission arrives turns it into an ongoing product rather than a one-shot clone.

## Product outcome

Create a single-owner form builder with live preview, publishable links, response storage, email notifications, and CSV export.

## Target user

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

## Required capabilities

- Node.js 22 or newer
- self-hosted deployment target
- SMTP credentials in .env for optional notifications

## Explicit non-goals for v1

- real-time team collaboration
- custom domains and managed TLS
- managed uptime, backups, and abuse controls
- integration catalog
- template and theme depth

## 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 a deliberately narrow personal form builder inspired by Fomr, starting from an empty repository.
Use exactly this stack: Next.js 16, TypeScript, Tailwind CSS, SQLite, and Drizzle ORM.
The core loop is create a form, preview it, publish it, collect responses, and export them.
Make it single-owner and protect the admin area with an ADMIN_PASSWORD from .env.
Create an admin form editor with a reorderable field list and a live respondent preview.
Support short text, long text, email, number, select, radio, checkbox, rating, date, and content blocks.
Allow required fields, labels, help text, placeholders, choices, and basic min/max validation.
Support one simple conditional rule per field: show it when another answer equals a configured value.
Add form-level colors, font choices, logo upload, cover image, spacing, and light or dark appearance.
Publish each form at /s/<slug> with accessible labels, keyboard navigation, and mobile layouts.
Validate every submission on the server against the saved form schema.
Store forms, immutable schema versions, responses, and timestamps in SQLite.
Provide a private response table with search, detail view, deletion, and CSV export.
Send optional owner notifications through SMTP, but keep collection working when SMTP is absent.
Add a honeypot, per-IP rate limiting, request-size limits, and safe upload handling for branding assets.
Include a configurable thank-you message and optional redirect URL.
Handle empty, loading, validation, success, not-found, and recoverable failure states.
Keep user data local and add JSON export and import for forms.
Do not add analytics, telemetry, ads, billing, or third-party accounts.
Put every secret in .env and include a complete .env.example.
Write unit tests for schema validation and branching plus one end-to-end publish-and-submit test.
Create a README covering setup, deployment, data location, backups, SMTP, security limits, and recovery.
Deliberately exclude custom domains, team collaboration, OAuth integrations, payments, and enterprise compliance.
Deliberately exclude a marketplace-sized template library and promise only personal-scale reliability.
Run tests and a production build before finishing, fixing failures instead of merely describing them.

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