Can I vibecode Webstudio Cloud?

Build a highly capable, detailed personal alternative to Webstudio Cloud. This should not be a trivial clone, but a robust visual website builder tailored for a single developer or designer to create, edit, and publish high-performance web pages. 
Use exactly this technology stack: Next.js 15 (App Router), TypeScript, Tailwind CSS for the editor UI, and SQLite with Prisma for local storage of project data.
The primary job of this application is to serve as a focused visual website builder and generator. It must allow the user to edit structured page sections, preview responsive layouts in real-time across different device widths (mobile, tablet, desktop), and ultimately publish the site as static files ready for deployment to any edge network or static host.
Start from a completely empty repository. Initialize the project and build the entire working application.
The application must operate in a single-user, private mode by default. Do not implement complex multi-user role-based access control.
The visual editor should feature a drag-and-drop interface for structural elements (like containers, grids, flex layouts) and UI components (headings, paragraphs, images, buttons). 
Provide a comprehensive styling panel on the right sidebar that gives the user granular control over CSS properties. This must include margin, padding, typography, colors, borders, and effects. The styling panel should map directly to a design token system, ensuring that colors and fonts can be managed globally as reusable tokens rather than ad-hoc inline styles.
Include a headless CMS integration feature: the builder should allow users to connect an external REST API or use the local SQLite database to fetch dynamic data. The user should be able to bind this data to UI components, such as mapping an array of blog posts to a repeating card component.
Include a foundational "AI-assisted design" input where a user can enter a natural language prompt, and (if an OpenAI key is provided in the .env) it calls a mock or real endpoint to suggest a component layout JSON structure.
The editor must maintain its state (e.g., using React Context or Zustand) to support undo/redo functionality and canvas selection.
Project schemas and page tree structures must be saved as JSON payloads within the local SQLite database. 
Include an export function that transforms the visual JSON tree into clean, semantic HTML/CSS or React components. 
Add a "Publish" feature that triggers a build of the static site into a `dist/` folder, simulating edge-optimized static delivery.
Ensure the interface is highly polished. Include clear loading indicators, validation errors, success toasts, and handle failure states gracefully. Ensure accessible keyboard navigation and focus management.
Exclude managed hosting, collaboration, team workspaces, or third-party accounts.
Provide a thorough README outlining local setup, database seeding, how to use the editor, and how to serve the exported static files. Add scripts for installation, development, testing, and building. Add end-to-end smoke tests using Playwright for the drag-and-drop workflow.