Formstack Forms

Build me a focused forms, surveys and lead capture workflow for the personal core of Formstack Forms. Requirements:

- Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend. Store responses in SQLite and provide search, filters, detail view, and CSV export.
- Paid product context: Build a secure low-volume form workflow with approvals and exports. Build only this DIY scope: Build a secure low-volume public form workflow with approvals, validate submissions, notify the owner, and provide a private response table with CSV export.
- 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. Send an owner notification without placing submitted values in logs. Support a thank-you screen and one simple conditional branch.
- Use a local web page with input, progress, review, and export views. Required input or access: Resend API key or SMTP credentials; self-hosted deploy target. Keep credentials in .env.
- Recovery: Add honeypot, rate limiting, submission-size limits, and a clear privacy notice.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A malformed submission must not create a partial response; editing the form must not reinterpret prior answers.
- Out of scope: enterprise compliance, workflow, integrations, support, and regulated deployments; advanced branching. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Formstack Forms

## Project scope
Build a secure low-volume public form workflow with approvals, validate submissions, notify the owner, and provide a private response table with CSV export.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Formstack Forms, build a secure low-volume form workflow with approvals and exports. The hard boundary is enterprise compliance, workflow, integrations, support, and regulated deployments, plus integrations, deliverability, and workflow depth.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Node.js 22
- Resend API key or SMTP credentials
- self-hosted deploy target

## Stack and architecture
- Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend.
- Store responses in SQLite and provide search, filters, detail view, and CSV export.
- Interface for this forms, surveys and lead capture workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Add honeypot, rate limiting, submission-size limits, and a clear privacy notice.
- Keep API keys and OAuth secrets in .env; redact them from logs, generated files, and error responses.
- State the practical limit: enterprise compliance, workflow, integrations, support, and regulated deployments.

## Agent implementation rules
- Project rule, data: Store responses in SQLite and provide search, filters, detail view, and CSV export.
- Project rule, behavior: Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields.
- Project rule, recovery: Add honeypot, rate limiting, submission-size limits, and a clear privacy notice.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this forms, surveys and lead capture operation with sample or user-owned data: Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields.
- Show a concrete result or export: Store responses in SQLite and provide search, filters, detail view, and CSV export.
- State the practical limit: enterprise compliance, workflow, integrations, support, and regulated deployments.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend. Store responses in SQLite and provide search, filters, detail view, and CSV export.
2. Phase 2, implement: Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields.
3. Phase 3, implement: Publish each form at a stable slug with server-side validation and accessible labels.
4. Phase 4, review and output: 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.
5. Phase 5, recovery and acceptance: Add honeypot, rate limiting, submission-size limits, and a clear privacy notice. Verify this invariant with a saved fixture: A malformed submission must not create a partial response; editing the form must not reinterpret prior answers. State the practical limit: enterprise compliance, workflow, integrations, support, and regulated deployments.

## Paid-product capabilities outside this build
- enterprise compliance, workflow, integrations, support, and regulated deployments
- advanced branching
- payment and CRM integrations
- large template libraries
- enterprise compliance

## Implementation prompt
Build me a focused forms, surveys and lead capture workflow for the personal core of Formstack Forms. Requirements:

- Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend. Store responses in SQLite and provide search, filters, detail view, and CSV export.
- Paid product context: Build a secure low-volume form workflow with approvals and exports. Build only this DIY scope: Build a secure low-volume public form workflow with approvals, validate submissions, notify the owner, and provide a private response table with CSV export.
- 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. Send an owner notification without placing submitted values in logs. Support a thank-you screen and one simple conditional branch.
- Use a local web page with input, progress, review, and export views. Required input or access: Resend API key or SMTP credentials; self-hosted deploy target. Keep credentials in .env.
- Recovery: Add honeypot, rate limiting, submission-size limits, and a clear privacy notice.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A malformed submission must not create a partial response; editing the form must not reinterpret prior answers.
- Out of scope: enterprise compliance, workflow, integrations, support, and regulated deployments; advanced branching. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.