Can I vibecode Draftbit?

text
Build a personal, local-first replacement for Draftbit, starting in a completely empty repository. You must use exactly the following technology stack: Next.js 15 (using the App Router), TypeScript for all frontend and backend code, Tailwind CSS for styling, PostgreSQL for the database, Drizzle ORM for database access, and Docker Compose for local orchestration. Under no circumstances should you offer alternative technology stacks or introduce other major frameworks.

The core product loop you must build is a visual mobile app builder that allows a user to compose a React Native application using a set of constrained, pre-built screen templates. The user must be able to connect the app to one approved data source, export the resulting React Native source code, and trigger a simple deploy script suitable for a small, trusted team. The first-run experience must work seamlessly locally, executed by one clearly documented command via Docker Compose. 

Store all user-generated data (e.g., app configurations, schemas) locally by default. Design an intuitive export process so the user can download their raw project files at any time. Manage all secrets and external API credentials using a `.env` file, include a `.env.example`, and guarantee that credentials are never hardcoded or committed to git. 

Implement a visual schema editor supporting the following data types: text, number, boolean, date, enum, and relations. Using this schema, automatically generate corresponding list, detail, create, edit, and kanban views. Implement basic role-based read and write access rules supporting 'admin' and 'member' roles. Support configuring exactly one external REST connector, ensuring credentials for this connector are encrypted in the database and explicitly mapped to the schema fields. 

Add an activity log that tracks changes, support CSV data import and export, basic database backups, and application health checks. Ship a Docker Compose configuration that automatically runs database migrations and seeds an example workspace with realistic sample data. 

The interface must explicitly handle clear empty states, loading indicators, success messages, and recoverable error boundaries. Implement strict input validation on both the client and server sides, ensure filenames are safe, and gracefully handle any unavailable external APIs. Write focused unit tests for the core schema transformation logic and include at least one end-to-end happy path test (e.g., using Playwright or Cypress). 

Create a comprehensive README detailing the initial setup, architectural decisions, permission models, data location, and backup procedures. Deliberately exclude features such as arbitrary user-authored code execution in the browser, a broad third-party integration marketplace, compilation of native mobile binaries (APK/IPA), and enterprise-grade compliance features. Do not add billing, telemetry, or analytics. Finish the process by running all tests, confirming the build works, and listing the exact terminal commands used.