Can I vibecode TimeHero?

Build a deliberately narrow personal substitute for TimeHero, not a full clone.
Use exactly this stack: Tauri 2 + React + TypeScript + SQLite.
Primary job: Build a local desktop utility that captures the essential automatic work planning and AI-driven adaptive scheduling workflow with keyboard-first controls and local storage.
Your design aesthetic must be outstanding. Create a dynamic and vibrant UI with a sleek dark mode, utilizing HSL tailored colors and a modern Google Font like Outfit or Inter. Add fluid micro-animations when tasks shuffle and reorganize themselves, and use glassmorphic panels for editing task details. It must look premium and eliminate the fatigue of traditional manual to-do lists visually.
Implement core TimeHero features: an adaptive scheduling engine that automatically parses task durations, deadlines, and priorities to intelligently slot work into a daily calendar view. If a task runs over time or is delayed, the UI should visually auto-adjust and reorganize remaining tasks in real-time.
Include Smart Risk Detection—a visual indicator (using gradients or glowing borders) alerting the user if a project is at risk of missing a deadline based on current velocity.
Add Natural Language Processing (NLP) input capabilities so users can quickly type 'Finish report by Friday 5pm takes 2 hours high priority' and the system structures it into a scheduled task.
Start from an empty folder and create the complete working project. Make the default mode single-user and private. Store user data locally. Put every secret and external credential in .env and provide .env.example.
Use realistic sample data that is clearly labelled and easy to delete to showcase the automatic shuffling.
Include clear, beautiful empty, loading, validation, success, and failure states with thoughtful interactions.
Add import and export capabilities. Use accessible keyboard navigation, labels, focus states, and sensible contrast. Validate untrusted input and never log secrets.
Deliberately exclude these paid-product advantages: deep operating-system edge-case coverage; vendor-maintained updates; heavy enterprise collaborative workspaces.
Where an external API is optional (like a Google Calendar sync placeholder), keep the app useful without it and explain the degraded mode.
Write focused unit tests for the data model and the most important adaptive scheduling workflow. Add one end-to-end smoke test that proves the core loop works.
Create a README with setup, permissions, architecture, data location, backup, and limitations. Add scripts for install, development, test, build, and a production-style local run.
Run the tests and build before finishing, then fix errors rather than merely describing them.