Your Build Plan

Step 1: Lock the version 1 spec

I'm building "HabitStreak", a tracking app: A mobile habit tracker app for iPhone and Android with daily reminders and streaks.
Turn this into a one-page spec for version 1 using exactly these pieces, and push back if anything is unnecessary:

Screens:
- Welcome / onboarding (pick your first habits)
- Today: habits to check off
- Add / edit habit
- Progress: streaks and weekly chart
- Settings & reminders

Data:
- users (id, email, display_name, timezone, created_at)
- habits (id, user_id, name, schedule e.g. daily or Mon/Wed/Fri, reminder_time, color, archived, created_at)
- habit_checkins (id, habit_id, user_id, date, done, note)

Must-have features:
- Check off a habit in one tap
- Streak counter and weekly progress chart
- Daily reminder at the user's chosen time
- Edit or archive habits

List what is OUT of scope for version 1 (e.g. web version, admin analytics, referrals). Keep it under 250 words.

✅ Done when: you can explain the app in one sentence and the spec fits on one page.

Step 2: Build the first screen

Create an Expo (React Native) mobile app called "HabitStreak". Start with ONLY the "Today: habits to check off" screen, using realistic placeholder habits. Style: clean, friendly, large tap targets (min 44px), one accent colour, system font. Don't add any other screens yet.

✅ Done when: the "Today: habits to check off" screen looks right in the phone preview.

Step 3: Add the remaining screens

Now add these screens with placeholder content, matching the style of the first screen:
- Welcome / onboarding (pick your first habits)
- Add / edit habit
- Progress: streaks and weekly chart
- Settings & reminders
Add a bottom tab bar so I can move between them. No database yet.

✅ Done when: you can click through every screen.

Step 4: Empty, loading and error states

For every screen, add: an empty state (e.g. "No habits yet, add your first one" with a button), a loading state, and a friendly error message with a retry button. Change nothing else.

✅ Done when: a brand-new user never sees a blank screen.

Step 5: Create the database

Connect Firebase. Create these collections with sensible field types and required fields:
- users (id, email, display_name, timezone, created_at)
- habits (id, user_id, name, schedule e.g. daily or Mon/Wed/Fri, reminder_time, color, archived, created_at)
- habit_checkins (id, habit_id, user_id, date, done, note)
Add 10 realistic sample habits. Explain in plain English what each one stores.

✅ Done when: you can see the sample data in the database dashboard.

Step 6: Connect screens to real data

Replace all placeholder content with real data from Firebase. Make create, edit and delete work for habits, with validation and a confirm step before deleting. After each change the screen should update without a manual refresh.

✅ Done when: a habit you add survives closing and reopening the app.

Step 7: Sign-up, login and data privacy

Add sign-up, login, logout and password reset using Firebase Authentication (email + Sign in with Apple + Google; Apple requires Sign in with Apple if you offer other social logins on iOS). Write Firestore security rules so users can only read and write their own documents; never leave test-mode rules on. Add an account screen with a Delete account button (Apple requires in-app account deletion).

✅ Done when: two test accounts can't see each other's data.

Step 8: Core logic: check-ins and streaks

Add the core habit logic: tapping a habit on the Today screen creates or removes today's row in habit_checkins. Calculate the current streak (consecutive scheduled days completed) and the best streak, and show a 7-day progress chart on the Progress screen. Respect each user's timezone so "today" is correct.

✅ Done when: the main feature works for a real user from start to finish.

Step 9: Notifications

Add push notifications with expo-notifications: ask permission after the user's first habit (not on launch), store the Expo push token per user, and send a daily reminder at each habit's reminder_time. Add an on/off switch in Settings.

✅ Done when: a reminder arrives on a real phone.

Step 10: Owner / admin view

Add an admin area only I can access (check my email/role on the server): see all users and habits, search them, and fix or remove bad data. Show simple numbers: total users, new this week.

✅ Done when: you can answer 'how many people used it this week?'.

Step 11: Polish, speed and accessibility

Review the whole app screen by screen: fix confusing labels, make text readable (min 16px), add alt text and labels for screen readers, ensure good colour contrast, and make it fast on a slow phone. List the changes before making them and change nothing else.

✅ Done when: a friend can use it without you explaining anything.

Step 12: Analytics and feedback

Add PostHog with these events only: signed_up, habit_created, returned_next_day. Add a small "Send feedback" link that emails me. Don't track personal data in events.

✅ Done when: you can see a sign-up → first habit funnel.

Step 13: Prepare store builds

Prepare the app for the stores with Expo EAS: set the app name "HabitStreak", a unique bundle identifier (e.g. com.yourname.habitstreak), version 1.0.0, app icon (1024×1024) and splash screen in app.json. Create eas.json with development, preview and production profiles. Remove test data and switch any keys to production. Give me the exact commands to run.

✅ Done when: an EAS build installs on your own phone.

Diagnose before fixing

Don't change any code yet. Here is the exact error and what I did right before it:
[paste error]
Explain in plain English what is causing it, list the 2 most likely causes, and propose the smallest possible fix. Wait for my OK.

Break a fix loop

We've tried to fix this 3 times and it keeps breaking. Stop. Revert your last changes to the files involved, then describe the simplest different approach that avoids the problem entirely. Change only the files needed.

Protect what works

Only change [screen/feature]. Do not modify any other file, component, style or database table. Before editing, list exactly which files you will touch.

Check the data layer

The screen shows nothing / the wrong data. Check, step by step: is the user logged in, does the security rule allow this read, does the query return rows, and is the result mapped to the screen? Report each check's result before fixing.

Reset Bolt.new's context

Summarise this project for a fresh session: what the app does, the screens, the data tables, what works, and the one thing currently broken. Keep it under 200 words.