Introducing "codebase to course", a skill that turns any codebase into an interactive coding course So that you can learn coding through your own projects, complete with visualization, plain-English code translations, metaphors, even quizzes... I vibe code a lot but have no idea how the code works under the... hood. This is how I think "learning to code" should be in the AI age: Build first, learn later Link belowshow more

Skill:

Cool. Agree that among with Vibe coding, Vibe learning should go hand in hand. I built this to help along the way as you cover with Claude code.

this is actually genius. Most people learn to code backwards, they study theory for months then try to build something. This flips it. Build first then understand what u built. Its like learning to drive by actually driving not by reading the car manual for 6 months

this is way closer to how people actually learn now. build first, then inspect the weird part you just shipped while the pain is still fresh.

"Build first, learn later" is the most underrated principle in AI right now. Everyone thinks you need to understand AI before you use it. You don't. You need to use it, get results, then understand why it worked. Same way nobody learned to drive by studying an engine. You got in the car and figured it out. This is how every business owner should approach AI. Start. Then learn.

Love it. My take on this is to convert a codebase into an interactive explainer. Do checkout at -

this is what i actually want when i inherit a codebase. not docs. a guided tour that explains the why behind the structure

This is my project that has similar intent that helps non-tech vibe coder better understand codebase and progress.

hey zara! would love to get your thoughts on this its more codex focussed, but its about getting to that level of leveraging ai tools to be the best study companion that you can have

the visualization angle is interesting. the hardest part of learning a codebase isn't the code itself but the reasoning behind the architecture. does it surface the "why" behind patterns or mostly the "what"?

woww i have been thinking of something like this for a long time. but you have brought it into the world much better than i was thinking! great work 👏🏽

Love all skills you are sharing!!! And "follow builders, not influencer" you have said impress me a lot. Users who built first retained 3x longer than those in "learn first" tutorials. Momentum beats theory!! Build first, Build in AI, learn later.

@DamiDina this is going to be awesome for beginners that wanna dive in deeper with tech. awesome work!!

love the visualizations, built something similar a few days back. it gives you a detailed read into the tech stack, architecture, design tradeoffs, and explains the code with code snippets. the quiz also has a surprise at the end lol.

Build first, learn later is the most natural way humans have ever learned anything. We just forgot because school taught us the opposite for 20 years. Kids don't study grammar before speaking. They speak, then understand why. This is that, but for code.

I was thinking of creating something similar because I am also vibe building while learning on the go. I have usually added in Agents rule to walk me through after each session in a structured manner. I’ll try this skill to see how it goes. Thanks

learning from code you vibe coded is actually smarter than generic tutorials because you already know what it's supposed to do. you just don't know how

Love it! So good! Need this right now!!

This idea is quite similar to @WonderingApp.

Yesterday I just used frontend-slides to study my code.

Build first, learn later is probably right. I’ve learned way more once the code had stakes and context.

@tangjinzhou fork

Nice one @zarazhangrui! This is what I think future of education looks like

"Build first, learn later" is such a great philosophy for the AI era. Using a Claude Code skill to reverse-engineer your own vibe-coded projects into a custom curriculum is brilliant. It perfectly bridges the gap between just generating code and actually understanding what you built.

A paradigm shift for learning to code.

This is also how senior engineers actually work, they read source code, not tutorials. The risk with build-first is encoding bad patterns early. Your skill sidesteps that by making the code explain itself. That's the real unlock.

Zara cooking! Love these skills!

honestly the hardest part of learning from a codebase is knowing where to even start. this makes that a lot less painful

This is really a good share.

build first learn later is how every kid learns to walk. we just forgot that approach somewhere around college textbooks

This would be a boon for non-tech users, who fear when handed over with a Github codebase link.

"Build first, learn later" is the thesis most people still aren't ready to hear. We've seen non-technical founders ship production features in week one, then retroactively understand what they built. The codebase IS the curriculum now.

This skill has a huge potential, i don’t need to code everything but i need to be able to read and understand it.

Such a great skill Zara. I will try it on some codebase.

very cool, love this!