How brian-w-m/devverse works
DevVerse combines a coding-activity tracker with a web dashboard and a Pixel Quest RPG experience. The principal documented workflow is VS Code edit tracking and score submission to the Go API, followed by DynamoDB-backed user/activity data displayed in the dashboard; GitHub login supplies identity. The README also describes leaderboard/streak features and the game reward loop. Backend auth and persistence calls are supported by sampled source; route wiring and several frontend/extension internals are not sampled, so uncertain links are omitted.
Main entry points: register.go API Routes · page.tsx Web App · auth.go Auth Route · route.ts OAuth Token Exchange
Components 20
User Clients
- VS Code
- Edit Tracker
extension/src/extension.ts - Web App
frontend/app/page.tsx - Dashboard
frontend/app/dashboard/page.tsx - Pixel Quest
frontend/app/game/page.tsx - Game Prototype
frontend/app/phaser-test/page.tsx
Identity
- OAuth Token Exchange
frontend/app/api/auth/github/token/route.ts
Backend API
- HTTP Server
backend/src/main.go - API Routes
backend/src/routes/register.go - Auth Route
backend/src/routes/auth.go - Auth Service
backend/src/services/auth_service.go - User Service
backend/src/services/user_service.go - Activity Routes
backend/src/routes/jobs.go - Activity Service
backend/src/services/job_service.go - Stats Routes
backend/src/routes/stats.go - Stats Service
backend/src/services/stats_service.go - Session Service
backend/src/services/session_service.go
Activity Data
- DynamoDB
Other components
- Developer
- GitHub
Connections 24
- Developer → VS Code: edits code
- VS Code → Edit Tracker: activates
- Edit Tracker → HTTP Server: submits scores
- Developer → Web App: uses
- Web App → OAuth Token Exchange: exchanges code
- OAuth Token Exchange → GitHub: requests token
- GitHub → OAuth Token Exchange: returns token
- Web App → Dashboard: opens
- Dashboard → Stats Routes: requests stats
- Developer → Pixel Quest: plays
- Pixel Quest → Game Prototype: prototype
- HTTP Server → API Routes: registers
- API Routes → Auth Route: dispatches
- Auth Route → Auth Service: verifies token
- Auth Service → GitHub: verifies identity
- Auth Route → User Service: creates or updates
- API Routes → Activity Routes: dispatches
- Activity Routes → Activity Service: handles activity
- API Routes → Stats Routes: dispatches
- Stats Routes → Stats Service: queries stats
- Stats Service → DynamoDB: reads users
- User Service → DynamoDB: reads and writes
- Activity Service → User Service: updates scores
- Session Service → DynamoDB: records activity