Can I vibecode MeisterTask?

text
Build a premium, highly visual personal replacement for MeisterTask in an empty repository.
Use Next.js 15, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks.
The core loop is: run visual project boards with recurring tasks, timelines, milestones, comments, lightweight reporting, and a searchable activity history.

DESIGN & UI AESTHETICS (CRITICAL):
Create a stunning, premium UI that feels responsive and alive, drawing inspiration from modern European design principles.
- Use a harmonious color palette with subtle gradients (e.g., sleek dark mode with vibrant accent colors for different project tags). Avoid plain primary colors.
- Use modern typography (e.g., Inter or Outfit) with excellent hierarchy and spacing.
- Implement glassmorphism for modal overlays and dropdowns to add depth.
- Incorporate subtle micro-animations (e.g., smooth transitions when dragging/dropping cards on the Kanban board, hover effects on buttons, satisfying state changes when completing tasks).
- The "Home" hub should be a clean, centralized dashboard that aggregates tasks, notifications, and personal notes into a single beautiful view.

KEY FEATURES TO IMPLEMENT:
- Centralized "Home" Hub: A beautifully designed dashboard for individuals to manage daily work, tasks, and notifications across all active projects.
- Flexible Kanban-style Boards: Drag-and-drop boards with customizable sections and labels.
- Recurring Tasks & Automations: Simple rule-based workflow automations (e.g., auto-assigning when moving to a new column).
- Built-in Time Tracking: A visually pleasing widget on task cards to track time seamlessly.
- Personal Agenda: A private space to plan daily focus.
- Lightweight Reporting: Beautiful charts showing time spent and task completion rates.

TECHNICAL REQUIREMENTS:
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement projects, members, issues, labels, time logs, and automations.
Provide list, kanban, and simple timeline views backed by one canonical issue model.
Add comments, mentions, assignments, watchers, and a complete activity log.
Add search, CSV import or export, and daily database backups.
Ship Docker Compose, health checks, migrations, seed data, and an admin recovery command.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out hundreds of external integrations, enterprise portfolio planning, SSO, and native mobile clients.
Finish by running the tests and listing the exact commands used.