Can I vibecode Auritrack?

Build a comprehensive, AI-powered personal finance management web application to act as a robust alternative to Auritrack. The app should act as an intelligent assistant for expense tracking, budgeting, and financial insights without requiring direct bank connections. 

**Technology Stack:** 
- Frontend: Next.js with TailwindCSS for a modern, responsive UI.
- Backend: Next.js API routes or Node/Express.
- Database: SQLite (local-first, e.g., using better-sqlite3).
- AI Integration: Anthropic Claude API (claude-3-5-sonnet) or OpenAI API.

**Core Features & Requirements:**
1. **Natural Language Expense Logging:** Implement a chat interface on the dashboard where users can type transactions in plain English (e.g., 'Spent $45 on groceries at Whole Foods'). Call the AI API with a strict JSON schema to extract amount, payee, date, and category. Display the parsed transaction inline, allowing the user to review and edit it before saving.

2. **Smart Statement Imports:** Build an import feature supporting CSV and text-layer PDFs (using `pdf-parse`). Chunk the data and process it through the AI model to clean and categorize messy bank data. Present results in an interactive review table for user confirmation before saving. Implement robust deduplication logic based on date, amount, and payee to prevent duplicate entries.

3. **Flexible Budgeting & Goal Setting:** Create a budgeting module where users can set monthly spending limits for custom categories (auto-created by AI if new). Display real-time progress bars for each budget category that turn red upon overspending. Allow users to set financial goals (e.g., 'Emergency Fund') and allocate savings towards them.

4. **AI-Powered Financial Insights:** Develop a reports dashboard with interactive charts (e.g., Recharts) showing spending trends and category breakdowns. Include an 'Ask your data' chat box: users can ask questions ('How much did I spend on dining out last month?'), and the AI translates this into a secure, read-only SQL query, runs it, and explains the answer.

5. **Security & Privacy:** Store API keys securely in `.env`. Never log transaction data. Implement an automated nightly backup mechanism that retains the last 30 days of the SQLite database in a local `backups/` directory.

6. **Manual Fallbacks:** Provide standard CRUD forms for transactions, categories, and budgets as a manual fallback.

7. **Documentation:** Provide a detailed README explaining setup, API key configuration, and a warning about potential API costs for processing large statement imports.