Can I vibecode Crouton?

Build a comprehensive, local-first web application clone of the "Crouton" recipe and meal planning app in an empty repository. Use Next.js 15, React, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and configure it as a Progressive Web App (PWA). Do not offer alternative technology stacks.

The core objective is to replicate Crouton's streamlined workflow for collecting, organizing, planning, and cooking recipes, focusing on a premium mobile-first user experience.

### Core Features to Implement:
1. **Recipe Organization & Intelligent Import:**
   - Allow users to store recipes in custom folders and organize them using tags.
   - Implement an "Intelligent Import" feature where users can paste a URL, and the app automatically parses the webpage to extract the title, ingredients (with quantities and units), method steps, and image metadata. Provide fallback manual entry forms.
   - Include an ingredient scaling system so users can dynamically adjust quantities based on desired servings.

2. **Guided Cooking Mode:**
   - Create a step-by-step "Guided Cooking" interface. Show one instruction at a time in large text.
   - Allow users to tap on ingredients within a step to instantly view their required quantities.
   - Integrate automatic timer detection: parse method steps for time durations (e.g., "bake for 20 minutes") and provide a one-tap button to start a visual timer directly on the screen.

3. **Meal Planning & Grocery Lists:**
   - Build a weekly meal planning calendar view. Allow users to add saved recipes to specific days and add custom text notes.
   - Automatically generate consolidated grocery lists based on the ingredients from the planned meals for a given date range. Combine identical ingredients and allow users to check them off.

### Technical & Architecture Requirements:
- Make the application work fully locally on the first run using a single documented command.
- Store all user data locally by default to ensure privacy and owner control.
- Implement JSON import and export functionalities, ensuring users can backup their entire recipe library, meal plans, and grocery lists easily.
- Design the UI to be mobile-first, ensuring large touch targets and offline capabilities.
- Keep secrets in `.env`, provide `.env.example`. Include safe handling for unavailable external APIs.
- Build clear empty states, loading indicators, and recoverable error handling.
- Write focused unit tests for complex transformations (URL parsing and ingredient scaling) and at least one end-to-end happy path for adding a recipe and cooking it.
- Create a `README.md` containing setup instructions, architecture overview, and backup procedures.

### Explicit Exclusions:
- Do not implement user accounts, billing, telemetry, analytics, or a hosted cloud backend.
- Leave out direct integrations with physical smart thermometers or smart-home devices.
- Do not integrate with third-party grocery delivery APIs or retailer ordering systems.
- Skip building polished native iOS/Android clients.

Finish by running the test suite and providing the exact commands to verify the app.