How hb-16-manoel/atlas works
Atlas is a personal planning and reflection app: a user works through a dashboard for tasks, habits, events, journal entries, progress, and settings. The page composes those views and obtains domain state through useAtlasData, which supports browser-local legacy data and authenticated cloud synchronization. Authentication includes account and recovery flows; cloud persistence is backed by Supabase. The README is only the stock Next.js starter and documents no product capabilities. Some component internals and sync wiring are unsampled, so the graph omits uncertain relationships.
Main entry points: page.tsx Atlas app shell · useAtlasData.ts Atlas data hook · AuthShell.tsx Auth flows · client.ts Browser Supabase client
Components 20
Planning experience
- Atlas app shell
app/page.tsx - Home
app/components/Home.tsx - Planning
app/components/Planning.tsx - Journal
app/components/Journal.tsx - Settings
app/components/Settings.tsx
Reflection insights
- Progress
app/components/Progress.tsx - Atlas intelligence
app/lib/atlasIntelligence.ts - Daily score
app/lib/dailyScore.ts
Account access
- Auth provider
app/components/AuthProvider.tsx - Auth flows
app/components/AuthShell.tsx - Auth callback
app/auth/callback/route.ts - Browser Supabase client
app/lib/supabase/client.ts - Server Supabase client
app/lib/supabase/server.ts
Data persistence
- Atlas data hook
app/hooks/useAtlasData.ts - Cloud repository
app/lib/data/cloudAtlasRepository.ts - Legacy browser store
app/lib/data/legacyAtlasRepository.ts - Supabase data
supabase/migrations
Other components
- User
- Supabase Auth
- Google OAuth
Connections 21
- User → Atlas app shell: uses
- Atlas app shell → Home: renders
- Atlas app shell → Planning: renders
- Atlas app shell → Journal: renders
- Atlas app shell → Progress: renders
- Atlas app shell → Settings: renders
- Atlas app shell → Atlas data hook: loads state
- Atlas data hook → Auth provider: reads user
- Atlas data hook → Cloud repository: creates repository
- Atlas data hook → Legacy browser store: reads/writes
- Cloud repository → Supabase data: reads/writes
- Progress → Atlas intelligence: analyzes
- Atlas intelligence → Daily score: calculates
- User → Auth flows: submits credentials
- Auth flows → Browser Supabase client: uses
- Auth provider → Browser Supabase client: uses
- Browser Supabase client → Supabase Auth: auth requests
- Auth flows → Google OAuth: starts sign-in
- Supabase Auth → Auth callback: redirects
- Auth callback → Server Supabase client: exchanges code
- Server Supabase client → Supabase Auth: uses