Can I vibecode Feathery?

text
Build a highly capable personal replacement for Feathery, beginning in an empty repository. You must use exactly the following technology stack: Next.js 15 (App Router), TypeScript, Tailwind CSS for styling, SQLite for the database, Drizzle ORM for data modeling, and Resend for transactional email delivery. Do not deviate from this stack or offer alternative frameworks.

Your primary objective is to build a robust platform for creating and hosting multi-step application forms. The application must feature a form builder with reusable field groups, client and server-side validation, and a public-facing URL for each published form. Upon a successful form submission, the system must validate the data, notify the form owner via email, and store the submission in a private, searchable dashboard with a CSV export capability.

Ensure the first-run experience works seamlessly locally with a single, well-documented terminal command. By default, store all user and submission data locally in the SQLite database. Ensure that exporting the data (e.g., via CSV) is a straightforward, first-class feature. Securely manage all secrets (such as the Resend API key) within a `.env` file, supply a `.env.example`, and never commit sensitive credentials to the repository.

Design the form builder to support a variety of inputs: short text, long text, email, number, select/dropdown, radio buttons, checkboxes, and basic file uploads (stored locally). Each form must be accessible via a stable, unique slug. Ensure all generated forms utilize accessible semantic HTML labels and robust server-side validation. Implement security best practices including a honeypot field for spam prevention, basic IP rate limiting, strict payload size limits for file uploads, and a configurable privacy notice.

The owner's dashboard must read from SQLite and provide capabilities to search, filter, and view detailed individual responses. The email notification sent via Resend must alert the owner of a new submission but, for security reasons, must NOT contain the submitted private values in the email body itself. Include a customizable thank-you screen and support for at least one simple conditional logic branch (e.g., show/hide a field based on a previous answer).

The application must possess clear visual states for empty dashboards, loading transitions, success confirmations, and recoverable error screens. Strongly validate all inputs, sanitize uploaded filenames, and handle failures of the Resend API gracefully without crashing the app. Write focused unit tests covering the core form validation and transformation logic, along with one end-to-end test verifying the happy path from form creation to submission. Create a comprehensive README documenting the setup, architecture, data location, and backup strategy. Deliberately exclude complex features like payment collection, extensive third-party CRM integrations, and multi-brand enterprise compliance. Run all tests and builds, explicitly resolving any errors before finalizing the code.