Vibecode Formasty
track this build5 steps, step by step0%KINDA · weekend project
A form builder is one of the most one-shottable categories there is: a schema, a renderer, a responses table, a CSV export. An agent will get you a working multi-step form with conditional fields and an embed snippet in a single session, and for a personal signup form or client intake that is genuinely enough. The gaps are the boring parts nobody thinks about until they bite: email that actually lands in inboxes, spam that gets past a honeypot, file uploads you have to back up, and the dozen integrations that turn a response into a row in someone else's tool. You also inherit uptime, because a form that is down is a lead you never knew existed. Build it if the form is yours and the volume is low; pay if the form is a business process.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Formasty. 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 ===== # Formasty indie build ## Goal Build the smallest trustworthy replacement for the core Formasty workflow for one developer or a tiny team. ## Scope Define a form as a JSON schema in an admin UI, render it publicly as a multi-step page or embeddable iframe, and store every submission in SQLite with email notification 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: - Deliverability: their notification email is warmed and authenticated, your SMTP box is not - The integration shelf: Sheets, Slack, Notion, CRM, Zapier style webhooks with retries and mapping UI - Template library and builder polish, which is most of what you are paying for in a form tool - Payment fields, e-signature, and anything that needs a compliance story like a signed DPA - Uptime and CDN edge delivery, so a form on a busy page fails silently when your box does If those capabilities are essential, use Formasty 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 single-user, self-hosted form builder and response collector. Stack: Next.js 15 App Router, TypeScript, Tailwind, SQLite via better-sqlite3. No other hosted services. Data model: forms(id, slug, title, schema JSON, theme JSON, createdAt), responses(id, formId, payload JSON, meta JSON, createdAt), deliveries(id, responseId, url, status, attempts). Admin builder at /admin/forms/[id]: add, reorder, duplicate and delete fields. Field types: short text, long text, email, number, single select, multi select, dropdown, date, rating 1 to 5, file upload, consent checkbox, hidden field. Per field: label, help text, required flag, placeholder, and simple conditional visibility (show this field when field X equals value Y). Multi-step forms: fields grouped into steps, one step per screen, progress bar, back button, answers held in client state until final submit. Public form at /f/[slug]: server-rendered, mobile-first, keyboard navigable, and revalidated on the server so client validation is never the only check. Persist in-progress answers to localStorage keyed by form slug so a refresh does not wipe the form. File uploads write to ./uploads with a size cap and mime allowlist defined in the schema; store the relative path in the response payload. Spam control: hidden honeypot field, reject submissions completed in under 2 seconds, and a per-IP rate limit table in SQLite. No captcha, no third party. Notifications: on submit, send a plain text digest of the response over SMTP with nodemailer using SMTP_HOST, SMTP_USER, SMTP_PASS, NOTIFY_TO from .env. If those are unset, log and continue instead of erroring. Optional per-form webhook URL: POST the response JSON, 3 retries with backoff, log every attempt in deliveries. Responses view at /admin/forms/[id]/responses: table with one column per field, text search, date range filter, detail drawer, delete, and CSV export of the current filter. Embedding: an /embed/[slug] route plus a small public/embed.js that injects an iframe and auto-resizes it via postMessage. Theming per form: accent color, one of three system font stacks, light or dark, optional cover image, custom thank-you message, optional redirect URL. Auth: a single ADMIN_PASSWORD from .env and a signed httpOnly cookie session for all /admin routes. No user accounts, no OAuth, no analytics, no telemetry. Seed script creating two demo forms: a three-step onboarding survey with conditional fields, and a one-page contact form. Out of scope: payments, e-signatures, team accounts, template marketplace, A/B testing, AI form generation. Deliver a README with setup steps, a .env.example, a note on backing up form.db plus ./uploads, and a Dockerfile listening on port 3000. Ship working code, not scaffolding: npm install, npm run seed, npm run dev must yield a fillable form at /f/contact and a visible row in the responses table. ## Required capabilities - a small VPS or always-on box to host it - SMTP credentials for notification email - disk space and a backup habit for uploads and the SQLite file - your own domain if you want the embed to look credible ## 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 Formasty. 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 ===== # Formasty indie build ## Goal Build the smallest trustworthy replacement for the core Formasty workflow for one developer or a tiny team. ## Scope Define a form as a JSON schema in an admin UI, render it publicly as a multi-step page or embeddable iframe, and store every submission in SQLite with email notification 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: - Deliverability: their notification email is warmed and authenticated, your SMTP box is not - The integration shelf: Sheets, Slack, Notion, CRM, Zapier style webhooks with retries and mapping UI - Template library and builder polish, which is most of what you are paying for in a form tool - Payment fields, e-signature, and anything that needs a compliance story like a signed DPA - Uptime and CDN edge delivery, so a form on a busy page fails silently when your box does If those capabilities are essential, use Formasty 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 single-user, self-hosted form builder and response collector. Stack: Next.js 15 App Router, TypeScript, Tailwind, SQLite via better-sqlite3. No other hosted services. Data model: forms(id, slug, title, schema JSON, theme JSON, createdAt), responses(id, formId, payload JSON, meta JSON, createdAt), deliveries(id, responseId, url, status, attempts). Admin builder at /admin/forms/[id]: add, reorder, duplicate and delete fields. Field types: short text, long text, email, number, single select, multi select, dropdown, date, rating 1 to 5, file upload, consent checkbox, hidden field. Per field: label, help text, required flag, placeholder, and simple conditional visibility (show this field when field X equals value Y). Multi-step forms: fields grouped into steps, one step per screen, progress bar, back button, answers held in client state until final submit. Public form at /f/[slug]: server-rendered, mobile-first, keyboard navigable, and revalidated on the server so client validation is never the only check. Persist in-progress answers to localStorage keyed by form slug so a refresh does not wipe the form. File uploads write to ./uploads with a size cap and mime allowlist defined in the schema; store the relative path in the response payload. Spam control: hidden honeypot field, reject submissions completed in under 2 seconds, and a per-IP rate limit table in SQLite. No captcha, no third party. Notifications: on submit, send a plain text digest of the response over SMTP with nodemailer using SMTP_HOST, SMTP_USER, SMTP_PASS, NOTIFY_TO from .env. If those are unset, log and continue instead of erroring. Optional per-form webhook URL: POST the response JSON, 3 retries with backoff, log every attempt in deliveries. Responses view at /admin/forms/[id]/responses: table with one column per field, text search, date range filter, detail drawer, delete, and CSV export of the current filter. Embedding: an /embed/[slug] route plus a small public/embed.js that injects an iframe and auto-resizes it via postMessage. Theming per form: accent color, one of three system font stacks, light or dark, optional cover image, custom thank-you message, optional redirect URL. Auth: a single ADMIN_PASSWORD from .env and a signed httpOnly cookie session for all /admin routes. No user accounts, no OAuth, no analytics, no telemetry. Seed script creating two demo forms: a three-step onboarding survey with conditional fields, and a one-page contact form. Out of scope: payments, e-signatures, team accounts, template marketplace, A/B testing, AI form generation. Deliver a README with setup steps, a .env.example, a note on backing up form.db plus ./uploads, and a Dockerfile listening on port 3000. Ship working code, not scaffolding: npm install, npm run seed, npm run dev must yield a fillable form at /f/contact and a visible row in the responses table. ## Required capabilities - a small VPS or always-on box to host it - SMTP credentials for notification email - disk space and a backup habit for uploads and the SQLite file - your own domain if you want the embed to look credible ## 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 Formasty. 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 ===== # Formasty product brief ## Problem A form builder is one of the most one-shottable categories there is: a schema, a renderer, a responses table, a CSV export. An agent will get you a working multi-step form with conditional fields and an embed snippet in a single session, and for a personal signup form or client intake that is genuinely enough. The gaps are the boring parts nobody thinks about until they bite: email that actually lands in inboxes, spam that gets past a honeypot, file uploads you have to back up, and the dozen integrations that turn a response into a row in someone else's tool. You also inherit uptime, because a form that is down is a lead you never knew existed. Build it if the form is yours and the volume is low; pay if the form is a business process. ## Product outcome Define a form as a JSON schema in an admin UI, render it publicly as a multi-step page or embeddable iframe, and store every submission in SQLite with email notification and CSV export. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - a small VPS or always-on box to host it - SMTP credentials for notification email - disk space and a backup habit for uploads and the SQLite file - your own domain if you want the embed to look credible ## Explicit non-goals for v1 - Deliverability: their notification email is warmed and authenticated, your SMTP box is not - The integration shelf: Sheets, Slack, Notion, CRM, Zapier style webhooks with retries and mapping UI - Template library and builder polish, which is most of what you are paying for in a form tool - Payment fields, e-signature, and anything that needs a compliance story like a signed DPA - Uptime and CDN edge delivery, so a form on a busy page fails silently when your box does ## 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 single-user, self-hosted form builder and response collector. Stack: Next.js 15 App Router, TypeScript, Tailwind, SQLite via better-sqlite3. No other hosted services. Data model: forms(id, slug, title, schema JSON, theme JSON, createdAt), responses(id, formId, payload JSON, meta JSON, createdAt), deliveries(id, responseId, url, status, attempts). Admin builder at /admin/forms/[id]: add, reorder, duplicate and delete fields. Field types: short text, long text, email, number, single select, multi select, dropdown, date, rating 1 to 5, file upload, consent checkbox, hidden field. Per field: label, help text, required flag, placeholder, and simple conditional visibility (show this field when field X equals value Y). Multi-step forms: fields grouped into steps, one step per screen, progress bar, back button, answers held in client state until final submit. Public form at /f/[slug]: server-rendered, mobile-first, keyboard navigable, and revalidated on the server so client validation is never the only check. Persist in-progress answers to localStorage keyed by form slug so a refresh does not wipe the form. File uploads write to ./uploads with a size cap and mime allowlist defined in the schema; store the relative path in the response payload. Spam control: hidden honeypot field, reject submissions completed in under 2 seconds, and a per-IP rate limit table in SQLite. No captcha, no third party. Notifications: on submit, send a plain text digest of the response over SMTP with nodemailer using SMTP_HOST, SMTP_USER, SMTP_PASS, NOTIFY_TO from .env. If those are unset, log and continue instead of erroring. Optional per-form webhook URL: POST the response JSON, 3 retries with backoff, log every attempt in deliveries. Responses view at /admin/forms/[id]/responses: table with one column per field, text search, date range filter, detail drawer, delete, and CSV export of the current filter. Embedding: an /embed/[slug] route plus a small public/embed.js that injects an iframe and auto-resizes it via postMessage. Theming per form: accent color, one of three system font stacks, light or dark, optional cover image, custom thank-you message, optional redirect URL. Auth: a single ADMIN_PASSWORD from .env and a signed httpOnly cookie session for all /admin routes. No user accounts, no OAuth, no analytics, no telemetry. Seed script creating two demo forms: a three-step onboarding survey with conditional fields, and a one-page contact form. Out of scope: payments, e-signatures, team accounts, template marketplace, A/B testing, AI form generation. Deliver a README with setup steps, a .env.example, a note on backing up form.db plus ./uploads, and a Dockerfile listening on port 3000. Ship working code, not scaffolding: npm install, npm run seed, npm run dev must yield a fillable form at /f/contact and a visible row in the responses table. ## 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 Formasty capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Formasty indie build ## Goal Build the smallest trustworthy replacement for the core Formasty workflow for one developer or a tiny team. ## Scope Define a form as a JSON schema in an admin UI, render it publicly as a multi-step page or embeddable iframe, and store every submission in SQLite with email notification 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: - Deliverability: their notification email is warmed and authenticated, your SMTP box is not - The integration shelf: Sheets, Slack, Notion, CRM, Zapier style webhooks with retries and mapping UI - Template library and builder polish, which is most of what you are paying for in a form tool - Payment fields, e-signature, and anything that needs a compliance story like a signed DPA - Uptime and CDN edge delivery, so a form on a busy page fails silently when your box does If those capabilities are essential, use Formasty 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 single-user, self-hosted form builder and response collector. Stack: Next.js 15 App Router, TypeScript, Tailwind, SQLite via better-sqlite3. No other hosted services. Data model: forms(id, slug, title, schema JSON, theme JSON, createdAt), responses(id, formId, payload JSON, meta JSON, createdAt), deliveries(id, responseId, url, status, attempts). Admin builder at /admin/forms/[id]: add, reorder, duplicate and delete fields. Field types: short text, long text, email, number, single select, multi select, dropdown, date, rating 1 to 5, file upload, consent checkbox, hidden field. Per field: label, help text, required flag, placeholder, and simple conditional visibility (show this field when field X equals value Y). Multi-step forms: fields grouped into steps, one step per screen, progress bar, back button, answers held in client state until final submit. Public form at /f/[slug]: server-rendered, mobile-first, keyboard navigable, and revalidated on the server so client validation is never the only check. Persist in-progress answers to localStorage keyed by form slug so a refresh does not wipe the form. File uploads write to ./uploads with a size cap and mime allowlist defined in the schema; store the relative path in the response payload. Spam control: hidden honeypot field, reject submissions completed in under 2 seconds, and a per-IP rate limit table in SQLite. No captcha, no third party. Notifications: on submit, send a plain text digest of the response over SMTP with nodemailer using SMTP_HOST, SMTP_USER, SMTP_PASS, NOTIFY_TO from .env. If those are unset, log and continue instead of erroring. Optional per-form webhook URL: POST the response JSON, 3 retries with backoff, log every attempt in deliveries. Responses view at /admin/forms/[id]/responses: table with one column per field, text search, date range filter, detail drawer, delete, and CSV export of the current filter. Embedding: an /embed/[slug] route plus a small public/embed.js that injects an iframe and auto-resizes it via postMessage. Theming per form: accent color, one of three system font stacks, light or dark, optional cover image, custom thank-you message, optional redirect URL. Auth: a single ADMIN_PASSWORD from .env and a signed httpOnly cookie session for all /admin routes. No user accounts, no OAuth, no analytics, no telemetry. Seed script creating two demo forms: a three-step onboarding survey with conditional fields, and a one-page contact form. Out of scope: payments, e-signatures, team accounts, template marketplace, A/B testing, AI form generation. Deliver a README with setup steps, a .env.example, a note on backing up form.db plus ./uploads, and a Dockerfile listening on port 3000. Ship working code, not scaffolding: npm install, npm run seed, npm run dev must yield a fillable form at /f/contact and a visible row in the responses table. ## Required capabilities - a small VPS or always-on box to host it - SMTP credentials for notification email - disk space and a backup habit for uploads and the SQLite file - your own domain if you want the embed to look credible ## 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
# Formasty product brief ## Problem A form builder is one of the most one-shottable categories there is: a schema, a renderer, a responses table, a CSV export. An agent will get you a working multi-step form with conditional fields and an embed snippet in a single session, and for a personal signup form or client intake that is genuinely enough. The gaps are the boring parts nobody thinks about until they bite: email that actually lands in inboxes, spam that gets past a honeypot, file uploads you have to back up, and the dozen integrations that turn a response into a row in someone else's tool. You also inherit uptime, because a form that is down is a lead you never knew existed. Build it if the form is yours and the volume is low; pay if the form is a business process. ## Product outcome Define a form as a JSON schema in an admin UI, render it publicly as a multi-step page or embeddable iframe, and store every submission in SQLite with email notification and CSV export. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - a small VPS or always-on box to host it - SMTP credentials for notification email - disk space and a backup habit for uploads and the SQLite file - your own domain if you want the embed to look credible ## Explicit non-goals for v1 - Deliverability: their notification email is warmed and authenticated, your SMTP box is not - The integration shelf: Sheets, Slack, Notion, CRM, Zapier style webhooks with retries and mapping UI - Template library and builder polish, which is most of what you are paying for in a form tool - Payment fields, e-signature, and anything that needs a compliance story like a signed DPA - Uptime and CDN edge delivery, so a form on a busy page fails silently when your box does ## 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 single-user, self-hosted form builder and response collector. Stack: Next.js 15 App Router, TypeScript, Tailwind, SQLite via better-sqlite3. No other hosted services. Data model: forms(id, slug, title, schema JSON, theme JSON, createdAt), responses(id, formId, payload JSON, meta JSON, createdAt), deliveries(id, responseId, url, status, attempts). Admin builder at /admin/forms/[id]: add, reorder, duplicate and delete fields. Field types: short text, long text, email, number, single select, multi select, dropdown, date, rating 1 to 5, file upload, consent checkbox, hidden field. Per field: label, help text, required flag, placeholder, and simple conditional visibility (show this field when field X equals value Y). Multi-step forms: fields grouped into steps, one step per screen, progress bar, back button, answers held in client state until final submit. Public form at /f/[slug]: server-rendered, mobile-first, keyboard navigable, and revalidated on the server so client validation is never the only check. Persist in-progress answers to localStorage keyed by form slug so a refresh does not wipe the form. File uploads write to ./uploads with a size cap and mime allowlist defined in the schema; store the relative path in the response payload. Spam control: hidden honeypot field, reject submissions completed in under 2 seconds, and a per-IP rate limit table in SQLite. No captcha, no third party. Notifications: on submit, send a plain text digest of the response over SMTP with nodemailer using SMTP_HOST, SMTP_USER, SMTP_PASS, NOTIFY_TO from .env. If those are unset, log and continue instead of erroring. Optional per-form webhook URL: POST the response JSON, 3 retries with backoff, log every attempt in deliveries. Responses view at /admin/forms/[id]/responses: table with one column per field, text search, date range filter, detail drawer, delete, and CSV export of the current filter. Embedding: an /embed/[slug] route plus a small public/embed.js that injects an iframe and auto-resizes it via postMessage. Theming per form: accent color, one of three system font stacks, light or dark, optional cover image, custom thank-you message, optional redirect URL. Auth: a single ADMIN_PASSWORD from .env and a signed httpOnly cookie session for all /admin routes. No user accounts, no OAuth, no analytics, no telemetry. Seed script creating two demo forms: a three-step onboarding survey with conditional fields, and a one-page contact form. Out of scope: payments, e-signatures, team accounts, template marketplace, A/B testing, AI form generation. Deliver a README with setup steps, a .env.example, a note on backing up form.db plus ./uploads, and a Dockerfile listening on port 3000. Ship working code, not scaffolding: npm install, npm run seed, npm run dev must yield a fillable form at /f/contact and a visible row in the responses table. ## 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 Formasty 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
Because forms are load-bearing. The moment a form is collecting real leads, applications, or client files, the cost of it quietly breaking exceeds any subscription, and you stop wanting to own the email deliverability, spam waves, and file storage yourself. Paid form tools also sell speed: a decent one gets a branded, conditional, multi-step form live in ten minutes with a template, which is faster than reviewing an agent's output. The self-hosted version wins when it is one form you control on a site you already run.
xDeliverability: their notification email is warmed and authenticated, your SMTP box is not
xThe integration shelf: Sheets, Slack, Notion, CRM, Zapier style webhooks with retries and mapping UI
xTemplate library and builder polish, which is most of what you are paying for in a form tool
xPayment fields, e-signature, and anything that needs a compliance story like a signed DPA
xUptime and CDN edge delivery, so a form on a busy page fails silently when your box does
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Formasty ($29/mo) with one prompt"
Vibecode Formasty
Kinda. The core of Formasty is buildable in a weekend with the prompt on this page, but there are real gaps: Deliverability: their notification email is warmed and authenticated, your SMTP box is not, The integration shelf: Sheets, Slack, Notion, CRM, Zapier style webhooks with retries and mapping UI. Read the honest list above before committing.
How much does Formasty cost?
Formasty costs about $29/month (Pro, checked 2026-08-18), which is $348 per year.
What do I lose by replacing Formasty?
Honestly: Deliverability: their notification email is warmed and authenticated, your SMTP box is not; The integration shelf: Sheets, Slack, Notion, CRM, Zapier style webhooks with retries and mapping UI; Template library and builder polish, which is most of what you are paying for in a form tool; Payment fields, e-signature, and anything that needs a compliance story like a signed DPA; Uptime and CDN edge delivery, so a form on a busy page fails silently when your box does. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Formasty?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.