Closer/PROJECT.md

Relationship App — Couples Connection

Overview

Project: Relationship App (Couples Connection) Created: 2026-05-13 Status: Active (Phase 1 - Foundation & Infrastructure - 1.0.x) Build Phase: 1 (Foundation & Infrastructure)

Description

A mobile app designed to help couples build a deeper emotional connection through meaningful interaction, guided conversations, and personal moments. Built with React Native + Expo for iOS and Android.

Tech Stack

• React Native — mobile framework (cross-platform: iOS + Android)
• Expo — development platform and build tooling
• TypeScript — type safety
• NativeWind — Tailwind CSS for React Native
• Supabase — Auth, Database (PostgreSQL), Realtime, Storage
• Cloudflare R2 — media storage
• Expo Push Notifications — push alerts
• shadcn/ui-style — component primitives adapted for mobile

Directory Structure (Phase 1 target)

• app/ — Expo Router screens and layouts
• components/ — Reusable UI components
• lib/ — Utilities, hooks, Supabase client
• constants/ — Theme, colors, spacing
• assets/ — Images, fonts
• supabase/ — Migrations and config (if using CLI)

Git

• Branch: dev (working), main (stable)
• Remote: ssh://forgejo/null/relationship-app.git

Versioning

Version numbers correlate to the active phase:

• Phase 1: 1.0.x (foundation, bootstrap, auth)
• Phase 2: 1.1.x (core question engine)
• Phase 3: 1.2.x (milestones & memories)
• Phase 4: 1.3.x (messaging & notifications)
• Phase 5: 1.4.x (polish & launch prep)

Phase Completion Git Rule

Push to dev after every completed and verified batch.

• Agents do not touch git.
• Bishop verifies and updates docs.
• Ripley performs final checks, commits, and pushes to dev.

Conventions

• Follow AGENTS.md for agent dispatch protocol
• All agents read project-requirements.md before starting tasks
• Ripley owns git — no agent touches git directly
• See BATCH_SIZING.md for batch sizing rules (one focused task per batch)
• NOT Next.js. NOT a web app. This is React Native + Expo.