halobestie-clone/requirement/.claude/memory/context.md at master

Files

ramadhan sjamsani a7a2a32d27 Phase 1 scaffold: auth for all apps

- Backend: Fastify with two listeners (public + internal), routes, services, DB migration + seed
- client_app: Flutter with BLoC, all auth screens (welcome, display name, register, OTP, force-register)
- mitra_app: Flutter with BLoC, OTP-only login
- control_center: React + Vite, email/password login, mitra/user management, anonymity settings
- Docs: phase1 plan, API contract, client app mockup
- CLAUDE.md and shared memory for all subprojects

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-05 10:08:42 +08:00

522 B

Raw Permalink Blame History

name, description, type

name	description	type
Requirement Context	Conventions and scope for Halo Bestie requirement documents	project

Phased requirement documents for all apps.

Naming convention: phase<N>-<domain>.md (e.g. phase1-auth.md, phase1-payment.md)

Each doc must state: which app(s) it affects (client_app, mitra_app, control_center, backend) and any backend route implications.

Known deferred: Real-time chat and live features are out of scope for initial phases — planned for a future phase.

522 B Raw Permalink Blame History

522 B

Raw Permalink Blame History