Vibecode Reform
track this build5 steps, step by step0%YES · one-shottable
The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Reform, publish a clean branded lead form with routing, notifications, and exports. The hard boundary is polished ux, spam controls, integrations, and reliable hosted delivery, plus integrations, deliverability, and workflow depth.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Reform. 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 ===== # Reform indie build ## Goal Build the smallest trustworthy replacement for the core Reform workflow for one developer or a tiny team. ## Scope Publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with 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: - polished UX, spam controls, integrations, and reliable hosted delivery - advanced branching - payment and CRM integrations - large template libraries - enterprise compliance If those capabilities are essential, use Formbricks 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 personal replacement for Reform in an empty repository. Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend; do not offer alternative stacks. The core loop is: publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with CSV export. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields. Publish each form at a stable slug with server-side validation and accessible labels. Add honeypot, rate limiting, submission-size limits, and a clear privacy notice. Store responses in SQLite and provide search, filters, detail view, and CSV export. Send an owner notification without placing submitted values in logs. Support a thank-you screen and one simple conditional branch. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out payment collection. Deliberately leave out hundreds of third-party integrations. Deliberately leave out multi-brand enterprise workspaces and compliance attestations. Finish by running the tests and listing the exact commands used. ## Required capabilities - Node.js 22 - Resend API key or SMTP credentials - self-hosted deploy target ## 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 Reform. 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 ===== # Reform indie build ## Goal Build the smallest trustworthy replacement for the core Reform workflow for one developer or a tiny team. ## Scope Publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with 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: - polished UX, spam controls, integrations, and reliable hosted delivery - advanced branching - payment and CRM integrations - large template libraries - enterprise compliance If those capabilities are essential, use Formbricks 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 personal replacement for Reform in an empty repository. Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend; do not offer alternative stacks. The core loop is: publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with CSV export. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields. Publish each form at a stable slug with server-side validation and accessible labels. Add honeypot, rate limiting, submission-size limits, and a clear privacy notice. Store responses in SQLite and provide search, filters, detail view, and CSV export. Send an owner notification without placing submitted values in logs. Support a thank-you screen and one simple conditional branch. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out payment collection. Deliberately leave out hundreds of third-party integrations. Deliberately leave out multi-brand enterprise workspaces and compliance attestations. Finish by running the tests and listing the exact commands used. ## Required capabilities - Node.js 22 - Resend API key or SMTP credentials - self-hosted deploy target ## 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 Reform. 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 ===== # Reform product brief ## Problem The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Reform, publish a clean branded lead form with routing, notifications, and exports. The hard boundary is polished ux, spam controls, integrations, and reliable hosted delivery, plus integrations, deliverability, and workflow depth. ## Product outcome Publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with CSV export. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node.js 22 - Resend API key or SMTP credentials - self-hosted deploy target ## Explicit non-goals for v1 - polished UX, spam controls, integrations, and reliable hosted delivery - advanced branching - payment and CRM integrations - large template libraries - enterprise compliance ## 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 personal replacement for Reform in an empty repository. Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend; do not offer alternative stacks. The core loop is: publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with CSV export. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields. Publish each form at a stable slug with server-side validation and accessible labels. Add honeypot, rate limiting, submission-size limits, and a clear privacy notice. Store responses in SQLite and provide search, filters, detail view, and CSV export. Send an owner notification without placing submitted values in logs. Support a thank-you screen and one simple conditional branch. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out payment collection. Deliberately leave out hundreds of third-party integrations. Deliberately leave out multi-brand enterprise workspaces and compliance attestations. Finish by running the tests and listing the exact commands used. ## 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 Reform capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Reform indie build ## Goal Build the smallest trustworthy replacement for the core Reform workflow for one developer or a tiny team. ## Scope Publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with 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: - polished UX, spam controls, integrations, and reliable hosted delivery - advanced branching - payment and CRM integrations - large template libraries - enterprise compliance If those capabilities are essential, use Formbricks 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 personal replacement for Reform in an empty repository. Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend; do not offer alternative stacks. The core loop is: publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with CSV export. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields. Publish each form at a stable slug with server-side validation and accessible labels. Add honeypot, rate limiting, submission-size limits, and a clear privacy notice. Store responses in SQLite and provide search, filters, detail view, and CSV export. Send an owner notification without placing submitted values in logs. Support a thank-you screen and one simple conditional branch. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out payment collection. Deliberately leave out hundreds of third-party integrations. Deliberately leave out multi-brand enterprise workspaces and compliance attestations. Finish by running the tests and listing the exact commands used. ## Required capabilities - Node.js 22 - Resend API key or SMTP credentials - self-hosted deploy target ## 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.
PRODUCT.md
# Reform product brief ## Problem The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Reform, publish a clean branded lead form with routing, notifications, and exports. The hard boundary is polished ux, spam controls, integrations, and reliable hosted delivery, plus integrations, deliverability, and workflow depth. ## Product outcome Publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with CSV export. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node.js 22 - Resend API key or SMTP credentials - self-hosted deploy target ## Explicit non-goals for v1 - polished UX, spam controls, integrations, and reliable hosted delivery - advanced branching - payment and CRM integrations - large template libraries - enterprise compliance ## 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 personal replacement for Reform in an empty repository. Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend; do not offer alternative stacks. The core loop is: publish a clean branded lead form, validate submissions, route and notify the owner, and provide a private response table with CSV export. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields. Publish each form at a stable slug with server-side validation and accessible labels. Add honeypot, rate limiting, submission-size limits, and a clear privacy notice. Store responses in SQLite and provide search, filters, detail view, and CSV export. Send an owner notification without placing submitted values in logs. Support a thank-you screen and one simple conditional branch. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out payment collection. Deliberately leave out hundreds of third-party integrations. Deliberately leave out multi-brand enterprise workspaces and compliance attestations. Finish by running the tests and listing the exact commands used. ## 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 Reform 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 · this prompt is generated from the build plan · improve it via PR
People still pay for Reform because a basic form is trivial; people pay when the form feeds a dependable business workflow and never loses a response. The recurring cost buys spam control, email delivery, storage, exports, accessibility, conditional logic, and integrations, not just the visible interface.
xpolished UX, spam controls, integrations, and reliable hosted delivery
xadvanced branching
xpayment and CRM integrations
xlarge template libraries
xenterprise compliance
share on X ↗"I just replaced Reform ($35/mo) with one prompt"
Don't feel like building it? These folks already made it free.
HeyFormTypeform's manners, minus the monthly rentopen source↗
OpnFormTally with a server bill instead of a subscriptionopen source↗no votes, no pay-to-list · just what's real
Reform pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/workspace | $0/workspace | Unlimited draft forms; 0 live published forms and therefore 0 collectible responses. |
| basic | $15/workspace | $12.50/workspace | Unlimited live forms and responses; basic integrations and branding controls. |
| pro | $35/workspace | $29.17/workspace | Unlimited live forms and responses; advanced integrations, routing and branding controls. |
free tierUnlimited draft forms, but 0 live published forms and therefore 0 collectible responses.
billingMonthly + annual; the live annual cards contain internally contradictory annual-total text, noted tier by tier.
hidden costsThe 14-day Pro trial requires a card and automatically begins paid Pro billing unless canceled.
verified 2026-08-12 · source ↗
Vibecode Reform
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal Reform replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does Reform cost?
Reform costs about $35/month (Pro, checked 2026-07-31), which is $420 per year. That's what you save by replacing it with one prompt.
What do I lose by replacing Reform?
Honestly: polished UX, spam controls, integrations, and reliable hosted delivery; advanced branching; payment and CRM integrations; large template libraries; enterprise compliance. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Reform?
Yes: HeyForm (Typeform's manners, minus the monthly rent) OpnForm (Tally with a server bill instead of a subscription) The prompt is for when you want it exactly your way.