Studigo

Studigo is an AI study companion that turns a student's own class materials into a grounded, course-specific tutor.

Students create a Study Room, upload teacher study guides, textbook chapters, notes, worksheets, and presentations, then use one workspace to learn, ask questions, quiz themselves, generate flashcards, track mastery, and keep the work as a downloadable study guide.

Give Studigo what you are supposed to learn and the resources you are supposed to learn it from. Studigo turns them into a study companion.

Play the math game (beta)

▶ Play Moon Keep. It's a multiplication Metroidvania prototype and the current golden build.

• The previous golden builds are Moon Keep (POC X) and Moon Keep (POC IX).
• It plays in the browser with a keyboard or touch, and ↺ in the header restarts a run.
• It's a standalone prototype served from GitHub Pages, not part of the Studigo app.
• The source, rules and tests are in prototypes/moon-road/. Start with POC-XI.md.
• Run and test it: python -m http.server 8123 from prototypes/moon-road/dist (open /poc-xi/), and node --test "prototypes/moon-road/test/**/*.test.mjs" from the repo root.
• Making art or levels for the game? The local tools (Pixelorama, LDtk, TexturePacker, Blender, Godot) and the pipeline are in TOOLCHAIN.md. Tool binaries stay on your machine and are never committed.

Engineering start here

For engineers, reviewers, and coding agents, start with ENGINEERING.md. It explains the AI/software authority boundary, why the main technologies were selected, the end-to-end data path, where each responsibility lives in the codebase, and which deeper contract to open next.

The canonical execution plan is implementation/ENGINEERING_PLAN.md. Security readiness and public-launch blockers are maintained under implementation/security-readiness/.

Status

The core student loop — sign up → create a Study Room → upload materials → ingest → ask → cited answer — is implemented and working end to end, along with Learn, Quiz, Flashcards, and mastery derived from real practice.

• Frontend: Next.js + React, responsive PWA shell.
• Backend: Next.js route handlers + Supabase Auth/Postgres/Storage.
• Authentication: Supabase Auth with Google, Apple, and Microsoft social OAuth as the launch providers, plus email fallback. Facebook is a later optional provider.
• AI layer: provider-isolated OpenAI Responses + embeddings package.
• RAG: Supabase Postgres + pgvector with room-scoped similarity search.
• Documents: private uploads, metadata, processing states, and signed downloads.
• Executable layer: installable PWA now; Tauri desktop shell is reserved separately, and the chosen App Store route is an Expo/React Native iOS client over the existing hosted backend.
• Engineering handoff: ENGINEERING.md is the compact start-here map; deeper product/architecture contracts live in docs/, and the canonical engineering execution plan lives in implementation/ENGINEERING_PLAN.md.

What works today:

This is the beginning of the README. Read the rest at the original. Read the full README ↗