Foundations
The full course, in reading order.
From “what this project actually is” to “how to ship a change without breaking three files”.
- 6–10 lessons
- quiz per lesson
- 20 xp each
The context wall ends here
Geko reads your public repo and teaches it back in plain English — architecture, lessons and debug steps, all from your own files.
public repos only · 3 projects · read-only
$ geko analyze github.com/you/your-app
→ guidebook ready
geko“Your landing page renders from src/app/page.tsx — start there when a change goes wrong.” 🦎
sample output
Pick your depth
Same repo, same voice. Pick the depth you need today.
built from your files only
The full course, in reading order.
From “what this project actually is” to “how to ship a change without breaking three files”.
Describe the bug. Learn the cause.
Geko points at the files that likely cause it, gives concrete fix steps, then teaches the concept underneath.
The map, before the lessons.
Layers, data flow and the concepts that hold it together — in plain English, built from your tree.
The run
Four steps. The first two take about a minute; the analysis runs in the background while you watch.
limits, stated up front
Paste the GitHub URL. We read the tree and skip what teaches you nothing: node_modules, lockfiles, binaries, anything over 300 KB.
Framework, database, auth, hosting — read from your manifests and folders. Deterministic, no LLM involved in this part.
Lost? Start with the map. Staying? Start with lessons. Broken? Start with debug.
Every lesson ends with questions answerable only from your codebase. Pass, and the XP is yours.
Bring a project that has grown past one file. That is where the confusion lives — and where this helps most.