Can I vibecode SmartSuite?

Build a highly polished, premium personal replacement for SmartSuite, a comprehensive Work OS, in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks.
The core loop is: model structured records for a team, provide grid, form, kanban, and filtered views, add dashboards, and expose a documented API.

KEY FEATURES TO IMPLEMENT:
1. Structured Hierarchy: Organize data systematically using a clear hierarchy (Workspaces -> Solutions -> Tables -> Records -> Fields).
2. Diverse Data Visualizations: Build flexible views from a single canonical schema, including Grid (spreadsheet-style), Kanban boards, Forms, and detailed Record views.
3. Powerful Dashboards: Create a unified dashboard interface that provides visual insights, metrics, and KPI summaries aggregated from underlying table data.
4. Advanced Field Types & Relations: Support rich field types including text, number, currency, date, boolean, select, multi-select, and relational fields between tables.
5. Task & Project Management Foundation: Ensure the schema and UI inherently support task tracking, assignments, status updates, and dynamic filtering.

PREMIUM UI/UX DESIGN AESTHETICS:
- Deliver a state-of-the-art enterprise aesthetic that feels incredibly premium, eliminating the clunkiness of traditional data tools.
- Implement a modern, clean design system using harmonious, sophisticated color palettes (e.g., sleek white/light gray backgrounds with vibrant primary accents).
- Utilize high-quality typography (like Inter or Roboto) to ensure dense data grids remain highly legible and beautifully spaced.
- Incorporate subtle micro-animations for interactions like dragging Kanban cards, opening record modals, or filtering views.
- Ensure the interface feels responsive and alive, using skeleton loaders, smooth transitions, and hover states that guide the user's focus effortlessly.

TECHNICAL REQUIREMENTS:
Make the first run work locally with one documented command (e.g., docker-compose up).
Store all user data locally. Put secrets in .env, ship .env.example.
Add role-based permissions, optimistic concurrency checks, audit history, and trash restore.
Provide CSV import/export and a token-authenticated REST API generated from the schema.
Ship migrations, seed data (with realistic multi-table examples), backups, and health checks.
Include clear empty, loading, success, and recoverable error states.
Add robust input validation on both client and server.
Write focused tests for the core data transformations and one end-to-end happy path.
Create a comprehensive README with setup, architecture, and backup steps.
Do not add billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out full spreadsheet formula compatibility and large-enterprise governance.
Finish by running the tests and listing the exact commands used.