Hackathon toolkit: build and win in the AI age (Sibu 2026)
November 6, 2026
#notes
Hackathon toolkit: build and win in the AI age (Sibu 2026) Everything from my talk at My Kampung, My Pride · Sibu 2026, in one page. Bookmark it. The slides are at mfrashad.com/speaking-slides/hackathon-ai-age.html.
- Free AI tools (claim these today) Tool What you get Link Google AI Studio Describe your app in plain words → it builds a working app (Build mode). Free. aistudio.google.com Google AI Plus (students) 12 months free for college/uni students aged 18+. Claim by 31 Dec 2026. Needs a payment method and renews at RM23.99/month, so cancel before it renews. gemini.google/my/students GitHub Student Developer Pack Copilot Student (free), GitHub Pro, a free .me domain and more. Needs a school email or proof of enrolment. education.github.com/pack Kiro AI coding app from AWS with a free tier. (The community credit code is fully claimed.) I haven't tested this free tier myself. kiro.dev Freebuff A free coding agent in your browser, desktop or terminal. I haven't tested it myself. freebuff.com OpenCode Free, open-source coding agent that comes with free models. opencode.ai OpenRouter Free ":free" model versions (50 requests/day without credits). openrouter.ai/models?max_price=0 Lovable Great for a first draft, but the free plan is 5 credits/day. Students get 50% off Pro. lovable.dev/students
- The free stack Build: Google AI Studio, Kiro, GitHub Copilot, OpenCode Data + login: Supabase · Convex if you need realtime (live updates, chat, multiplayer) Deploy: Vercel (free, gives you a live link) Pitch deck: Canva Stick to tools you already know. Familiarity = speed.
- From idea to live link (no-code path) Open AI Studio → Build. Describe who it's for, the one thing it does, and how it should look. Iterate one change per message. Paste a screenshot when something looks wrong. Export the code (Download, or Save to GitHub). On Vercel: Add New → Project → import the repo → Deploy. You get a live link. If your app uses Gemini, add your API key in Vercel as an environment variable. Never paste it into the code. Put the link and a QR code on your pitch slide. Test it on a phone before you pitch. Skip the login page. Hardcode the user. Judges don't need to sign up to see your demo.
- Make it not look AI-made 21st.dev: 12,000+ components and templates by real design engineers. Hit "Copy prompt" and paste it into your AI tool. binmob: 1,191 real website designs to borrow layout, type and colour from. Give the AI a screenshot of a site you like and say "make it look like this". One font, one accent colour, real photos. No emoji bullets, no purple gradients.
- Demo video Screen-record your app (Windows: Win+G, Mac: Cmd+Shift+5, or your phone's screen recorder). Always have a backup recording. If the live demo breaks, play the video and talk over it. Inspiration for launch videos made with AI prompts: launchvideos.gallery Upload to YouTube (unlisted is fine) and put the link in your README and Devpost.
- Your pitch: 5 min + 2 min demo + 3 min Q&A Time What Rubric it hits 0:00–0:30 Hook. A person, a story, a prop. Make us feel it. Presentation (15) 0:30–1:30 Problem. Who, where in Sibu, how you know (you talked to them). Problem & relevance (20) 1:30–3:30 Solution + demo. The 1–3 features, working. Prototype (25) + Innovation (20) 3:30–4:30 Feasibility & impact. Who uses it, who pays, what it costs to run, next step. Feasibility & impact (20) 4:30–5:00 Close. One line they'll remember. Presentation (15) 1–2 sentences per slide. If you're reading your slide out loud, the judges have stopped listening. Prepare answers for: Who pays? Will people actually use it? What if the AI is wrong? What's next? Study winning projects on Devpost to see what good looks like.
- Know your judges Read the jury slide and look your judges up. Same rubric, different lens: Technical background: does it actually work? Is it feasible? Is the AI doing something real? Entrepreneur / industry: who pays, will people actually use it, what does it cost? Academic: is there evidence for the problem? How would you measure impact? Talk to the mentors early, while you can still change things.
- Split the work (your team is set, now divide it) Builder(s): the core feature working end to end. Designer: UI polish, slides, thumbnail. Pitcher: talks to real people about the problem, writes the story and deck, rehearses, preps Q&A. Suggested timeline: idea locked and checked with a mentor by lunch → core feature working by 5 PM → tonight: polish, design, demo video, deck → tomorrow 8:30: final fixes, rehearse 3 times, submit by 9:30 AM.
- After the hackathon (don't let it die on Sunday) GitHub repo with a proper README: one-line problem, screenshot or GIF at the top, demo video link, how it works, how to run it, the team A thumbnail (1280×720) Demo video on YouTube Slides as a PDF in the repo, on Devpost, or in your LinkedIn Featured section A LinkedIn post (template below) While you're there: finish your LinkedIn profile (photo, headline, about, projects, featured) LinkedIn post template This weekend at the My Kampung, My Pride Sibu hackathon, our team built [name]: [one line on what it does]. The problem: [one sentence, with a real person or number]. What we built: [1–3 features]. Try it: [link] What I learned: [one honest lesson]. Thanks to [mentors, organisers] and my teammates [tag them].
- Examples from the talk Semak Dulu, a job scam simulator with an AI recruiter on WhatsApp (UNODC × Project Liber8). Can you spot the scam before you send your passport? Try it Idea for your theme: the same WhatsApp chatbot idea, applied to tourism. A homestay host sends one voice note, and gets back a page tourists can book in English and BM. Jalan-jalan Sibu: a playable digital museum of Sibu: walk to 9 landmarks and collect every stamp. Play it
- Keep going Hong Bing's hackathon field manual (he has placed in 20 hackathons): hong.build/hack My hackathon guide: instagram.com/p/DeSk0ejkq_X Upcoming hackathons: mfrashad.com/resources/hackathon-resources Say hi: IG @rashadventure · LinkedIn in/mfathyrashad · mfrashad.com This page is a Cleve note. Cleve is the AI workspace for writing and thinking that I build: write notes, publish them as pages like this one. cleve.ai