I Built a Documentation Tool in 48 Hours (While Running a Code Jam) Most founders would tell you: "Focus on one thing. Ship it. Polish it. Then move to the next." I'm 12. I don't have the luxury of that advice. Yesterday, I launched KODA v16 — an AI coding mentor running on a 480B parameter model, with a 4-layer fallback chain and production-grade error logging. Today, I'm announcing Scribe — a standalone tool that turns AI conversations into permanent, searchable engineering documentation. Both are live. Both are free. And I built them on a 6.7-inch phone in Tamil Nadu. Here is how I did it, why I did it, and what it means for the future of under-resourced builders. The Problem: AI Conversations Are Ephemeral You ask an AI to explain Python decorators. It gives you a brilliant answer. You copy the code. You close the tab. Three days later, you forget how it works. This happens to everyone. But it hits beginners harder. They don't have notebooks, they don't have Notion workspaces, they don't have a system. They just have a chat history that disappears into the void. My mentor Nyaomaru asked me: "What separates a world-class engineer from someone who just uses AI?" My answer: Documentation. World-class engineers don't just code. They preserve their learning. They build handbooks. They create systems that outlive their memory. So I built Scribe. The Solution: Turn Chats Into Handbooks Scribe (https://scribekit.netlify.app) is a dead-simple tool: Paste any AI conversation (from KODA, ChatGPT, Claude, Gemini — doesn't matter) Auto-format into clean Markdown Add tags (python, debugging, api, etc.) Download as .md file or copy to clipboard (Optional) Save to your personal library with Supabase auth That's it. No fluff. No AI generation. Just preservation. The Tech Stack (Zero-Build, Phone-Friendly) Component Choice Why Frontend Vanilla HTML/CSS/JS (single file) I edit this on Trebedit on my phone. No React, no build step. Auth Supabase (email/password, no verification) Frictionless MVP. Users signup → instant access. Database Supabase Postgres + RLS Row-level security ensures users only see their own docs. Hosting Netlify (free tier) Instant deploys, global CDN, zero config. Styling Custom CSS (dark mode, Inter font) Professional look, mobile-first responsive. Total lines of code: ~400 Total build time: 48 hours (while managing the KODA Code Jam) Total cost: $0 The Architecture: Security Without Complexity Here is the Supabase schema that keeps user data private: CREATE TABLE scribe_logs ( id UUID DEFAULT gen_random_uuid() PRIMARY KEY, user_id UUID REFERENCES auth.users(id) ON DELETE CASCADE, title TEXT NOT NULL, content TEXT NOT NULL, source_ai TEXT, tags TEXT[], word_count INTEGER, created_at TIMESTAMPTZ DEFAULT NOW() ); -- Row Level Security (RLS) ALTER TABLE scribe_logs ENABLE ROW LEVEL SECURITY; -- Users can ONLY see their own logs CREATE POLICY user_own_logs ON scribe_logs FOR SELECT USING (auth.uid() = user_id); Why this matters: Beginners trust you with their learning. If they save a Python tutorial they struggled through, that data is sacred. RLS ensures no SQL query can ever leak another user's docs. I learned this from Nyaomaru's advice: "Production-ready means reliability, security, and failure handling." The Philosophy: Builders Are Built by Building (and Documenting) KODA's philosophy is: "Mistakes are the lesson." Scribe's philosophy is: "Documentation is the legacy." You can't have one without the other. You break code → you learn → you document → you never forget. This is how you go from "I have a cheap phone" to "I am a world-class engineer." World-class engineers: ✅ Write code ✅ Break things ✅ Document the lessons ✅ Share the knowledge Scribe handles step 3. KODA handles steps 1-2. Together, they form a complete learning loop. The Timing: Why I Built This During a Code Jam You might think: "Bro, you have a Code Jam running. Why distract yourself?" Here is the truth: Scribe is not a distraction. It is infrastructure. The KODA Code Jam closes on Sept 14, 23:59 IST. Winners will be crowned on Sept 15. But what happens after? Participants will have built niche apps. They will have learned Python, JavaScript, API integration. They will have conversations with KODA that taught them critical skills. Without Scribe, those lessons vanish. With Scribe, those lessons become permanent. I built Scribe during the Fest so it would be ready after the Fest. When participants look back at their journey, they can export it, tag it, and keep it forever. That is not a distraction. That is completion. The Roadmap: What Comes Next Scribe is live. But it is v1. Here is what ships in v2 (post-Fest): Feature Priority Why KODA Integration P0 One-click "Export to Scribe" button inside KODA chat Vector Icons (SVG) P1 Replace emojis with professional scalable icons Full-Screen Editor P1 Better mobile UX for long documents Auto-Tagging P2 AI suggests tags based on conversation content Notion/GitHub Export P2 Power users want their docs in their workflow Public Shareable Docs P3 Let builders showcase their learning publicly All of this will be built on the same zero-budget, phone-first stack. Because if I can do it on a POCO C55 in Tamil Nadu, you can do it anywhere. Try It Now Scribe is live: https://scribekit.netlify.app Create a free account (no email verification, instant access) Paste any AI conversation Tag it, format it, download it Build your engineering handbook It is free. It is open. It is yours. The Bigger Picture I am 12. I have 3,000 followers on Dev.to. I run an AI coding mentor with a 480B parameter model. I just shipped a documentation tool in 48 hours. But none of that is the point. The point is this: If I can build this on a cheap phone in a small town in India, what can you build? You have a laptop. You have internet. You have more resources than I do. What is your excuse? Build. Document. Ship. Repeat. The empire is not built in a day. It is built one line of code, one documented lesson, one shipped product at a time. Silent tigers hunt in sequence. But they never stop hunting. 🐯 KODA (AI Mentor): https://koda-aicodementortemp.netlify.app Scribe (Documentation): https://scribekit.netlify.app Code Jam (Closes Sept 14): Submit your niche app in the KODA drawer Let's build.