crave

Phase 5/6 of Crave — build the Account tab (profile, saved addresses, payment methods (mock), appearance picker (system/light/dark), notifications toggles, favorites list, sign-out). Guest mode shows a "Sign in" prompt and disables persistent sections. Use after crave-order-flow.

Phase 2 (part 2) of Crave — build the typed mock API layer (src/services/api), the AsyncStorage persistence wrappers (src/services/storage), and the Zustand cart + session stores with persist middleware. The api module is the SINGLE swap point for a real backend later — every screen reads through it via hooks. Includes the timer-driven order-status advance (Confirmed → Preparing → Picked up → On the way → Delivered). Use after crave-mock-data.

Phase 4 of Crave — build the core browsing surfaces by composing components against the mock API. Fills in Home (LocationHeader + SearchPill + categories + filter chips + feed sections + pull-to-refresh + skeletons), Search (debounced query + filter sheet), Restaurant detail (collapsing hero + sticky category strip + menu sections), and Item detail modal (option groups with live price + quantity + add-to-cart fly animation). Sticky CartBar appears whenever cart is non-empty. Use after crave-routing-auth.

Phase 1 of Crave — build the entire in-house component library in src/components per DESIGN-SPEC §5 (Button, Chip, CategoryIcon, RestaurantCard + wide/small, MenuItemRow, SearchPill, LocationHeader, CartBar, QuantityStepper, RatingStars, Badge, SectionHeader, Sheet, Skeleton, EmptyState, Stepper, MapView placeholder) plus the cross-cutting Reanimated motion patterns (press spring 0.97, cart fly, skeleton shimmer, sticky CartBar slide). Every component reads tokens from useTheme — no hardcoded design values. Use after crave-theme.

Build the /_kitchen-sink showcase route — a single screen that renders every component from src/components in both light and dark themes for visual audit. Includes a top theme-toggle and an "Exercise mock API" panel that calls each api.* method and prints the result. Used continuously across Phases 1–5 to catch drift; removed in Phase 6 (crave-qa-polish).

Phase 2 (part 1) of Crave — author the seed dataset in src/mocks. Produces 12–18 realistic restaurants across cuisines (rating, ETA range, fee, price level, badges, hero image with blurhash) plus 3–5 menu sections per restaurant (items with name, description, priceMinor, photo, popular flag, option groups), plus the categories row (Deals, Grocery, Pizza, Sushi, Burgers, Breakfast, Healthy, Dessert, Coffee). All money as integer minor units + currency. Use after crave-components.

Phase 5 of Crave — complete the order loop. Builds Cart (grouped items with steppers, promo code, price summary), Checkout (mock address picker, time selector ASAP/schedule, mock payment, tip selector, place-order CTA), Order Tracking (MapView placeholder with animated courier + Stepper advancing on a timer + courier card + delivered rating prompt), and the Orders tab (active + past with reorder). Money math is integer minor units throughout. Use after crave-browse.

Phase 6 of Crave — release-ready polish & QA. Sweeps empty/error/loading states across every screen, adds haptics on add-to-cart and place-order, runs an accessibility pass (VoiceOver/TalkBack, AA contrast, Dynamic Type, reduce-motion), enforces tsc + lint + expo-doctor are clean, removes debug routes (/_kitchen-sink), and finalizes app icon + splash + adaptive icon. Optionally produces an EAS preview build. Final phase — run after every other crave-* skill.

Phase 3 of Crave — wire the full Expo Router graph (root layout with providers + splash control + storage restore, (auth) group with welcome + sign-in, (tabs) group with Home/Search/Orders/Account, plus restaurant/[id], item/[id] modal, cart, checkout, order/[id] routes) AND build the mock authentication flow (accepts any email/phone OR Continue as guest, persisted via session store, gating checkout/orders). Use after crave-api-storage.

Phase 0 of Crave — scaffold the Expo + React Native app IN PLACE at the root of crave/ (alongside _props/), verify Node/npm/Expo versions against latest stable on the web, install dependencies via expo install, configure TypeScript path alias and app.json (newArchEnabled + typedRoutes), and create the app/ + src/ folder skeleton. Use when starting the build or when CLAUDE.md / _props/ scaffolding is missing.

Build Crave's design-token system in src/theme — colors (light default + dark), typography (Inter / Plus Jakarta Sans), spacing scale (4/8/12/16/20/24/32), radii (sm/md/lg/xl/pill), elevation, plus ThemeProvider, useTheme, and useThemedStyles hooks. Use immediately after crave-scaffold (Phase 0 close-out / Phase 1 prereq). Components MUST read every color, spacing, radius, and font size from here — literal hex/numbers in components are bugs.