Can I vibecode Fibery?

text
Build a highly polished, single-user replacement for the core flexible workspace loop of Fibery, focusing on providing a unified environment for rich documents and structured relational data. You must use exactly this technology stack: Next.js 15 (using the App Router), TypeScript for all logic, and SQLite for the backend database (accessed via an ORM of your choice, like Prisma or Drizzle). Do not introduce any alternative frameworks or databases.

Your primary job is to construct a dynamic, connected work management platform. Users must be able to define custom entity types (e.g., Projects, Tasks, Ideas, Bugs) and dynamically link them together in a relational schema (supporting one-to-many and many-to-many relationships). Start from an entirely empty folder and create the complete, working full-stack project.

A core requirement is to build a collaborative-style rich text document editor that supports bi-directional linking to the database entities. Users should be able to type a '/' command or use an '@' mention system to search for and link to any existing entity in the database directly within their text. Create multiple dynamic views for the stored data—such as Kanban boards, hierarchical nested lists, and robust table views—all of which read in real-time from the same SQLite backend. Include rudimentary automation concepts, such as automatically updating a parent project's status when all linked child tasks are marked as completed.

Deliver a visually striking, premium user interface featuring a refined dark mode. Utilize smooth gradients, glassmorphism for modal overlays, and avoid generic default colors. Use a sophisticated, muted background palette contrasted with vibrant accent colors for entity tags and status badges. Leverage a modern typography stack (like Inter or Roboto) for extreme legibility in dense data tables. Integrate subtle micro-animations (e.g., when expanding rows, dragging kanban cards, or opening documents) to ensure the interface feels responsive and alive.

The default mode must be single-user and entirely private. Store all data locally in SQLite. Do not add analytics, telemetry, advertising, or third-party authentication. Manage all secrets using a `.env` file. Populate the initial run with realistic sample data that clearly demonstrates relational links and bi-directional documents. The application must feature distinct visual states for empty data, loading, success, and validation errors. Provide a robust JSON import/export tool so users have complete control over their data.

Deliberately exclude enterprise features like granular permissions, extensive third-party API integrations, and real-time multiplayer editing via WebSockets. Write highly focused unit tests validating the relational data model and graph traversal logic, plus one comprehensive end-to-end smoke test. Supply a detailed README with setup instructions, architectural choices, and backup procedures. Add scripts for install, dev, test, build, and a production-style run. Ensure all tests pass before finalizing.