Can I vibecode Tody?

Build a personal replacement for Tody (a dynamic, condition-based household cleaning app) in an empty repository.
Use Next.js 15, TypeScript, TailwindCSS, SQLite, Drizzle ORM, and configure it as a local-first PWA to ensure it works well on mobile devices. Do not offer alternative stacks.

The core loop of this app revolves around condition-based tracking for household chores rather than rigid calendar schedules. Instead of cleaning because it's a specific day, users clean based on "actual need" or accumulated "dirtiness."

### Core Features to Implement:
1. **Condition-Based Chores & "Dirtiness" Metrics:**
   - Allow users to define chores by room or zone.
   - For each chore, the user can set a flexible frequency (e.g., every 3 weeks, every 5 days).
   - The app should display a visual "dirtiness" indicator (e.g., a progress bar or color-coded gauge from green to red) that slowly fills up based on the elapsed time compared to the expected frequency. This visual cue motivates users by showing the current state rather than a stressful deadline.
   
2. **Household Collaboration & Task Assignment:**
   - Support multiple household members.
   - Allow specific chores to be assigned to specific users, or left unassigned for anyone to grab.
   - When a chore is done, the user can claim credit for it, resetting the "dirtiness" meter to zero.
   - Maintain a neutral shared history of completed tasks to track who did what and when.

3. **Gamification & Focus Mode:**
   - Include optional gamification (e.g., simple points or streaks) for users when they claim credit for chores.
   - Add a "Focus Mode" that hides the overall list and presents only the most urgent ("dirtiest") tasks one by one to keep users in the flow while cleaning.

4. **Vacation/Pause Mode:**
   - Implement a pause feature so that if users are away on vacation, the "dirtiness" metrics freeze and don't overwhelm them when they return.

### Technical & UX Requirements:
- **Mobile-First UX:** Provide fast mobile-first capture with large, touch-friendly controls. Include clear visual indicators and modern aesthetics.
- **Offline & Sync:** Implement offline queueing and conflict-safe sync to one server, ensuring the PWA feels snappy even with poor connection.
- **State Management & Setup:** Include clear empty, loading, success, and recoverable error states.
- **Security & Portability:** Store data locally by default and make export straightforward (CSV/JSON). Keep data portable and owner-controlled. Put secrets in .env, ship .env.example.
- **Testing:** Write focused tests for the core logic (e.g., dirtiness calculation) and one end-to-end happy path.
- **Documentation:** Create a detailed README with setup, architecture, and backup steps.

### Exclusions:
- Do not add complex billing, telemetry, or a hosted control plane.
- Leave out broad smart-home integrations.
- Leave out native iOS/Android builds (stick to PWA).

Finish by running tests and listing the setup commands.