DEV Community: Muhammad Murtuza Hussain

Job hunting became my side hustle, so I built Deis (Gemma 4) Tinder for jobs: swipe right, Gemma tailors your CV

Muhammad Murtuza Hussain — Sun, 18 Oct 2026 20:56:01 +0000

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle

My contract ended on Wednesday. By then I had tailored 83 CVs by hand this autumn: one per job, each one rewritten to the job ad's own words, each one checked so it didn't claim anything I couldn't defend in an interview. Most early-career people I know are doing the same thing, alone, at night.

There are AI tools for this. The best known charge per application: reviews put AI Apply's auto-apply credits at about 32 cents to a dollar each, on top of a monthly plan. When you're applying to 500 jobs, that's a few hundred euro you don't have, spent on applications that a model wrote and you never read.

So I built Deis. It's Irish for opportunity, and it's said "desh".

TL;DR. Deis is a swipe-to-apply job app for early-career people in Ireland. It shows you jobs filtered for your level, your languages and your right to work. Swipe right and open-weight Gemma 4 writes a CV, a cover letter and form answers tailored to the job. Every line on that CV points to a fact you confirmed, and code removes anything Gemma can't back up. It runs on your own model: on your laptop through Ollama (with the Wi-Fi off, if you like), on your free Google AI Studio key, or on a server you rent. An application costs about €0. The app is €9.99 once, and the code is open source.

What I Built

A 90-second check-in. Where in Ireland you'd work, how far along you are, whether you can work here now (EU, Stamp 4, Stamp 1G or needing a permit), the kinds of work you want, and any languages besides English.
A profile of small, true facts. Upload your CV and Gemma splits it into facts you tick off one by one. LinkedIn won't let apps read your profile, but it will give you your own data: Deis turns LinkedIn's data export into facts without any AI at all.
A deck of real Irish jobs. About 300 live early-career jobs at a time, 70 to 100 in a typical deck once your filters run. Deis reads 55 employers' public job boards and shared Google Jobs searches. Then code, not the model, hides what you can't or won't take: roles asking for 3+ years, roles that need German or Turkish, postings that rule out your visa. Every card quotes the posting's own words: "asks for 2+ years of B2B sales experience", "unable to offer visa sponsorship".
Swipe right, two ways. Quick builds the kit (fit check, CV, letter, draft answers) in the background while you keep swiping. Careful shows you the fit first and asks about your gaps: "The role asks for SQL. Where have you used it?" Your answer becomes a proposed fact, you approve it, and every application after that is stronger.
Paste a job you found elsewhere. It goes through the same code as the boards and lands on top of the deck, offline too.
You apply. Download the CV as Word or PDF, copy the answers, open the posting. Deis never applies for you. Auto-apply tools hit account walls and CAPTCHAs, break LinkedIn's terms, and send the same weak application to 500 places. In a hiring market as small as Ireland's, that follows you around.

Why not just paste it into ChatGPT? You can, and for one application it's fine. For forty it isn't. You paste your CV again every time, the chat forgets which facts you confirmed, and nothing stops it writing "3 years of experience" or "no sponsorship needed" in a confident voice you'll sign. It doesn't know which Irish jobs you can't get, so you find out after the letter is written. Deis keeps your facts in one place, hides those jobs before you see them, checks every line against what you said, and shows you what it removed. And it runs on a model you can keep on your own laptop, so your CV isn't training anybody's next model.

Who pays? Graduates and early-career people in Ireland who are applying to dozens of jobs, and especially international master's graduates on Stamp 1G. Many postings quietly rule them out, and finding that out after writing a cover letter hurts. €9.99 once is less than one month of the subscription tools, and about the price of a takeaway. The first person to really use it paid for it on the call, and the second sale came from someone I've never met. Both stories are below.

Demo

Try it: deiscareers.tech. Choose Try as Aoife or Try as Rahul: two fictional graduates, applying for real Irish jobs. The web demo takes no real CV. Your own CV is read in the desktop app, on your computer, so the hosted demo never receives it.

Desktop app: macOS, Windows and Linux installers, with a 14-day free trial, then €9.99 once. Buy a key here. Until the end of October, the code hacktoberfest2026 takes 80% off and is applied for you at checkout, so it's €2. The app isn't signed by Apple yet, so macOS asks you to open it once from Privacy & Security. The download page shows the steps. On a phone, the free Android app and iPhone home screen app run the same demo as the website. Questions, or a key that won't work? Email hello@deiscareers.tech.

Code

MuhammadMurtuzaHussain / deis

Swipe-to-apply job app for early-career people in Ireland. Open-weight Gemma tailors your CV and cover letter to each job, and every line traces back to something you told it.

Jobs you can actually get. A swipe-to-apply job app for early-career people in Ireland, where open-weight Gemma 4 tailors your CV and code removes anything it can't back up

Try the web demo · Watch the film (1 min) · DEV post · Download · hello@deiscareers.tech · Built for the DEV Hacktoberfest Open-Source AI Challenge, Week 2: Side Hustle

Deis (said "desh") is Irish for opportunity.

Why

I tailored 83 CVs by hand this autumn: one per job, each rewritten to the job ad's own words and checked so it didn't claim anything I couldn't defend in an interview. Most early-career people I know do the same thing, alone, at night. The AI tools that do it for you charge per application and write things you'd never sign: "3 years of experience", "no sponsorship needed".

Deis keeps your facts in one place, hides the Irish jobs you can't get before…

View on GitHub

How I Built It

Gemma judges, code guarantees

A tailored CV that invents a certificate, or a total years of experience, can cost someone the job. So Gemma decides what to say, and code decides what stays.

Every CV line has to cite the facts it came from. Code drops lines with no real facts behind them, and checks each sentence: any number, tool or certificate it mentions has to be in the cited facts.
Code never lets a model state a total years of experience, write "currently studying" about a finished degree, or say anything about visas, stamps or sponsorship. That last rule came from testing: Gemma 4 26B wrote that my Stamp 1G persona was "eligible to work in Ireland without sponsorship".
Employers, job titles, dates and education are copied from your facts, never rewritten.
Job postings are data, not instructions. Hidden text and sentences addressed to AI tools are stripped before Gemma reads a posting and shown to you on the card. Real postings already contain them.
Everything the guard removed is on the kit's Checks tab, and one switch shows the source facts under every CV line.

I measured it. On eight kits written by Gemma 4 E4B on my MacBook (fit check, CV, letter and answers):

Run	Sentences kept	Removed by the guard
First run (13 Oct)	210	56
After fixing what the first run showed (13 Oct)	261	11 (4%)
Current guard, CV, letter and answers all checked (16 Oct)	196	11 (5.3%)

I read every removal of the last run by hand. About half were real: a test persona's finished MSc written as "current", a company's own pitch copied into a letter, an empty heading. The other half were true lines the guard was too strict about. I'd rather it erred that way. A full kit takes about 46 seconds on the laptop (median of 8).

The first run taught me something about small models: Gemma never invented a fact id. Instead it cited facts by quoting them or by their label, and my guard threw those good lines away. Now quotes and labels are matched back to the facts they name. What's left for the guard to remove are real over-claims: tools I never used, "currently" studying a degree I'd finished, a number from nowhere.

The deck is code, not AI

I hand-labelled 81 real Irish postings as show, stretch or hide and tuned the filter on them (86% before, 100% after). Then I labelled 52 postings it had never seen, without looking at what it decided: 51 of 52 right on the first run. The one miss hid a Trainee Accountant job because "complete the ACA qualification over a period of 3 to 4 years" looked like an experience requirement. A graduate or trainee title now needs a line that really says "experience" before Deis hides it. The details are in eval/RESULTS.md.

Gemma never reads a job you won't see, which is what keeps it cheap.

Your model

Every AI call goes through a per-request chain of models built with Mastra: one agent per job (card, fit, CV, letter, answers, coach), and the kit is a Mastra workflow that writes the CV, letter and answers in parallel. The chain is whatever the user chose (Ollama, an AI Studio key, any OpenAI-compatible server), with fallbacks.

That turned out to matter on day two. Google AI Studio's Gemma 4 returned errors for hours, and some requests hung for over 90 seconds. The hosted demo now gives cloud calls a deadline and probes AI Studio, and while it's failing it asks a second Gemma host first: Gemma 4 26B on OpenRouter.

It also matters when there's no network. With Gemma on your laptop, File > Work offline turns on an egress guard that refuses every connection that isn't to your own computer. The deck shows the jobs it saved, you can paste a job, and the kit still builds. I tried it with the Wi-Fi off: a pasted job still built a full kit on Gemma on the laptop. The guard has its own tests in tests/offline.test.ts.

The bug I shipped and fixed

The hosted demo counted all of a person's AI calls against one limit. Browsing cards used it up, so after about 20 calls in an hour your next kit was told to come back later. Worse, the counter trusted the first address in a header the client controls, so changing that header reset it. Now each step has its own allowance per person, a person has a total across all steps, and the whole demo has an hourly budget. The address comes from Cloudflare's own header and is validated before it's counted.

The rest

Jobs: SerpApi Google Jobs, one shared search per role family for all of Ireland, refreshed about once a week, so one search serves every user. (The Google Jobs engine rejects gl=ie; the location alone works.) Plus 55 employers' public boards on Greenhouse, Ashby, Lever and SmartRecruiters, refreshed every six hours.
Desktop: Electron around the same Next.js server, running on 127.0.0.1 behind a host check, at a stable deis://app origin so your profile survives restarts. Installers for all three systems come from GitHub Actions.
Tracing: Sentry agent tracing: a span per workflow step and per Gemma call with tokens, and an issue for every guard rule that fires, tagged with the model. Never a CV, a prompt or a key.
Hosting: Render web service and Key Value in Frankfurt for the demo, the shared job feed and the demo key's rate limits.
Design: Bricolage Grotesque for the big type, Geist for everything else, light and dark. Swipe, buttons or arrow keys. One accent, a lime highlighter, which only ever means go or proven: select a fact and it draws behind every CV line that cites it, and when a kit finishes the CV writes itself line by line while the sentences the guard removed flash past struck through. All of it stops under reduced motion.

Why Does Open Innovation Matter?

Because the business only works if the model is free to run. Here is one application, measured:

	Per application	500 applications
Pay-per-application auto-apply (AI Apply credit packs, 2026 reviews)	about $0.32 to $1.00, plus a monthly plan	about $160 to $500
Deis with Gemma 4 E4B on your laptop	€0 (about 46 seconds)	€0
Deis with your free Google AI Studio key	€0	€0
Deis on a paid Gemma 4 host (reseller price)	about $0.0013	about $0.65

With a closed API, I'd either have to charge a subscription to cover tokens or ration your applications. With open weights I can sell the app once and get out of the way.

And the €9.99 has to pay for something. The hosted demo and the shared job feed run on Render: a Starter web service ($7 a month) and Key Value ($10 a month). That's about two sales a month to break even. The tokens cost nothing extra because each person brings their own model.

Because a CV is private. On the desktop app your profile, your applications and, with Ollama, the model all stay on your computer. There's no Deis account and no server copy of your CV.

Because nobody can take it away. When AI Studio went down, Deis switched host. If I disappear, the code is AGPL: build it yourself, free, forever. The €9.99 pays for the signed app, updates and the daily Irish job feed, not for permission.

Where a closed model would be better: the writing. A frontier model would write livelier CVs and need fewer rewrites. It would still need the same guard, because the guard is what stops a confident model from inventing a sponsorship claim. Open weights cost you a 6.6 GB download and a laptop that can run it. I think that's a fair trade for something that handles your CV, but you should weigh it yourself.

My First User

I shared Deis while it was still a prototype: on LinkedIn, on Instagram, in my class's WhatsApp groups and in a group of builders who ship things. Eight people were on a waitlist by the time it was polished, and when deiscareers.tech went live this week I sent it to all of them, with a few reels and posts.

Plenty of people replied. Almost nobody downloaded it. I had pictured them running Gemma on their own laptops; instead everyone tried the web demo on the shared AI Studio key, it hit its rate limit, and Sentry showed me exactly where. So I changed the shape of the product: the web is now a demo with two sample graduates, and your own CV only goes into the desktop app, which has a 14-day free trial.

My Agent Session & How I Built It With Claude Code

I built Deis in a week, from 13 to 18 October, across 18 sessions with Claude Code. I made the decisions: the idea, what to cut, what my first user needed, when the UI wasn't good enough. Claude Code wrote most of the code, ran the tests and evals, and checked its own work against the live demo.

The session below is the short version: 24 messages, one per turning point, in my words and its answers. A few moments worth looking for:

The first message is my unedited brain dump: "something like AI Apply, in a Tinder format where you swipe". The core rule, Gemma judges, code guarantees, came out of the first day.
AI Studio going down on day two, and how the demo got deadlines, a health probe and a second Gemma host.
"I hate the UI and UX", and the Highlighter design that came out of it.
My first user's feedback turning into code the same day: career stages up to 7+ years, tax and accounting roles, and job postings that keep their bullet points.
A re-review that caught three bugs before users did, including a checkout link that sent buyers to the server's internal address.

By the end of the week: 89 commits, 364 tests, installers for three systems, and two sales.

Building Deis with Claude Code: a week from a Tinder-for-jobs brain dump to two paid sales

You

Look into the Week 2 challenge brief, then get back to me when you've understood what needs to be done. I have an idea similar to AI Apply but in an open-source way: an agentic workflow, free of cost, cost-efficient as much as we can. Here's my unedited brain dump: something like AI Apply, in a Tinder format where you swipe.

Agent

Day 1 (13 Oct): the core idea became 'Gemma judges, code guarantees'. Code decides which Irish jobs you see (seniority, right to work, languages). Gemma writes the CV, and a guard drops any line that doesn't cite a confirmed fact.

▸ git commit Start Deis: job filters, fact ledger and CV guard

Input

Start Deis: job filters, fact ledger and CV guard

Output

First commit; then 'Right to work is code's job; guard tolerates real model output' and a guard eval runner

You

DigitalOcean is taking time to sort a payment issue, so let's keep moving with Google AI Studio meanwhile. Sentry DSN made with a new project.

Agent

AI Studio's Gemma 4 returned 500s for hours and some calls hung past 90 seconds. So every cloud call got a deadline, the demo got a health probe, and a second Gemma host became the fallback. Sentry got one issue per guard rule, by name only: never a CV, a prompt or a key.

You

Keys are in on Render, test the live demo. And prep it for OpenRouter: the CV output does not give a good CV and no career objective.

Agent

Gemma 4 26B on OpenRouter is now the demo's second host. The CV follows the layout of the author's own hand-tailored CVs: a professional summary ending in a career objective, labelled competencies, and 3 to 5 bullets per main job.

You

Let's finalise the infrastructure and output quality, and make a fully offline running mode for the app. Also audit the app and tell me how we're doing.

Agent

Ran a seven-part audit (infrastructure, output quality, offline, UI, security, code health, launch). Fixed the top of it: per-route and demo-wide rate limits keyed on Cloudflare's header, a feed that never wipes the deck on a failed refresh, and an offline mode with an egress guard on every socket plus paste-a-job.

▸ Bash pnpm test && pnpm lint && tsc

Input

$ pnpm test && pnpm lint && tsc

Output

75 tests at the audit; tests, lint and types now run in CI on every push

You

I hate the UI and UX. We don't just need a modern UI with colours and fonts, we need an actual overhaul with magic: more dynamic, more animations, it should feel crazy premium.

Agent

The 'Highlighter' design: one lime accent that only means go or proven. A physical swipe deck with fly-to-tab, and a kit that writes itself line by line while removed sentences flash past struck through. Select a fact and the highlighter draws to every CV line that cites it. All of it stops under reduced motion.

You

How will people download it? We also need an update mechanism, and people should be able to set their own SerpApi key, because mine will run out soon.

Agent

Desktop installers for macOS, Windows and Linux built and smoke-tested in GitHub Actions, published on each v* tag. deiscareers.tech is the home. Windows and Linux update themselves; the Mac points to the download page. SerpApi can use your own key.

▸ git tag v0.1.1 ... v0.1.5

Input

v0.1.1 ... v0.1.5

Output

Five releases on 16 Oct, including the Android APK and 'Gemma on your computer in one click'

You

I just connected Entire to the CLI. And for Sentry: are we using it well? It has logged 12 issues but I can't recall the last time one was picked up. How are we using Mastra?

Agent

Sentry now separates the demo, desktop and development environments, with the task in guard issue titles and alerts for model errors. Mastra traces go to Mastra Platform with prompts and outputs stripped, and pure-code scorers grade every hosted kit.

You

Make it clear in the app that they should use local models for the best results, maybe a one-click installation.

Agent

The desktop app links Ollama's installer for your OS, checks every 4 seconds until it's running, then downloads Gemma in one click with live progress. The web demo says so on the hero and in its rate-limit messages.

You

We need a feature for people with 5 to 7 years of experience, and more career fields: it's all tech right now. Add tax, accounting, management, with a search. Address everything from studying to 7+ years.

Agent

This came from the first real user: an MBA student with ten years in tax. The check-in now goes from studying to 7+ years, with 25 kinds of work and a search.

▸ git commit Stages from studying to 7 or more years; Kinds of work: tax, accounting, mana...

Input

Stages from studying to 7 or more years; Kinds of work: tax, accounting, management and more, with search

Output

17 Oct

You

Where are we standing, what's left, how do we bring it to a close? Maybe we don't allow people to put their profile in on the web demo, only in the app. Let's focus on quality.

Agent

The web demo now runs two fictional graduates only, and the server refuses a real CV, so no CV reaches the hosted model. A re-review caught three bugs before users did: a checkout redirect to the proxy's internal address, a page that broke the build, and wrong copy for returning visitors. CI's checksPass meant the broken build never deployed.

You

My first user said when they expand a job description, the bullet points from the actual JD became paragraphs. Not easy to read.

Agent

Google Jobs postings (44% of the deck) arrive with list items as bare lines. A new parser rebuilds headings, paragraphs and lists, and rejoins sentences split around bold words. Measured on all 340 live postings: Google Jobs postings with real lists went from 4 of 151 to 123.

You

Just got a new purchase from someone I have no idea who it is. I think the product is finding its market through word of mouth! Also add the support email [REDACTED] to the website.

Agent

Two sales on Polar: the first user bought it on the call, and the second came from a stranger. The October code is applied at checkout, and the support inbox is on the site and in the desktop licence screen. 89 commits and 364 tests by the end of the week.

My first real user wasn't who I built it for. I expected a recent tech graduate. A friend forwarded Deis to her MBA class, and the person who got on a call with me was one of her classmates: an international student with ten years of experience, looking for tax and accountancy roles. Deis only really knew early-career tech jobs. So that week it grew career stages from 3 to 5 years up to 7 or more, and kinds of work beyond tech, from tax and accounting to management, with a search so anyone can find their own field.

What they told me:

They read the job description before they swipe. I'd assumed people glance at a card and swipe. They opened every posting, and the posting's own bullet points had turned into a wall of paragraphs. The full posting now keeps its lists and headings.
They said the price was too low, and then they bought it. An MBA student telling me to charge more was not what I expected. What sold them was swiping and getting a CV, a cover letter and form answers where every line is backed by something they said. They bought it on the call with the October code: Deis's first sale.
Ollama needed a human the first time. Their first question was "why am I installing Ollama?" Once I explained that it runs the AI on their own laptop, they switched to it and kept going.
They liked that Deis never applies for them. They're graduating this month, and every time they open the app there are about 250 jobs that fit, instead of a blank scroll through LinkedIn or Indeed.

The posting they were reading, before and after their feedback:

And the sales. The first came on that call. The second came in on the day I wrote this post, from someone I've never met: nobody I know, nobody I sent it to. Deis is starting to travel by word of mouth.

People outside Ireland wrote back too. A friend in Germany asked for a German version, a friend in Australia sent a voice note about the swipe, and a friend in India wants it for remote roles in Ireland, which the check-in's remote and right-to-work questions already cover. Still, I'm keeping Deis to Ireland for now, on purpose. It's the job market I know from the inside, and every country does this differently: CV styles, languages, what employers expect to see. Other countries can come later. For now I'd rather build something that really helps people in Ireland than something for everyone that helps no one.

I also showed it to people at a networking event recently. The question I heard most was why I'd open-source it and charge so little. My answer: €9.99 pays for the server and the job feed, and the code stays open because a tool for people looking for work shouldn't be something anyone can take away from them.

Prize Categories

Best Use of Gemma: Gemma 4 E4B on the laptop and Gemma 4 26B/31B in the cloud do every AI job in the app, measured and guarded.
Best Use of Render: the hosted demo and the shared Irish job feed, with Key Value for the cache and rate limits.
Best Use of SerpApi: Google Jobs as a shared, cached feed for early-career roles across Ireland.
Best Use of Sentry Agent Tracing: traces of every workflow step and Gemma call, and one issue per guard rule, tagged by model.
Best Use of Mastra: per-request model chains with fallbacks, one agent per task, and a parallel kit workflow.
Best Use of a .tech Domain: deiscareers.tech is Deis's home: the web demo, the download page, checkout, and the shared job feed the desktop app reads.

I drafted this post with Claude Code and edited it myself. The code, the tests and the evals in the repo are the same ones I ran for the numbers above.

"Is AI going to replace me?" I built Droichead on Gemma 4 in one day, then pitched it with a flip chart

Muhammad Murtuza Hussain — Mon, 12 Oct 2026 08:18:38 +0000

This is a submission for the MLH x DEV Writing Challenge

The announcer struggled with the name. Droichead is Irish for "bridge", and it's not an easy word to read out cold. I was standing next to my friend Nithin, telling him the technical track was his. Then they read out mine.

I asked three more times whether they really meant me.

I've never taken a single technical module. I studied business and maths, and my master's is in cybersecurity risk management, which is governance, not code. I'd started LeetCode four days earlier. Everything I know about building software I learned at hackathons, and on Saturday 3 October, at Hacktoberfest Hack Day Dublin x The AI Collective, that classroom gave me a prize: Best Open-Source AI Project.

This post is the build behind it: what Droichead does, how an open-weight model runs it without being allowed to make things up, and what I did while the AI was writing the code.

TL;DR. Droichead is a calm, private career navigator for people whose work is being reshaped by AI, built for Ireland's multilingual workforce. A 90-second check-in gives you roles to grow into, an honest gap analysis, and a dated week-by-week plan that links only to real courses, preferring free and government-funded Irish programmes. It runs entirely on Google's open-weight Gemma 4: in the cloud, or fully offline on a laptop through Ollama. It works in seven languages, with no accounts and no database. I built it solo in one four-hour Claude Code session, and I pitched it with a flip chart.

What I Built

The question on the board

The organisers set out five tracks. With ten minutes left to choose, I was standing in front of the Job Displacement board, and I didn't need to go and interview anyone: my own role ends on 14 October. I was applying for everything, including jobs I'd never trained for, and asking the exact question the track was asking. Is AI going to replace me?

So I wrote a persona. Eva is a software engineer in Dublin. She keeps hearing about a role called Forward Deployed Engineer, a client-facing engineer who applies technology in the field, and wonders whether it's her way forward. She just doesn't know how to get there. Her pain points were mine:

The job market is tough.
Certificates are expensive.
In Ireland, a lot of hiring runs through referrals.
When you're applying for everything, it's hard to know which role is the right fit.

And in Ireland it's harder if you work in a second language. A big part of the workforce does: large Polish and Ukrainian communities, and the international staff who keep Dublin's tech and finance sectors running. The advice they get is generic, English-only and often fear-based. Meanwhile Ireland funds excellent upskilling through Springboard+, Skillnet Ireland and SOLAS eCollege, but most people never connect those programmes to a concrete next role.

What it does

A 90-second check-in. Tap-first and skippable: role, industry, experience, the skills you enjoy, how you feel about AI, and the hours you can give each week. You can dictate the answers, or drop in a PDF CV, which is read in your browser and never uploaded.
Pulse. Real articles from the last seven days (RTÉ, Silicon Republic, the Irish Times, the Guardian, TechCrunch), each with one line on what it means for you, next to live CSO Ireland unemployment figures.
Roles to grow into. Emerging roles like Forward Deployed Engineer, AI Solutions Engineer or AI-enabled Finance Analyst, ranked by how close they are to what you already do.
A gap analysis that leads with what you have. Then what's partly there, then what to build, with a time estimate at your hours per week, and a Listen button that reads it aloud.
Bridge the gap. Pick a goal date and get a phased, week-by-week plan with a portfolio project. Every course comes from a human-checked catalogue.
My plan. A timeline with a weekly streak, an .ics calendar export, a printable wall planner with QR codes that open each course from the paper, live job openings with how long ago each was posted, LinkedIn post drafts, local events, and a weekly check-in that re-plans around a bad week without guilt.

All of it works in English, Gaeilge, Polski, Українська, Español, Deutsch and Français: the interface, the AI's answers, read-aloud and dictation.

The idea behind it fits on a napkin, and it's the scroll animation on the landing page. Wanting to switch jobs is a wish. Give it a deadline and it's a goal. Put a plan behind the goal and you have a strategy. Act on it every week and that's success.

Demo

Try it: droichead.onrender.com. It's on Render's free tier, so the first load after a quiet spell takes a little while to wake up. Tap Try a demo for one of two personas: Aoife, a software developer in Dublin (English), or Оксана, an accountant in Cork (Ukrainian). Or do the check-in as yourself.

Pulse: roles to grow into	News for you, plus live CSO data

Gap analysis	My plan

Printable wall planner	One QR code per course

The wall planner is my favourite part. A plan that only lives in a browser tab is easy to close. A plan on your fridge, where you can scan the next course with your phone, is harder to ignore.

MuhammadMurtuzaHussain / Droichead

Droichead is a calm, private career navigator for people whose work is being reshaped by AI. It runs on open-weight Gemma 4 and works in seven languages.

Droichead

Bridge the gap to the job that's coming. Droichead (DRUH-hed) is Irish for "bridge".

Droichead is a calm, private career navigator for people whose work is being reshaped by AI. It runs on open-weight Gemma 4 and works in seven languages. It was built in Dublin in one day for Hack for Humanity (Hacktoberfest Hack Day Dublin x The AI Collective), on the job-displacement track: help people navigate changing roles, skills, opportunities and economic security.

Live demo: https://droichead.onrender.com · Licence: MIT

A wish to switch jobs is a fantasy. Give it a deadline and it becomes a goal. Put a plan behind the goal and you have a strategy. Act on the strategy consistently and that is success.

The problem, locally

AI anxiety is real, and it is not evenly spread. In Ireland, a big share of the workforce works in a second language. That includes large Polish and…

View on GitHub

How It Works

Browser: Next.js 16, React 19, Tailwind v4, Motion
  IndexedDB (Dexie): profile, plans, check-ins      pdf.js: CV read in the browser
        │  profile sent per request, never stored
        ▼
Stateless route handlers
  /api/pulse    RSS feeds + CSO PxStat ─► Gemma: roles, "what it means for you", economy
  /api/gap      Gemma: have / partly there / to build
  /api/plan     Gemma picks from a 32-item course catalogue ─► code schedules the weeks
  /api/replan   code reschedules ─► Gemma writes one kind sentence and one tiny next step
  /api/jobs     Arbeitnow + Remotive, matched to the target role
  /api/posts    Gemma: LinkedIn drafts
        │
        ▼
Gemma 4: Google AI Studio (26B-A4B) │ Ollama on a laptop (12B) │ any OpenAI-compatible endpoint

The model picks, the code owns the facts

Career advice is a bad place for a model to improvise. A made-up course link wastes someone's evening, and a made-up deadline wastes their month. So I split the work the way I'd split it with a colleague I trusted but checked:

Gemma decides	Code guarantees
Which roles fit, and why	Every news item is a real article from a real feed
What you already have, what's partly there, what to build	Unemployment figures come straight from the CSO API
Phases, tasks and minutes for each task	Every course link is one a human checked, picked by id
Which catalogue resource fits each task	The dates: weeks are computed from the goal date and your hours
A warm, specific line of encouragement	Re-planning: nothing stays overdue, and each week fits your hours

The model never writes a URL. It gets a catalogue of 32 resources (Springboard+, Skillnet Ireland, eCollege, Cyber Skills and more), each with an id, and it's told it may only use those ids. Then the server checks anyway. An id Gemma invents simply disappears:

// app/api/plan/route.ts: an id that isn't in the human-checked catalogue is dropped
const resourceId = t.resourceId && RESOURCE_BY_ID[t.resourceId] ? t.resourceId : undefined;

Every response is validated against a zod schema. If it doesn't validate, Gemma gets the validation error back and one more try:

// lib/llm.ts
for (let attempt = 0; attempt < 2; attempt++) {
  const text = await complete(messages, opts.maxTokens ?? 2000, opts.temperature ?? 0.5, signal);
  try {
    return opts.schema.parse(extractJSON(text));
  } catch (e) {
    messages.push({ role: "assistant", content: text });
    messages.push({
      role: "user",
      content: `That did not validate (${String(e).slice(0, 400)}). Reply again with ONLY the corrected JSON object.`,
    });
  }
}

And if the model is unreachable altogether, the demo personas fall back to pre-written content. A live demo in a room with shaky wifi should never dead-end.

The weekly check-in follows the same rule. When you tell it you're "a bit behind" or "way behind", plain code moves the tasks so nothing stays overdue and each week's load fits the hours you say you have. Gemma only writes the encouragement and one tiny next step. Rescheduling has to be right every time. Kindness is where a model earns its place.

There's one more guard in the system prompt: news text and CVs are treated as untrusted data, and the model is told never to follow instructions found inside them. A CV is exactly the kind of document someone could slip a prompt into.

One model family, three places

Where	Model	Why
The live demo	`gemma-4-26b-a4b-it` on Google AI Studio	Fast enough to pitch with
A laptop, offline	`gemma4:12b` on Ollama	Your answers never leave your machine
Anywhere else	Any OpenAI-compatible endpoint (DigitalOcean Inference, vLLM, Groq)	Swap providers with environment variables

I measured both main setups on the day, on the same calls:

Call	Laptop: Gemma 4 12B on Ollama	Cloud: Gemma 4 26B-A4B on AI Studio
Gap analysis	~9 s	~4 s
Roles	~28 s	~9 s
News commentary	~21 s	~8 s
26-week plan	~42 s	~23 s

Two things I learned the hard way, both visible in the agent session below:

Gemma 4 thinks at length by default, and it can spend the whole budget doing it. My first call to the 26B took 17 seconds and returned no answer at all, just thoughts. Setting thinkingLevel to minimal through Google's native API brought it to about 5 seconds, with valid JSON in Irish.
Gemma on Google's API has no system role. So the system prompt is folded into the first user turn:

// lib/llm.ts: Gemma on Google's API has no system role
const [sys, ...rest] = messages;
const turns = rest.map((m, i) => ({
  role: m.role === "assistant" ? "model" : "user",
  parts: [{ text: i === 0 ? `${sys.content}\n\n${m.content}` : m.content }],
}));
// ...
generationConfig: { temperature, maxOutputTokens: maxTokens, thinkingConfig: { thinkingLevel: "minimal" } },

A local model also handles one request at a time, and React's dev mode fires effects twice. So identical requests in flight share one generation, and when everyone waiting on a generation has gone away, it's cancelled so it stops blocking the queue.

Private by design

There are no accounts, no database and no tracking. Your profile and plan live in your browser's IndexedDB, with one-tap export and delete. The server routes are stateless: your profile is sent with each request and never stored. Your CV is read on your device with pdf.js. On the laptop setup, nothing leaves your machine at all.

An Agent Skill other agents can reuse

The method itself is packaged as skills/bridge-the-gap/SKILL.md, so any agent can run the same gap analysis and planning without Droichead's UI. Its rules are the app's rules: lead with strengths, prefer free and funded programmes, never invent URLs, treat CVs as data, and never post on the person's behalf.

The build, by commit

Seventeen commits, all on the day (Irish time):

Time	Commit
11:32	Initial commit
11:44	Skeleton: survey, pulse, gap analysis, planner
11:56	Redesign, real photography, RSS news
12:01	Six more languages, with a check that every locale has every key
12:03	The Agent Skill
12:25	AI moves to open-weight Gemma 4 on Ollama, locally
12:57	Gemma 4 on Google AI Studio, the scroll-drawn bridge, the wall planner
13:05	Render Blueprint
13:29 to 13:43	Social preview, QR codes, streaks, voice, CV upload, live CSO data, live jobs, weekly re-plan
14:35	README with screenshots

On Lighthouse it scored 93 for performance, 89 for accessibility, 100 for best practices and 100 for SEO.

Partner Technologies

Gemma 4 (open-weight, from Google)

Gemma does every AI job in the app: roles, news commentary, gap analysis, plans, check-in messages and LinkedIn drafts. Open weights matter for this product in three ways:

Privacy. A career plan is built from your work history and your worries. On Ollama it never leaves your laptop, and the code to do that is the same code the live demo runs.
Cost. People looking for their next role are often the people least able to pay for another subscription. A local model costs nothing per plan.
Control. Because Gemma runs inside my own pipeline, every answer passes through code I wrote before anyone sees it: schemas, the id check, deterministic scheduling. I could also swap sizes and providers and measure the difference, which is how I picked 26B-A4B for the demo.

It handled Ukrainian, Polish and Irish JSON well enough to ship. The one honest caveat: a native speaker hasn't reviewed the Gaeilge yet.

Google AI Studio

I'd used AI Studio for the first time the day before, building Pīzhù for a DEV weekend challenge. That practice run turned out to be the best preparation I could have done, because at noon on hack day I needed a plan B fast. The native API was the key: it's the only route where I could turn Gemma's thinking down to minimal.

Render

The whole deployment is one render.yaml Blueprint: a free Node service in Frankfurt (the closest region to Dublin), built with npm ci && npm run build, a health check on /api/health, and a redeploy on every push to main. Render asks for the AI Studio key when you create the Blueprint, so the key never touches the repo. The one thing to know: the free tier sleeps after about 15 minutes idle, so I opened the site a couple of minutes before my pitch.

DigitalOcean (the plan A that didn't happen)

DigitalOcean was the diamond sponsor, and I wanted to build on it. Joanna, one of the organisers, spent time getting my credits through, but the billing set-up wouldn't accept either of my cards, and without billing I couldn't generate a key for DigitalOcean's Inference. I'm including it because the code still carries it: there's a .do/app.yaml App Platform spec in the repo, and lib/llm.ts talks to any OpenAI-compatible endpoint, with DigitalOcean Inference as the default base URL. Pointing Droichead back at DigitalOcean is a matter of setting a key and a model name.

The detour took less than half an hour, and it made the product better. Discovering that my laptop already had Gemma 4 on Ollama is why "your answers can stay on your computer" is a feature and not a slogan.

Hackathon Experience

Getting there

At 00:33 I was wrapping meal prep for the week. By six I was on a bus from Galway to Dublin. The event had two names, Hacktoberfest Hack Day Dublin x The AI Collective Dublin Chapter on MLH and Hack for Humanity: Dublin on Luma, and I was on Luma's waiting list, so I didn't know where the venue was. I picked a direction and walked for twenty minutes. It was the wrong one. A taxi later I was one of the first people through the door at Dogpatch Labs, and Ashley, one of the organisers, turned my morning from lost to ready within a few minutes of chatting.

Seven tables, all full. Around 45 people in roughly 15 teams, from Ireland, Brazil, Poland, Ukraine, India and elsewhere in Asia. While everyone else talked architecture, I stood in a corner with Avi from Give a Go, who told me I had a voice for radio. It was exactly what I needed to hear.

Twenty minutes with nothing to build

I went outside and recorded a voice note: what the product should do, what the agent workflow should look like, and where AI should earn its place rather than replace a simple calculation. Then I handed it to Claude Code. That voice note is the first message in the session below.

While the first build ran, I had twenty minutes with nothing to do, and that's the part that catches people out. You can't interrupt the build without slowing it down. So I asked a different question: what can Claude not do that I can? The answer was pitching.

There was a flip chart in the corner. I tore off a sheet and split it into four quadrants: Eva and her thought bubble, "Is AI going to replace me?"; FDE, covered with sticky notes I could peel back with the audience; the pain points; and how Droichead answers each one. Then I thought about latency. A model takes several seconds to answer, which is a long time in a three-minute pitch, so I put the project name, a tagline and the tech stack on sticky notes to give the audience something to read while Gemma worked.

An illustration, redrawn from my description. The real one had more marker and fewer straight lines.

Three minutes, one flip chart

Most teams had slick slides. I dragged in a stand with a folded sheet of paper and started talking with my laptop still unplugged: "Hi folks, I'm Muhammad Murtuza from Galway, and Galway people are known to be a bit crazy, so what you're about to hear is a crazy guy's storytelling. Let's meet Eva." By the time I reached her pain points, I'd plugged in and gone live.

For the live demo I picked a volunteer: Nithin, who has years in offensive security and had no idea what I was about to do. I pasted his LinkedIn profile into Droichead. On the venue wifi the model took about twelve seconds, so I walked the room through Eva's plan while it worked, then came back to his result. The role it suggested was one he said he actually wanted: "that's the role I want." A real reaction, live, is hard to fake on a slide.

I ran out of time before the languages, the accessibility work or the live Irish data. I finished on the clock anyway, on the Lighthouse scores and a QR code to the live site.

Waiting to lose

Every other team had a back-and-forth with the three judges. I got one question from one judge: what's the human element? I said Droichead sends you out of the app, to events and to people on LinkedIn, because referrals matter in Ireland. Then I sat down certain I'd lost. I'd given them a person, a feeling and a solution, and in a room full of builders that felt like too little.

It was enough. Droichead won Best Open-Source AI Project. Congratulations to Moldmate by Christopher Svitok and team, who won the non-technical Build Without Code track. The prize was €25 and three sessions with Andrei, a Head of AI, which could not have come at a better moment for someone looking for their next role in AI and security.

What I'll remember

When the AI is building, ask what only you can do. Claude writes code faster than I ever will. It can't read a room, choose a volunteer, or cover twelve seconds of silence. Those twenty minutes were the most valuable of my day.
Start with a problem you live. Eva was a version of me, and I think the room could tell.
Pitch for the room, not the rubric. The flip chart wasn't a gimmick. It was me being myself, and it gave people something to read while the model thought.
Don't read the judges by the number of questions. I was sure one question meant I'd lost.

The rule that came out of that day, the model picks and the code owns the facts, became how I build. I used it the day before in Pīzhù without a name for it, and again the week after in Return Route.

What It Can't Do Yet

The Gaeilge needs a native speaker's review. The Irish interface was written with AI help and checked by script, not by a fluent speaker.
The match percentages are Gemma's estimates. They rank roles sensibly, but they aren't a validated score, and the app shouldn't pretend otherwise.
The catalogue is 32 hand-picked resources. That's enough to be useful and small enough to check by hand. It needs to grow, and to be maintained.
Live jobs come from Arbeitnow and Remotive, which skew towards Germany, the UK and remote roles. Irish job boards are next.
It answers the judge's question only halfway. It sends you to events and drafts your LinkedIn posts, but it doesn't introduce you to anyone yet. Partnering with Skillnet Ireland, Intreo or community groups that support Polish and Ukrainian workers would.
It needs a signal. An offline-first PWA, for people with patchy data, is on the list.

My Agent Session

I built Droichead with Claude Code in one session on hack day, from the voice note to the README. This is a curated version: my prompts lightly trimmed, Claude's turns summarised, and the tool calls and their outputs real. It includes the moment DigitalOcean's billing fell through, the benchmark that found Gemma 4 on my laptop, and the thinking-budget fix.

Building Droichead with Claude Code at a Dublin hack day: from a voice note to a winning open-weight career bridge

You

[11:25 Dublin time. Dictated as a voice note outside the venue, lightly trimmed.]

Project idea. I don't have the name in my mind, but I want a platform where users can... oh, you know what, actually, not use a login. Let's keep it safe, secure, and very much browser side data storing. Users put in what they do, their employment history, their preferences, in a very quick, playful survey that is not boring. Then the platform tells them the current news, what's happening in the industry, how the roles are changing, how the economic times are changing, and how people can adapt. AI gives anxiety to everyone that it will replace people, but I suppose the correct answer is that it will ask people to upgrade a bit, with AI-enabled tools.

Now here comes the wow part. I don't want just an overview, Google News can do that. The person clicks one of the top roles, say forward deployed engineer, and it shows how they can bridge the gap from their current profile. When they hit "I want to bridge the gap", the AI makes them a custom planner: certifications, a calendar, job alerts posted in the past 48 hours, LinkedIn post recommendations so they can be visible, and events nearby.

Because just thinking about switching a job is a fantasy. Having a deadline with what you want is a goal. A plan with a deadline and a goal is a strategy. And consistent actions are success.

Let's plan this, with an Irish palette for the UI, and a multilingual UI in Irish, Polish, Ukrainian, Spanish, German and French.

Agent

Found your event: Hacktoberfest Hack Day Dublin x The AI Collective. It ends at 16:00 Dublin time today, which leaves about 4 hours of build time.

▸ mcp__devrelay-gateway__get_mlh_event Hacktoberfest Hack Day Dublin x The AI Collective Dublin Chapter

Input

Hacktoberfest Hack Day Dublin x The AI Collective Dublin Chapter

Output

Ends 16:00 IST. Tracks include Job Displacement. Prize category: Best Open-Source AI Project (open-source or open-weight AI as a real part of the product, public GitHub repo).

What the event details change:
- The theme fits. Your idea lands squarely on the Job Displacement track, and the event asks for a local problem, so the pitch is "built for Ireland's workforce, in the languages Ireland actually speaks": large Polish and Ukrainian communities, and international tech workers in Dublin.
- Courses should point at Irish public programmes: Springboard+, Skillnet Ireland, SOLAS eCollege, Intreo.
- For the open-source AI prize, the model has to be open-weight and the repo public and licensed.

Agent

Scaffolding Next.js, then the data model (IndexedDB, no accounts), zod schemas for every model output, a human-checked course catalogue the model can only reference by id, and four API routes. The first build passes.

▸ Bash Add DO spec, MIT license, commit and push

Input

$ Add DO spec, MIT license, commit and push

Output

[main e22f68a] Droichead skeleton: survey, pulse, gap analysis, planner on DO Gradient

The news API I planned on (GDELT) is timing out from here, so I'm testing RSS feeds instead:

▸ Bash Debug the GDELT fetch timing and response

Input

$ Debug the GDELT fetch timing and response

Output

TypeError: fetch failed. ConnectTimeoutError (attempted address: api.gdeltproject.org:443, timeout: 10000ms)

▸ Bash Test candidate news RSS feeds for speed

Input

$ Test candidate news RSS feeds for speed

Output

200 0.18s rte.ie business, 40 items
200 0.26s irishtimes.com business, 100 items
200 0.24s techcrunch.com AI, 20 items
200 0.43s theguardian.com AI, 20 items

RSS is faster and gives real Irish headlines (RTÉ, the Irish Times, Silicon Republic). Switching.

Agent

Redesign with the design-taste skill: Geist (it covers Irish, Polish and Ukrainian characters), Phosphor icons, real photos of the Samuel Beckett Bridge in Dublin and the Brian Boru Bridge in Cork (credited), dark mode. Then all 7 locales, with a script that checks every locale has every key and no dashes.

▸ Bash Add and run i18n key parity check

Input

$ Add and run i18n key parity check

Output

en, ga, pl, uk, es, de, fr: all keys present, 0 dashes

Next, the README (judges read it) and a small Agent Skill, skills/bridge-the-gap/SKILL.md, that packages the gap-analysis method so any agent can run it. Pushed. The flow works end to end, but only on demo data: the AI isn't connected yet.

You

i cant find the .env.local and from which section in DO shall i grab the key from
let's come to this when 1 is done, because i did not understand this.

the credits are in DO so let's use it if needed

Agent

You couldn't find .env.local because it didn't exist yet, and dotfiles are hidden in Finder. I've created it, and it's already in .gitignore, so the key will never be pushed.

DigitalOcean renamed the product: it's now Inference (it used to be Gradient). Control panel, INFERENCE, Manage, Create model access key, All models, No VPC network, then copy the key right away: it's only shown once.

You

the digital ocean is giving me issues with payment information and stuff i dont think i can get a key, can we do alternative plan?

Agent

Good news: Ollama is already installed on your Mac, with open-weight models downloaded.

▸ Bash List local Ollama models

Input

$ List local Ollama models

Output

gemma4:12b 11.9B Q4_K_M 8.0 GB
gemma4:e4b 7.5B Q4_K_M 6.6 GB

▸ Bash Benchmark Gemma 4 12B speed and Ukrainian JSON output

Input

$ Benchmark Gemma 4 12B speed and Ukrainian JSON output

Output

gemma4:12b 30.7s (includes loading) 21.2 tok/s
{"have": ["Глибоке розуміння фінансової звітності", "Досвід аудиту та аналізу даних", ...], "weeksEstimate": 18, ...}

▸ Bash Benchmark Gemma 4 E4B and warm 12B

Input

$ Benchmark Gemma 4 E4B and warm 12B

Output

gemma4:e4b 11.7s 43.4 tok/s
gemma4:12b 15.0s 23.6 tok/s (warm)

Gemma 4 12B writes good Ukrainian. I'm making Ollama the default backend, keeping the OpenAI-compatible path for DigitalOcean if billing ever works, and adding a warm-up call so the first real request is fast.

Agent

A local model handles one request at a time, so: identical in-flight requests now share one generation, abandoned ones are cancelled when the user navigates away, and the pulse is split into two requests so roles show up before the news.

▸ Bash Time live news and gap calls

Input

$ Time live news and gap calls

Output

roles ~28 s, news ~21 s (real Irish headlines with a 'for you' line), gap ~9 s

We don't need DigitalOcean at all. All the AI now runs on your laptop on open-weight Gemma 4, so "your answers never leave your computer" is literally true. Pushed.

You

okay great! let's make the Ui much better more interactive i suppose and makes it look wow, you know like an amazing Ui/UX, at the moment it looks like a government website got modernized with AI slop. source more skills and improve the UI.

Also, do you think we can deploy this? I can grab keys from google Ai studio and stuff if needed. let;s polish it to the best extent we can and make this an actual wow

Agent

Adding a Google AI Studio provider (it serves the open-weight Gemma family), then checking the key against the model list. I won't print the key.

▸ Bash Benchmark Gemma 4 models on Google API

Input

$ Benchmark Gemma 4 models on Google API

Output

gemma-4-26b-a4b-it 200 17.1s 0 tok <thought> ...
gemma-4-31b-it 200 48.1s 74 tok <thought> ...

Both models think at length by default, and it eats the whole token budget. Testing whether thinking can be turned down through the native API:

▸ Bash Test thinkingLevel options for Gemma 4

Input

$ Test thinkingLevel options for Gemma 4

Output

minimal: gemma-4-26b-a4b-it 200 5.3s, valid Irish JSON {"have": ["Taithí mór i gcúrsaí airgeadais", ...]}
low: 400 "Thinking level is not supported for this model."

▸ Bash Benchmark Gemma 4 31B with minimal thinking

Input

$ Benchmark Gemma 4 31B with minimal thinking

Output

gemma-4-31b-it 500 34.2s INTERNAL

Gemma 4 26B-A4B with thinkingLevel minimal: 5 seconds, valid output. The 31B errors, so 26B-A4B it is. Gemma on this API also has no system role, so the system prompt gets folded into the first user turn.

Agent

▸ Bash Test Google-backed routes on prod server

Input

$ Test Google-backed routes on prod server

Output

{"ok":true,"ai":{"provider":"google","model":"gemma-4-26b-a4b-it"}}
gap: real 4.20 s
pulse roles: real 9.42 s

Roughly 4 times faster than local. Now the redesign: dark emerald theme, a floating glass nav, the hero photo of the bridge, a scroll-drawn arc where Wish, Goal, Strategy and Action light up in turn, and a printable A4 wall planner.

One honesty fix before deploying: the landing page says the AI runs "on this computer", which won't be true on a server. Rewording it in all 7 languages so it's true for both setups.

You

we are going with render for deployment, so will it be a blueprint or something else

Agent

A Blueprint: a render.yaml in the repo that describes the service, so Render sets it up the same way every time and asks you for the secret key. Free Node service in Frankfurt (the closest region to Dublin), npm ci && npm run build, health check on /api/health, auto-deploy on push. Added and pushed. Paste your AI Studio key as GOOGLE_API_KEY when Render asks, and send me the URL when it's live.

You

https://droichead.onrender.com/ here you go, suggest me ideas on how we can improve the project or polish it more.

Agent

▸ Bash Smoke-test live Render deployment APIs

Input

$ Smoke-test live Render deployment APIs

Output

gap: real 3.80 s
news: real 8.00 s, 4 stories
- irishtimes.com | Use of AI on the rise in workplaces, says PwC
- irishtimes.com | Workday to cut jobs in Dublin HQ but will press on with AI
- techcrunch.com | The rise of the GTM engineer

The live site works. It's 13:23, so about 2.5 hours left. Ranked by how much they help against the effort:
1. MLH submission and a demo script. 2. A 60-second backup video. 3. Make the 23-second plan wait feel intentional.
4. QR codes on the printed wall planner. 5. Live CSO Ireland figures. 6. Read-aloud and voice answers in all 7 languages. 7. Celebrate progress, with a weekly streak.
8. Weekly check-in and re-plan. 9. Real job listings. 10. CV upload, read in the browser.
Also: ask an Irish speaker at the venue to check the Gaeilge, and open the site 2 minutes before judging, because Render's free tier sleeps.

You

okay let's do , 3, 4, 5, 6, 7. 8, 9, 10

i will work on 1 and 2 after we have done the above task. can you add the social preview image btw?

Agent

Quickest first: the social preview, then 3, 4, 7, 6, 10, 5, 9 and 8, committing as I go.

▸ Bash Add CSO unemployment fetcher and test it

Input

$ Add CSO unemployment fetcher and test it

Output

{ month: '2026 September', rate: 5, prev: 5, youth: 12.5 }

▸ Bash Test live jobs endpoint for several roles

Input

$ Test live jobs endpoint for several roles

Output

== Forward Deployed Engineer (3 in the last 48h)
  7 h | Arbeitnow | Forward Deployed Engineer | Tacto | Munich
  9 h | Arbeitnow | Forward Deployed Engineer | Flow Engineering | London

All eight features plus the social preview are built, pushed and confirmed on the live site: the staged plan loading, a QR sheet with one code per course, confetti and a weekly streak, dictation and Listen buttons, PDF CVs read in the browser with pdf.js, live CSO figures (5.0% unemployment, 12.5% for under-25s), live jobs with how long ago each was posted, and a weekly check-in that reschedules without guilt.

You

you make the mlh submission thing, i will look at it and submit
i will do that

Agent

▸ Bash Verify no secrets in git; get commit time range

Input

$ Verify no secrets in git; get commit time range

Output

0 matches of key in git history (should be 0)
2026-10-03 11:32:45 +0100 Initial commit from Create Next App
2026-10-03 13:43:40 +0100 (latest)
16 commits

The draft is in SUBMISSION.md. I haven't created or submitted anything on MLH. Checked against the rules and the Best Open-Source AI Project challenge: built today (16 commits, 11:32 to 13:43), public repo with an MIT licence, Gemma 4 does all the AI work, the Agent Skill follows the open standard, no secrets in the history, and an AI disclosure section that names Gemma 4 at runtime and Claude Code while building.

You

everything is done, i have submitted, just update the read me, add screenshots if needed and push to github

Agent

Capturing 2x screenshots of the live site with headless Chrome, reviewing each one, retaking the two where the floating nav covered a heading, then compressing them to JPEG.

▸ Bash Commit README and screenshots, push to GitHub

Input

$ Commit README and screenshots, push to GitHub

Output

[main b2023c8] README: full feature tour with screenshots, open-source AI, privacy, deploy and AI disclosure
11 screenshots, about 1.9 MB

The README is pushed with all 11 screenshots, the architecture, the open-source AI setup, privacy, how to deploy, and the AI disclosure.

You

quick question which model is faster at responses, the local or cloud one

Agent

The cloud one, by about 3 to 5 times. What we measured today:

Call	Local, Gemma 4 12B on Ollama	Cloud, Gemma 4 26B-A4B on Google AI Studio
Gap analysis	~9 s	~4 s
Roles	~28 s	~9 s
News commentary	~21 s	~8 s
26-week plan	~42 s	~23 s

The cloud model is bigger, but it's a mixture of experts, so only about 4B parameters work on each token. The local model's advantage is privacy and resilience: answers never leave your machine, and it works without internet. That's a good backup if the venue wifi drops during the demo.

Thank You

To Ashley, Joanna and Andrei from The AI Collective's Dublin chapter, to Avi from Give a Go, and to Major League Hacking for running the day. Joanna, thank you for sorting out my DigitalOcean credits. Nithin, thank you for being the best volunteer anyone could ask for.

If you're nearby, I'm hosting a Hacktoberfest Fest in Galway on 29 or 30 October with the University of Galway Cybersecurity Society. Come and build something. And if you're a non-coder wondering whether to walk into a room like that one: go. Bring what you're good at, and let the AI do what it does best.

Live demo: droichead.onrender.com
Code (MIT): github.com/MuhammadMurtuzaHussain/Droichead
MLH submission: Droichead on MLH
The longer story of the day: I Never Studied Code. I Still Won the Technical Track. on Medium

Photos of the Samuel Beckett Bridge (DXR) and the Brian Boru Bridge (Joachim Kohler-HB) are from Wikimedia Commons, CC BY-SA 4.0. Unemployment data from CSO Ireland (MUM01).

Built with AI assistance (Claude Code) on the day, and written up with AI help. Gemma 4 generates the advice inside the app. The product decisions, the pitch and the flip chart were mine, and I reviewed and edited everything here.

I walked an hour for 30 cents: Gemma plans litter walks that end at a deposit machine

Muhammad Murtuza Hussain — Sun, 11 Oct 2026 23:13:59 +0000

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass

At 18:27 on Sunday, a machine at Lidl in Galway printed me a voucher for €0.30: two cans at 15 cents each. It's the first deposit I've claimed in two years of living in Ireland. I don't buy drinks. I carry water in a flask.

The cans weren't mine. I picked them up on a walk that an open-weight model planned for me, along with six other bits of litter that paid nothing at all.

There's a story going round 9GAG about someone in Germany who paid for a PS5 with deposit bottles. I couldn't verify it. My number is easier to check, and I kept the voucher.

TL;DR. Return Route plans a walk through the spots where cans and bottles get left behind, and ends it at a deposit return machine. When you get back, one photo of your haul and Gemma counts it. The refund comes from the deposit table, never from the model. Gemma can run in the cloud, on your laptop, or (untested yet) in your phone's browser. I took it on a real walk in Galway: about an hour outside, 8 pieces of litter picked up, 2 that paid, €0.30. You can keep the money or give it away.

What I Built

Ireland has had a deposit return scheme, Re-turn, since February 2024. A can or a small bottle carries 15c, a big bottle 25c, and you get it back from a machine at the supermarket. So every can in a hedge is a refund nobody claimed.

Return Route turns that into a reason to go outside:

Pick how long you've got: 30 minutes, an hour, 90 minutes or your own time. You can add a note like "finish at Tesco, stay off the main road".
Gemma plans a loop through the places where drinks get left behind (picnic tables, pitches, viewpoints, benches near an off-licence) and finishes at a return machine. You get a range for what you might make, never a promise.
Put the phone away. The route goes to Google Maps, and a short briefing is read aloud: where you're going, what to look for, one safety tip.
Back home, take one photo. Gemma counts the containers, says which ones the machine will refuse (crushed, damaged, no deposit mark) and prints an itemised voucher. Then you keep the money, or switch on Walk for a cause: the app turns green, the refund goes to a cause you name, and Gemma drafts a post to get others walking.

Screens from the live site: a real plan from Terryland Forest Park on Gemma 26B, then the app's sample haul photo. That photo is generated, with deposit stickers added so the marks are readable.

The screen is on at the start and at the end. In between, it's Google Maps in your pocket and your eyes on the ground. That was the rule I designed around: the app's job is to get you out the door and then get out of the way.

It's for people who walk anyway and would like the walk to do something: dog walkers, students, anyone who joins a local cleanup. I volunteer on weekend cleanups in Terryland Forest Park, which is why the demo starts there.

It covers Ireland's Re-turn and 18 other European deposit schemes, each with its own rates and rules. Return Route is unofficial and not affiliated with Re-turn or any scheme operator.

Demo

The full walk, from planning at home to the voucher, filmed on Ray-Ban Meta glasses and my phone (12 minutes, with chapters):

The one-minute version:

Try it: return-route.onrender.com. It runs on Render's free tier, so the first load after a quiet spell takes about 50 seconds.

Not in Europe? Open return-route.onrender.com/?demo, or tap the demo button on the home screen. The guided demo plans a real walk from Terryland Forest Park with Gemma, plays it on the map, then shows the actual haul from my walk and the voucher it earned. It never touches your own totals.

I took it outside

Sunday 11 October, east Galway, 15°C and overcast. Times are Irish time.

17:26: Planned a 90-minute walk at home, with Gemma 4 26B in the cloud. The app's guess: €1.05 to €3.85.
17:30: Out the door. No gloves. (Bring gloves.)
Before I'd left the house: a Monster can with the Re-turn logo, not crushed. 15c.
On the road: a crushed can (the machine refuses crushed ones, but it's still litter, so it went in the bag), a wrapper, and an off-licence the planner had scored as a hotspot.
Stop 1, the park: spotless. I did find a playground five minutes from home I'd never seen.
Between stops: a big bottle, damaged, so it pays nothing. Then a Strong Power can in a hedge: the first real score of the day. A squashed Coca-Cola can and a carton.
Stop 2, the skate park: busy with kids, so I left it to them. A glass bottle stayed in the bush: glass isn't in Re-turn, and it's not something to handle bare-handed.
Stop 3: Google Maps led me to a college fence with no way in. It was getting dark and the last stop was far, so I headed for Lidl. My guess on camera: "about 30 cents".
18:19: I photographed the haul. The laptop tier failed first, because the laptop was at home. The cloud tier read it: 2 cans, deposit mark not visible, the crushed cans and the bottle struck off. €0.00 for sure, up to €0.30.
18:27: The Re-turn machine took 2 cans. Voucher: €0.30. The top of Gemma's range, exactly my guess, and well below the app's estimate.

What I said outside Lidl, unscripted: "the open source project that I just made is working very well … we touched grass, I hope that counts."

What the walk taught me

My neighbourhood is cleaner than the planner thought. It guessed €1.05 to €3.85 and I made €0.30. I'll take that as good news about east Galway. It's also exactly what the app's hotspot history is for: every logged walk shifts the estimate for the stops you visited.
The stops were the quietest part. The cans were in hedges, on walls and along the road near the off-licence, not at the picnic tables. The planner's starting scores favour parks, and on a clean Sunday the park was clean.
A stop behind a fence is a dead end. The map said there was something worth visiting; it didn't say you can't get in.
Photo close, labels up. From above, in a bag, Gemma couldn't confirm the small Re-turn logos. The + button fixed the count by hand.
Crushed doesn't pay. Pick them up anyway.
Bring gloves.

What I changed after the walk

No more stops behind a school gate. Pitches and picnic tables inside school or childcare grounds, and anything mapped as private, are no longer stops, unless the map marks that pitch as open to the public. University campuses stay in, because they're usually open. When I checked the map data for east Galway afterwards, 17 pitches and 6 picnic tables were inside school grounds; the city snapshot had 51 more school pitches and a school playground. They're gone now.

The first version still leaked 6 pitches when the map came from vector tiles. A place near the edge of a tile also appears in the next tile's margin, and that tile only carries a sliver of the school's outline, so the check passed. Each place is now read only from the tile it's actually in.

Code

MuhammadMurtuzaHussain / return-route

Return Route

A walk that pays. Gemma plans a loop through the spots where cans and bottles get left behind,
and ends it at a deposit return machine. Keep the refund, or give it away.

Ireland's Re-turn scheme pays 15c for a can or a small bottle and 25c for a big one, so every can in a hedge is a refund nobody claimed. Return Route turns that into a reason to go outside. Tell it how long you've got. It plans a walk past picnic tables, pitches and viewpoints near off-licences, gives you an honest range for what you might make, hands the route to Google Maps, and then gets out of your way.

When you're back, take one photo of your haul. Gemma counts the containers, flags the ones the machine will refuse and works out your refund from the deposit table. Keep the money, or switch to…

View on GitHub

MIT licensed, built during the challenge week, with 54 tests. If you only read six files, read these:

File	What it does
`src/lib/ai/guard.ts`	Every rule Gemma can't break: real stops only, no money talk, no bins
`src/lib/countries.ts`	19 deposit schemes, and the only place money comes from
`src/mastra/workflows/planWalk.ts`	The planning workflow, with map, weather and events in parallel
`src/lib/plan/overpass.ts`	OpenStreetMap places, minus anything behind a school gate
`src/lib/ai/edge.worker.ts`	Gemma 4 E2B in the browser on WebGPU (untested on a phone)
`src/lib/privacy.ts`	What Sentry never sees: coordinates, IPs, cache keys

Run it on your own laptop:

ollama pull gemma4:e4b
git clone https://github.com/MuhammadMurtuzaHussain/return-route && cd return-route && pnpm install
cp .env.example .env.local   # MODEL_PROVIDER=ollama
pnpm dev                     # http://localhost:3100

How I Built It

Gemma judges, code guarantees

A small model will sometimes invent a park, promise you a fiver, or tell you to go through the bins. So I split the work. Gemma does the parts that need judgement. Plain code owns everything that has to be right, and Gemma can't override it.

Gemma decides	Code guarantees
Which stops, in what order, and why each one	Every stop is a real place from the map, and the walk fits your time
What's in the photo: material, size, mark visible, crushed or not	What it pays, from the deposit table
What to look for, and one safety tip	The place names in the spoken briefing
One opening line for your post	The count, the amount and the cause in that post

Gemma picks from a list of real places, and a stop it invents is dropped. A route that's too long is trimmed against the real walking path. Money never comes from the model: any sentence where Gemma mentions an amount is removed before it's shown or read aloud.

/** Gemma's words are read aloud; they must not promise money the app did not compute. */
export function stripMoney(s: string): string {
  return s
    .split(/(?<=[.!?])\s+/)
    .filter((sentence) => !/[€£$]\s?\d|\d+\s?(euro|eur|cent|kr|zł|ft)\b/i.test(sentence))
    .join(" ")
    .trim();
}

/** Bins belong to the people who rely on them. Keep "leave bins alone", drop "look in the bins". */
export function leaveBins(s: string): string {
  return s
    .split(/(?<=[.!?])\s+/)
    .filter((sentence) => !/\bbins?\b|pfandring/i.test(sentence) || /\b(leave|don'?t|do not|never|avoid|not)\b/i.test(sentence))
    .join(" ")
    .trim();
}

The walk showed why the split matters. Gemma couldn't see the deposit marks in my bag photo, so it didn't guess. It reported "mark not visible", and the code turned that into a range: €0.00 for sure, up to €0.30. The machine paid the top of it. When a model that handles money can't see, I want it to say so, and this one did.

That split is also what should let a 2B model in a phone's browser do the same job as a 26B model in the cloud.

One model family, three places

Where	Model	Where your haul photo goes
In the cloud	Gemma 4 26B-A4B through Google AI Studio	To Google
On your laptop	Gemma 4 E4B through Ollama	Nowhere: it stays on your laptop
In your phone's browser	Gemma 4 E2B on WebGPU (transformers.js), about 3.4 GB once	Nowhere: it's read on the phone

You pick in Settings. The prompts, the guard and the deposit table are the same for all three.

The phone tier is untested. The code is in the repo and the production build bundles the worker and the WebGPU runtime, but I haven't had an Android phone to run it on, so I can't tell you how long the download takes or how fast it plans. Treat it as the part I'd test first.

Planning needs open map, weather and routing services (OpenFreeMap, Open-Meteo, Valhalla), so your start point goes to those whichever tier you pick. What changes between tiers is where your photo and the model's work go.

The planner: a Mastra workflow

place ──► map ║ weather ║ events ──► assemble ──► pick ──► route
 │          │      │         │          │          │         │
 deposit    OSM    Open-     SerpApi    score      Gemma     Valhalla walking
 scheme     POIs   Meteo     (optional) hotspots   picks &   route, trimmed
 for the                                           orders    until it fits
 country                                           2-3 stops

The map, the weather and today's events are fetched in parallel. The score is a hotspot prior for each kind of place, times yesterday's weather (a warm evening leaves cans behind), the day of the week, any match or gig nearby, and your own past hauls. Nobody has a live litter feed, so the estimate starts as an honest guess and gets sharper with each walk you log. That history stays on your device. There are no accounts.

If your country has no deposit scheme, the first step stops the workflow with a plain message instead of planning a walk that can't pay. On the phone tier, the server runs the first half of the same workflow, Gemma picks the stops in a Web Worker, and the server checks and routes the result.

Here's one plan from the live site, as Sentry traced it. The Gemma call is 7.2 of the 8.7 seconds:

Measuring it

I wrote 8 Galway walks (different starts, lengths and notes like "finish at Lidl" or "stay off the main road") and ran them through both server tiers before and after tightening the planner:

Tier	Plans the guard didn't touch	Too long	Invented stop	Finished where asked	Time per plan
Cloud, 26B-A4B, before	7/8	1	0	4/5	5.2 s
Cloud, 26B-A4B, after	8/8	0	0	5/5	5.3 s
Laptop, E4B, before	6/8	2	0	4/5	5.7 s
Laptop, E4B, after	7/8	0	1	5/5	5.4 s

The fix was mostly code, not prompting: for every return point on offer, the planner works out which stops still fit if the walk ends there, a shop you name becomes the finish, and two stops in the same field get distinct names. The one stop E4B invented was caught and dropped.

To be clear about what this measures: it shows Gemma follows the rules. It doesn't show the stops have cans. Only walking tells you that, and on my one walk, the park was clean.

The haul reader has an eval harness too (pnpm eval), but only one real haul so far: the bag from this walk. Both server tiers read it as 0 eligible, because the marks were too small from above. The real answer was 2. That's why the camera screen says "labels up, nothing stacked", and it's the first thing I'll measure properly.

When the cloud gets turned away

Locally, everything worked. On Render, planning failed. Sentry showed why: every Overpass mirror was answering the server with errors, and the place lookup and weather service were returning 429. Render's free tier sends traffic from IP addresses shared by many apps, and public map servers rate-limit them. A laptop never sees that.

So the map now has a chain of fallbacks:

Render Key Value, which caches each neighbourhood for 12 hours.
A bundled OpenStreetMap snapshot of Galway, so the demo never waits on a map server.
OpenFreeMap vector tiles from a CDN. A 30-minute area took 1 to 2 seconds in Galway, Berlin, Copenhagen, Amsterdam and Vienna. Return machines come from Overpass alongside, with a 6-second budget.
Full Overpass.
The walker's own browser, which fetches the map from their connection and plans again.

The side effect is that plans now work anywhere in Europe, not just in Galway. The whole service is one render.yaml Blueprint: the web service and the Key Value cache, deployed on every push to main.

What Sentry sees, and what it shouldn't

Every Gemma call is an agent span with the model, tokens and latency, so I can see the planner and the haul reader side by side. Prompts and replies are never sent: the Input tab is empty on purpose.

Every time the guard overrules Gemma, that's an issue tagged with the tier and the model. The one at the top of the guard list is real: E4B planned a route too long for the time. The three below it I triggered on purpose, to check that the phone tier's picks are guarded and reported too.

And then I found my own walk in it. Taking screenshots for this post, I searched the traces and found 415 weather spans from the last two weeks with the walker's position in the URL: latitude=53.2845&longitude=-9.0420, accurate to about 10 metres, from both the browser and the server. The cache spans were worse: the rate limiter's key held the walker's IP address, and the map cache's key held rounded coordinates. I had a privacy block in the Sentry config, and it didn't cover either.

The fix is one small file shared by the browser, server and edge configs. URLs lose their query strings, and cache keys are cut down to their kind:

/** "https://api.open-meteo.com/v1/forecast?latitude=53.28…" → "https://api.open-meteo.com/v1/forecast" */
const URL_QUERY = /(https?:\/\/[^\s?#"]+)\?[^\s#"]*/g;
/** "incr rr:rl:plan:<ip>:29862636" → "incr rr:rl"; "get rr:area:v2:53.28,-9.04,2500" → "get rr:area" */
const CACHE_KEY = /\b(rr:[a-z]+)(?::[^\s"]*)?/g;

After it deployed, I planned a fresh walk on the live site and opened its trace. The weather span now reads GET https://api.open-meteo.com/v1/forecast, the rate limiter's span reads incr rr:rl, and there isn't a coordinate or an IP anywhere in it. The spans sent before the fix will age out with Sentry's retention.

Things that went wrong

Gemma sent people into bins. It suggested checking bins for bottles. In Germany, people leave bottles on a Pfandring for those who collect deposits for a living. leaveBins drops any sentence about bins unless it says to leave them alone.
Titles like "Park Waste Collection" and "Eyre Square Park Run". A title now has to name a real place on the route, and "run" becomes "loop".
"Based on the image, I have identified 7 containers." The narration is stripped before the voucher shows Gemma's notes.
Cities that map every bin ranked "Bins (4)" as their best stop. Street furniture is now capped, and bins only count inside a park.
Two stops called "Pitch, Wildflower Meadow". Look-alikes are now "east end" and "west end", and the briefing never says the same park twice.
Map markers drifted 30, 60 and 90 pixels down the page. Setting position on a custom MapLibre marker overrides its own positioning. Don't.
A school outline cut off at a tile edge let pitches inside school grounds through (above).
My privacy block had gaps (above).
Gemma 4 E4B overcounts busy hauls by about one. The voucher shows every item, so you can correct it before it counts.

Why Does Open Innovation Matter?

When the payout is 15 cents a can, the AI has to cost nothing. A walk that earns €0.30 can't pay for API calls. On a laptop, Gemma costs nothing per plan and nothing per photo, so the maths of the whole idea only works with an open model.

Your photo doesn't have to leave your device. On the laptop tier, the haul photo is read by Gemma on your own machine. The phone tier is built to do the same in the browser, though I haven't tested it on a phone yet. Your walk history stays in your browser too: there are no accounts. A walk history is a map of where you live and when you're out. It shouldn't sit on someone else's server, and after this week, it doesn't sit in my Sentry either.

I could build a box around the model. Gemma runs inside my own pipeline, so every output passes through code I wrote and tested before anyone sees it. The same family runs at three sizes in three places, so I wrote the prompts and the guard once, and Sentry tells me which size breaks which rule.

It's open all the way down. Map data from OpenStreetMap, tiles from OpenFreeMap, walking routes from Valhalla, weather from Open-Meteo, the workflow on Mastra, the phone model on transformers.js. None of them needs a key. The only part that does is the optional cloud tier.

Where a closed model might do better: reading small logos on crumpled cans in a bag. I haven't tested one, so I can't say it would. Both Gemma sizes I tried missed the marks on my real haul, and the honest fix so far is a better photo, not a bigger model.

What it can't do yet

The hotspot scores are educated guesses. They're based on what tends to attract drinkers (benches, pitches, off-licences), and my one real walk says roadsides beat parks.
Reading deposit marks from a bag photo is unreliable. Close up, labels up, it works. From above, in a bag, it doesn't.
The phone tier is untested on a real phone.
Europe only: 19 schemes. The UK's starts in October 2027. US states with bottle bills aren't in yet.
Free hosting: the first plan after a quiet spell waits about 50 seconds for Render to wake up.

My Agent Session

I built Return Route with Claude Code over three days, across five sessions: from reading this challenge, through the brain dump that became the PRD, the redesign, the Render outage, the videos, to the fixes in this post. This is a curated version: my prompts trimmed, Claude's turns summarised, and the tool calls real.

Building Return Route with Claude Code: from a brain dump to a €0.30 voucher

You

Look into the Week 1 challenge, and get back to me when you have understood it. I am thinking of an idea meanwhile.

Agent

Read the Week 1 brief. Touch Grass: build something with open-source AI at its core that gets people off the screen and into the world, and make the screen the shortest part of it. Submissions close Sun 11 Oct, 23:59 PDT. Writing quality is weighted most, taking it outside earns bonus points, and you can win only one prize category.

▸ get_challenges DEV challenges

Input

DEV challenges

Output

Hacktoberfest Open-Source AI Challenge: Week 1, 5 to 11 Oct. Featured: Render, TabPFN, Tinker, Arduino, DigitalOcean, Gemma. Partner: Mastra, Sentry Agent Tracing and 8 more.

You

Here's my unedited brain dump. Categorize it into a PRD and tell me how the plan looks for the vision I have in mind. The persona is a student, an early-career person or just a young adult, who likes to walk around and explore the city but would also like a bit more change in their pocket. One easy way to get extra coins is collecting cans and bottles and sending them into the return machine. This is inspired by a story of a person in Germany who picked up about 2,000 bottles, turned them in for 500 euro and bought a PS5. Can my app give people a good, predictable path around parks and the usual hotspots where they can pick up cans and litter? Focus on Ireland, because that's where I know the return scheme works, and other European countries with a scheme, plus the UK.

Agent

Wrote the PRD for "Return Route": say how long you've got, get a loop through likely hotspots that ends at a return machine, with an honest € range, then put the phone away. Checking the facts changed the plan: the UK scheme only starts in October 2027, so v1 is Ireland plus other live European schemes. The PS5 story is a viral 9GAG post with no outside confirmation, so the post should call it unverified. Re-turn pays 15c up to 500 ml and 25c above, only for cans and PET bottles with the logo, and the machines refuse crushed ones. Other Week 1 entries are already walk planners, so the edge is the money.

▸ WebSearch Germany man collected 2000 bottles Pfand bought PS5

Input

Germany man collected 2000 bottles Pfand bought PS5

Output

Only the viral post itself; treat it as an unconfirmed viral story.

▸ WebSearch UK deposit return scheme launch date England Scotland 2027

Input

UK deposit return scheme launch date England Scotland 2027

Output

October 2027, 20p per container.

▸ search_dev_to_semantic walking route planner with OpenStreetMap and open source routing

Input

walking route planner with OpenStreetMap and open source routing

Output

Paper Walk and other Week 1 walk planners.

You

I like everything. Can we run a small-weight model locally, for an edge AI use case? If so, let's build that, as well as cloud Google AI Studio. Scope: Ireland and other European countries with a return scheme. Donate mode: keep it in v1. Solo. Keep this project polished and ambitious, we need to win.

Agent

Built the MVP with Gemma in three places: E2B in the browser on WebGPU through transformers.js, E4B through Ollama, and 26B-A4B through AI Studio, with a Mastra planner and a deposit table for 19 European schemes. The rule from day one: Gemma picks stops from a list of real places and explains them; code drops invented stops, trims long routes, composes the spoken place names and prices everything, and stripMoney removes any amount Gemma writes. Public Overpass servers kept failing, so Galway ships as a saved OpenStreetMap snapshot. The phone tier builds but hasn't run on a phone.

▸ Bash Fetch and save Galway OSM snapshot

Input

$ Fetch and save Galway OSM snapshot

Output

Overpass unavailable: overpass.private.coffee → 500 (4 attempts)

▸ Bash Retry Galway snapshot with new mirrors

Input

$ Retry Galway snapshot with new mirrors

Output

galway: 536 features, 210 sources, 25 parks, 19 return points (4 mapped machines)

▸ Bash Test cloud Gemma tier from Terryland

Input

$ Test cloud Gemma tier from Terryland

Output

→ Aldi return machine 4.06 km, €0.88 to €3.15

▸ Bash Run unit tests

Input

$ Run unit tests

Output

Tests 25 passed (25)

You

Pushed to GitHub, add the render.yaml file so I can deploy. Once that's done, we need to rework the UI/UX using the taste skill and other stuff, because this is currently very AI slop.

Agent

Added a render.yaml Blueprint and redesigned around two objects from the story: an Irish waymarked trail post and a return machine's voucher. The start screen is a fingerpost with three yellow signs (30 min, 1 hour, 90 min). The route is a yellow trail with diamond waymarks. The haul prints as an itemised thermal voucher with crushed or unmarked items struck through. Off-black, paper white, one waymark yellow, Archivo condensed for signs and IBM Plex Mono for the voucher, in light and dark.

You

Here's my feedback. The app is perfect for anyone that knows what the app is, however when sharing with an audience it doesn't say much to help a new user. I would like a first-time user pop-up referencing the 9GAG story and how the app works. The Gemma · Cloud button doesn't look like a button, so the local option is quite slept on. Donate the refund does nothing: what does it actually do? Maybe a toggle that changes the UI into something more motivating, like walking for a cause, and helps you write a quick tweet. And the note button doesn't say that's how you customise your walk.

Agent

Added a welcome pop-up (the 9GAG story, three steps, where Gemma runs), turned the Gemma switch into a real control with a border and caret, renamed the note to "Customise this walk: your own time or direction", and sketched a cause mode for Donate.

You

I want you to open and audit, then tell me potential fixes and recommendations.

Agent

Ran the app at desktop and phone width, light and dark, and planned a real hour from Terryland on local Gemma. Worst bug: map markers for stops 2, 3 and € were drawn 30, 60 and 90 px below their real positions, because an inline position:relative on each marker overrode MapLibre's own positioning. Also found: Gemma suggesting people look in bins, generic titles like "Park Waste Collection", lowercased place names, a theme flash on reload and a sideways page jump.

You

Apply all, plus recommendations. Regarding Donate mode, I want the UI to have a different colour panel and an experience that makes people feel good about themselves. Also, since this app will be demoed for the competition, can we have the whole workflow demoed, from plotting to scanning and everything?

Agent

Walk for a cause turns the whole app green, names the cause, counts what you've given, and ends on a thank-you screen with a post: Gemma writes only the opening line, and guardPostLine strips numbers, money and hashtags so the count and amount come from the voucher. The guided demo at /?demo runs the whole flow in 8 steps with live Gemma, never touches real totals, and falls back to a labelled recorded plan if Gemma can't be reached. leaveBins now drops any sentence about bins unless it says to leave them alone.

▸ Bash Typecheck, lint, tests, production build

Input

$ Typecheck, lint, tests, production build

Output

Tests 33 passed (33); build succeeded

You

What partner technologies are we using? I'm seeing how we can use niche technologies to increase our chances of winning a prize, as well as tune our model and look for room to improve. I just read the past weekend's overall winning write-up, and now I'm thinking how we can go an extra mile while keeping the app as simple as it is.

Agent

Made planning a Mastra workflow (place → map ‖ weather ‖ events → assemble → pick → route) that stops early with a plain message where no scheme exists. Added Sentry: a span per step, so the parallel fetches visibly overlap, gen_ai spans per Gemma call with model, tier and tokens, and one issue per guard rule tagged with tier and model, with no prompts, coordinates or photos sent. SerpApi was dropped because the free plan lacks the Google Events engine. Then moved planning problems into code: for every possible finish, code works out which stops fit, a named shop becomes the finish, and look-alike stops get distinct names.

▸ Bash pnpm eval:plan, 8 Galway walks per tier, before and after

Input

$ pnpm eval:plan, 8 Galway walks per tier, before and after

Output

Cloud 26B: untouched by the guard 7/8 → 8/8, too long 1 → 0, finish honoured 4/5 → 5/5. Local E4B: 6/8 → 7/8, 2 → 0, 4/5 → 5/5

You

The app isn't working in the cloud, check what's wrong.

Agent

The Sentry issue showed every Overpass mirror refusing the Render server, plus 429s from the place lookup and the weather service. Render's free tier sends traffic from IPs shared with thousands of apps, and public map servers rate-limit them; a laptop never sees it. Map data now comes from OpenFreeMap's vector tiles on a CDN, with Key Value cache, snapshots, full Overpass and the walker's own browser as fallbacks. Plans now work anywhere in Europe.

▸ Bash Time a 30-minute area from tiles in five cities

Input

$ Time a 30-minute area from tiles in five cities

Output

Galway, Berlin, Copenhagen, Amsterdam, Vienna: about 1 to 2 s each

You

I am back from the walk, I have added video from my walk and some photos. I want you to make 2 videos: one an interesting punchy reel with captions and motion graphics, and a full comprehensive video of the walk and the app. In the photos there is my haul; use that photo in the actual demo. The cans were recyclable, so I got the money back: make sure the demo returns €0.30.

Agent

Live reads of the real bag photo by both E4B and 26B came to €0.00: from above, the Re-turn logos are too small to confirm. So the demo shows the reading checked against the Lidl voucher (2 cans at 15c, €0.30) and says where it came from, while a photo taken in the demo still goes to Gemma live. Made both videos in Remotion: a 65-second reel and an 11:54 full walk with chapters. Captions come from a transcript of the audio, and where a figure was unclear the caption says "…" rather than putting words in your mouth.

You

Look at the winning write-ups from the past weekend challenge so we get an idea of good practice, then craft our write-up with all the good elements. Also give me honest feedback on the project. Don't worry about the deadline, worry about quality, polish and relevance.

Agent

Read the overall, Gemma, Render, Mastra and Sentry winners. What they share: a real opening scene, failures shown and kept in the numbers, code owning the risky parts, partner sections backed by screenshots, and a "where closed would do better" paragraph. Drafted the post around the irony of an hour's walk for €0.30. Honest feedback included: the phone tier is untested, the hotspot priors didn't hold up on the one real walk (the park was clean, the cans were in hedges), and one stop sat behind a college fence.

▸ get_article_content Congrats to the Hacktoberfest Weekend Challenge: Build for a Friend Winners

Input

Congrats to the Hacktoberfest Weekend Challenge: Build for a Friend Winners

Output

Overall: Before I Call. Gemma: Kitchen Table. Render: Tala. Mastra: Prep Buddy. Sentry: Actually.

You

We can fix the private grounds one. The estimate was €1.05 to €3.85, but it's fine: a good indication that our neighbourhood is clean.

Agent

Stops inside school or childcare grounds, and anything tagged access=private, are no longer stops, unless the map marks that pitch as open. University campuses stay, since they're usually open. Overpass now returns school outlines; tiles use OpenMapTiles' landuse school polygons. The tile path still leaked 6 pitches: a place near a tile edge was read from the neighbour tile's margin, where that tile holds only a sliver of the school outline. Each place is now read from the tile it's in. Snapshots refreshed with only removals: east Galway lost 17 pitches and 6 picnic tables, the city 51 school pitches and a school playground. The area cache key was bumped so old areas aren't reused.

▸ Bash Find snapshot stops inside school grounds (east Galway)

Input

$ Find snapshot stops inside school grounds (east Galway)

Output

picnic ×6 and pitch ×4 → Merlin College Secondary School; pitches in 6 more schools

▸ Bash Tiles around Merlin College: places inside school grounds

Input

$ Tiles around Merlin College: places inside school grounds

Output

before the fix: 38 places, 6 inside school grounds; after: 32 places, 0 inside

▸ Bash pnpm test, tsc, lint, build

Input

$ pnpm test, tsc, lint, build

Output

Tests 51 passed (51); build succeeded

Prize Categories

Best Use of Gemma: Gemma 4 is the only model, in three places (26B-A4B through AI Studio, E4B through Ollama, and E2B in the browser on WebGPU, which is built but untested on a phone), with one guard around all of them. Gemma plans the walk, reads the haul photo and drafts the post; code owns the stops and the money. Measured over 8 walks per server tier, before and after, and tested on a real walk that ended in a real voucher.
Best Use of Render: one render.yaml Blueprint runs the app and a Render Key Value cache shared by the map, events and rate limits, deployed on every push. Render's shared outbound IPs taught me how public map servers treat cloud traffic, and the five-step fallback that came out of it makes plans work anywhere in Europe.
Best Use of Mastra: planning is a Mastra workflow, place → map ‖ weather ‖ events → assemble → pick → route, with the map, weather and events steps in parallel. It stops early with a plain message when a country has no scheme, and the phone tier runs its first half on the server and the Gemma step on the phone.
Best Use of Sentry Agent Tracing: each plan is a trace with a span per workflow step and gen_ai agent spans for the planner and the haul reader, with model, tokens and latency, and no prompts. Every guard override is an issue tagged with tier and model. Sentry found the Render outage that local runs never showed, and, while I was writing this post, a privacy hole in my own setup, which is now fixed.

Built solo.

If there's a deposit scheme where you live, take it out for half an hour and tell me in the comments what you found. And if you only find clean parks, that's useful too: it's what the planner needs to learn.

Built with AI assistance (Claude Code). I reviewed, tested and edited everything. The walk, the voucher and the evaluation numbers are real.

Pīzhù 批注: a writing tutor that never rewrites your essay, built for my friend Joy (Gemma 4)

Muhammad Murtuza Hussain — Fri, 02 Oct 2026 17:11:44 +0000

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend

What I Built

My friend Joy is doing an MA in Global Mass Communication in Ireland. Her first language is Mandarin. She reads media theory in two languages, argues well, and still gets essays back with comments like "expression needs work" and "be careful with academic tone".

Me and Joy met at the library of our university, both of us spend most of our day working in the reading room. This one particular afternoon, Joy invited me for a drink break at our student bar, where she also had her informal meeting with her EAP (english for academic purposes) faculty, where they discussed her dissertation, and I noticed how Joy received the feedback from faculty, but couldn't get the reasoning behind it, the faculty all could say was,

It's Just bad english

she said.

This moment had me to tinkering, but also I recalled that, I have seen the same thing with a lot of friends from China and Taiwan. The marks they lose are rarely about ideas. They come from a handful of habits that make perfect sense in Chinese and read badly to a British marker:

No articles. Mandarin has no a or the, so "The society is changing" feels natural.
一逗到底, "one comma all the way". A Chinese sentence can run through commas until the thought is complete. In English that is a comma splice.
Exam-template English. "With the development of society…", "In a word…" were taught as good style for 高考 and IELTS. A UK marker reads them as filler.
Confident claims. "This proves…" and "Everyone knows…" (众所周知) persuade in Chinese argumentative writing. In a UK essay they are unsupported.

The usual tools make this worse. Grammar checkers and chatbots rewrite the paragraph. It sounds fluent, it stops sounding like the student, she learns nothing, and in UK and Irish universities an AI-rewritten essay is an academic-integrity problem.

So I built Pīzhù (批注). The word means margin notes: the comments a good teacher writes beside your work. That is the whole product:

It underlines the exact words a UK marker would pause on.
It explains why, in English and in Chinese (简体 or 繁體), including why a Mandarin speaker tends to write it that way, framed as a habit, never a mistake in thinking.
It gives a hint, and at most a tiny nudge of a few words.
It never rewrites. Joy makes every change herself.

Demo

Try it: pizhu.onrender.com. Press Try a sample, then Check my writing. The sample essay is one I wrote for testing; it is full of these habits and includes one reference I invented on purpose, so you can watch the reference checker catch it. (The demo runs on Render's free tier, so the very first load can take a few seconds to wake up.)

The essay on grid paper, with notes in the margin. Every note sits beside its own line, and the open one draws an ink line to its words.

Lesson mode. One note at a time, with tapioca pearls as progress. Enter for "got it", the arrow keys to move.

Back to Word. Students write in Word, and Word comments are literally margin notes, so one click gives Joy her own document back, every word unchanged, with each note as a comment from Mòmo.

Reference check. Google Scholar via SerpApi: three real books found, the invented one flagged.

On a phone, in dark mode, in 简体中文.

Code

Everything is open source (MIT) at github.com/MuhammadMurtuzaHussain/pizhu. If you only read four files, read these:

File	What it does
`src/lib/guard.ts`	The "never rewrite" rule: verbatim spans and a word-level edit budget for nudges
`src/mastra/agents/prompts.ts`	The tutor brief: twelve Mandarin-to-English habits and the checklist Gemma follows
`src/mastra/workflows/references.ts`	The reference check: Gemma extracts, code matches, SerpApi verifies
`src/components/MarginPaper.tsx`	Margin notes positioned beside each line, with the ink connector

Run it privately on your own laptop in three commands:

ollama pull gemma4:e4b
git clone https://github.com/MuhammadMurtuzaHussain/pizhu && cd pizhu && pnpm install
pnpm dev   # http://localhost:3000

MuhammadMurtuzaHussain / pizhu

Margin notes, not rewrites. An open-source writing tutor for Mandarin-speaking students at UK and Irish universities, powered by open-weight Gemma 4

Live demo · DEV post · Run locally · Built for the DEV Hacktoberfest Weekend Challenge

Why

My friend Joy is doing an MA in Global Mass Communication in an Irish University. Her ideas are sharp; her marks lose points to a small set of habits that make perfect sense in Chinese and read badly to a British marker: no articles (中文没有冠词), comma splices (一逗到底), exam-template phrases ("With the development of society…"), and confident claims (众所周知).

Grammar tools and chatbots rewrite the paragraph. It sounds fluent, it stops sounding like her, she learns nothing, and in an Irish university it is an academic-integrity risk.

Pīzhù does what a good tutor does in the margin: it points at the exact words, explains why in English and Chinese (简体 or…

View on GitHub

How I Built It

Gemma 4 is the only model in Pīzhù. It is open weights under Apache 2.0, and the same family runs in two places:

Where	Model	Why
Joy's laptop (the default)	`gemma4:e4b` or `gemma4:12b` via Ollama	Her coursework never leaves her machine
Hosted demo	`gemma-4-26b-a4b-it` via Google AI Studio	So anyone can try it without installing anything

One environment variable switches between them.

Next.js UI ──► /api/analyze  (streams one paragraph at a time)
                 │
                 ▼
          Mastra tutorAgent ──► Gemma 4  (structured output, Zod schema)
                 │
                 ▼
          guard.ts  ← the "never rewrite" rule, enforced in code
                 │
                 ▼
          + rule-based British spelling  →  margin notes

Reference tab ──► Mastra workflow:
          extract (Gemma) → match citations (code) → verify (SerpApi Google Scholar)

1. Teaching Gemma to annotate instead of rewrite

The tutor is a Mastra agent with a system prompt written like a brief for a university writing-centre tutor. It describes twelve habits, each pairing a UK convention with the Mandarin pattern behind it, and gives Gemma a checklist: check every comma, every "As for…", every bare countable noun.

Gemma returns structured JSON validated with Zod. The schema has no field for a rewritten paragraph. The only text Gemma may propose is an optional nudge.

2. Not trusting the prompt

Prompts are requests, not guarantees. guard.ts checks every note before Joy sees it:

The highlighted span must exist in her text (tolerating curly quotes and spacing). If Gemma "quotes" something she never wrote, the note is dropped.
A nudge may change at most max(4, 30%) of the span's words, measured by word-level edit distance. Anything bigger is stripped back to a hint, and the card says "Try this one yourself."
Spans that cross a sentence boundary never get a nudge. Restructuring is the student's job.

export function nudgeAllowed(span: string, nudge: string): boolean {
  if (!nudge.trim() || nudge.trim() === span.trim()) return false;
  if (words(span).length > 25) return false;
  if (crossesSentence(span)) return false;
  return wordEditDistance(span, nudge) <= Math.max(4, Math.ceil(words(span).length * 0.3));
}

Across my evaluation runs, Gemma proposed 89 nudges and the guard turned 8 of them back into hints. Most came from the smallest model, which is exactly where you want the safety net.

3. Rules for what rules do best

The small model was unreliable at spotting American spellings, so I stopped asking it. A word list catches analyze → analyse and behavior → behaviour every time, and those notes merge with Gemma's. Gemma handles the judgement; the rules handle the lookups.

4. Checking references with SerpApi

Fabricated or garbled references are a growing problem, so the reference tab runs a three-step Mastra workflow:

Gemma extracts each entry (authors, year, title) and offers Harvard formatting hints, never a corrected entry.
Plain code matches in-text citations like (Hall, 1980) against the list: cited but missing, or listed but never cited.
SerpApi's Google Scholar engine looks up every title: ✅ found, ≈ details differ, or ❓ couldn't find it, so check it exists.

Two real-world snags made it better. Scholar often drops subtitles ("Understanding media" for Understanding Media: The Extensions of Man), and its top hit is sometimes a book review rather than the book. Pīzhù compares main titles, searches with Scholar's author: operator first, and accepts a one-year drift for reprints. Only titles and first authors are sent, never essay text.

5. Designed for Joy, not for a generic user

This is where I spent the second half of the weekend, because a tool you feel judged by is a tool you stop opening.

Mòmo 墨墨, the ink panda. Black and white is literally 墨 ink on paper. Pandas are loved in both mainland China and Taiwan, and a gentle mascot takes the sting out of being corrected. Mòmo reads with you, sips bubble tea, cheers when you fix things, and presses a 好 seal when you finish. A reduplicated name like 墨墨 feels affectionate, the way 团团圆圆 does.
A bubble-tea palette. Taro purple, milk white, strawberry for must-fix, mango for worth-fixing, matcha for all good. Red is the colour of luck and celebration in Chinese culture, so errors are a soft strawberry, never alarm red.
Feedback that protects 面子 (face). Notes are private, never graded, and called habits. The "Marker's eye" summary under each paragraph uses UK marking dimensions (argument, structure, language, referencing) and never gives a mark.
集章, collecting stamps. Anyone who grew up with 7-Eleven point cards or station stamp books knows the pull. Work through three notes of a habit and you earn its stamp.
Handwriting-style Chinese. Explanations are set in 霞鹜文楷 (LXGW WenKai), an open-source kai typeface many Chinese and Taiwanese students already love, so they read like a teacher's note.
The interface in 简体 and 繁體, with explanations in English, Chinese or both.

Why Does Open Innovation Matter?

This project only makes sense with open models.

1. Privacy and academic integrity. Pasting unsubmitted coursework into a third-party chatbot means handing it to a server you do not control, and universities increasingly tell students to be careful with exactly that. With Gemma in Ollama, Joy's drafts stay on her laptop, and the app says so in plain words: 🔒 Local. Your essay stays on this laptop.

2. Control over behaviour. Closed chat products are built to produce the answer. I needed the opposite: a model that points and explains but does not fix. With open weights inside my own pipeline, I could enforce that rule in code instead of hoping a prompt holds.

3. Being able to swap models, and measure it. I wrote fifteen test paragraphs seeded with known habits, plus two clean ones to catch over-flagging, and ran the same pipeline on three sizes of Gemma:

Model (where it runs)	Recall on seeded habits	Must-fix notes on clean paragraphs	Seconds per paragraph
Gemma 4 E4B (laptop, 16 GB)	84.2%	1	12.8
Gemma 4 12B (laptop, 16 GB)	94.7%	0	34.1
Gemma 4 26B-A4B (AI Studio)	89.5%	0	25.4

Joy can choose her trade-off: E4B for quick checks while drafting, 12B before she submits. Tuning the hosted model taught me something too: Gemma 4 "thinks" at length by default, and one paragraph took 335 seconds. Setting the thinking level to minimal brought it to about 30 seconds with no visible loss in quality.

4. Cost. Running locally costs nothing. International students already pay some of the highest fees in UK higher education; a tool behind a subscription is a tool many of them will not use.

Handing it to Joy

I sent Joy the link on WeChat with a slightly nervous "i made this app for u". She didn't test it on my sample essay. She tested it on what she is actually writing right now, her dissertation, and later sent back a review I could not have scripted.

What worked for her:

The general feeling of this app: it's very useful, especially for our module assignments. The Chinese explanation is easier to understand than the criteria written in our module 😂

Another advantage of it is that it explains why I should correct my sentence. As grammarly could only give me a red label but sometimes I don't know that's the problem and how to fix it. The explanation really helps me to understand how to write properly.

That second message is the reason Pīzhù exists, put better than I managed: a red underline tells you that something is wrong, and Joy needed to know why. It is the same gap as "It's just bad English".

She was just as honest about what didn't work:

As my dissertation is a long paper, when I tried to ask advice from momo, I have to send my paper separately, even need to split each chapter to 2-3 parts. Thus, momo cannot get the full understanding of my argument. If the app could do longer articles, it would be great!

(She calls it "momo". That made my day.)

And she had two requests:

Another advice I would like to share it that, if it could help you analyse the assignment requirements or criteria, and have similarity detection like turntin, it will help students understand how to do their assignments and worry less before submitting.

What I shipped the same evening

Longer papers. The hosted demo now accepts 6,000 words instead of 1,500. The cap only exists because the demo runs on free tiers; running Pīzhù locally has no limit at all.
A whole-paper overview. Mòmo now reads the entire paper in one pass, alongside the line-by-line notes, and tells you what it thinks your argument is, what works, and the three most important whole-paper fixes. If Mòmo's summary of your argument isn't what you meant, that is the most useful feedback of all.
Your assignment brief, explained. Paste the task and the marking criteria, and Mòmo restates each criterion in plain English and Chinese, then marks it met, partly or missing against your paper. Joy's line about the Chinese being easier than her module criteria was the whole spec.
It travels. The overview sits at the top of the Word export, above her own unchanged text.

Turnitin-style similarity checking is the one request I'm deliberately not building. It only works by comparing your essay against a database of other people's papers, which means uploading and keeping your writing: exactly what Pīzhù is designed never to do. It does the honest half of that job instead: it flags claims that need a citation and checks that every reference actually exists.

Her last message: "No problem, it's already a brilliant app!" I've promised her half the prize if it wins.

My Agent Session

I built Pīzhù with Claude Code over the weekend, from reading the challenge rules, to the PRD, to debugging the reference matcher and the margin-note layout:

Building Pīzhù 批注 with Claude Code: a margin-note writing tutor on Gemma 4

You

Today's Hacktoberfest challenge is Build for a Friend. My idea: a tool that helps Mandarin-native students write better academic English (EAP). Lots of my friends from China and Taiwan lose marks and confidence when they're so smart. I do NOT want the model to rewrite their work, just tell them where the English is off and why. Focus on UK and Irish academic writing, UI relevant to Mandarin speakers, with a Chinese UI option. Plan it against the submission template and partners, build a PRD, and ask me questions.

Agent

Read the challenge rules (deadline 5 Oct 06:59 UTC; writing quality weighted most) and checked partner tech. Gemma 4 is open-weight under Apache 2.0, multilingual and runs locally, so it is the core model; Tinker can't fine-tune Gemma, so I left it out. Asked four questions: the friend, where Gemma runs, partner categories, and stack.

▸ get_challenges DEV challenges

Input

DEV challenges

Output

Hacktoberfest Weekend Challenge: Build for a Friend, 2-5 Oct

▸ WebSearch latest Gemma open model release 2026 Ollama sizes

Input

latest Gemma open model release 2026 Ollama sizes

Output

Gemma 4: E2B, E4B, 12B, 26B A4B, 31B

You

Named friend who will test (Joy, Global Mass Communication, Simplified Chinese). Hybrid inference. Gemma with SerpApi. TypeScript: Next.js + Mastra. 16 GB RAM.

Agent

Wrote the PRD: 'annotate, don't rewrite'. Built a Mastra tutor agent with a Zod schema that has no field for a rewritten paragraph, plus guard.ts: every span must exist verbatim in the student's text, and any nudge changing more than max(4, 30%) of the words is stripped back to a hint. First local run on gemma4:e4b: six notes on paragraph 1 with natural Chinese explanations, one oversized fix stripped by the guard.

▸ Bash Smoke-test paragraph analysis with local Gemma

Input

$ Smoke-test paragraph analysis with local Gemma

Output

6 annotations, nudgesStripped: 1

▸ Bash Write and run unit tests for guard and citations

Input

$ Write and run unit tests for guard and citations

Output

14 passed

Agent

Wrote 15 hand-made test paragraphs seeded with Mandarin-L1 habits plus 2 clean ones. E4B recall 73.7%, weakest on American spellings and missing citations. Added a deterministic US→UK spelling list (rules for lookups, Gemma for judgement) and a sharper checklist: recall rose to 84.2%. 12B: 94.7% with zero false must-fix notes.

▸ Bash Run eval fixtures on Gemma 4 E4B

Input

$ Run eval fixtures on Gemma 4 E4B

Output

recall 0.737

▸ Bash Eval Gemma 12B then re-eval E4B

Input

$ Eval Gemma 12B then re-eval E4B

Output

12B 0.947, E4B 0.842

Agent

Hosted path: one paragraph took 335 s on Gemma 4 31B because it thinks at length. Probed the API: 31B was returning 500s, and 26B-A4B with thinkingLevel 'minimal' answered in ~7 s. Switched the hosted demo to 26B-A4B; paragraphs now take ~30 s with no visible quality loss (89.5% recall).

▸ Bash Compare latency of Gemma 26B MoE vs 31B

Input

$ Compare latency of Gemma 26B MoE vs 31B

Output

26b-a4b minimal: 6.7s; default: 28.4s

Agent

Reference checker as a Mastra workflow: Gemma extracts entries, plain code matches in-text citations, SerpApi Google Scholar verifies. Two real snags fixed: Scholar drops subtitles ('Understanding media'), and its top hit is sometimes a book review. Compare main titles, search with author: first, allow ±1 year for reprints. Result: three real books found, the invented one flagged.

▸ Bash Run reference check twice for stability

Input

$ Run reference check twice for stability

Output

found, found, found, not_found

You

Deploy failed (Render: EROFS read-only file system, unlink /usr/bin/pnpm).

Agent

corepack enable tries to write a pnpm link into Render's read-only /usr/bin. Switched render.yaml to corepack pnpm install/build/start, verified a local production build, pushed. It went live at pizhu.onrender.com.

You

Load the design skills we used for my website and enhance the UI/UX and colours. It's for a Chinese audience, so maybe a dragon or panda avatar, chosen by the consumer psychology of Chinese and Taiwanese students.

Agent

Recommended 墨墨 Mòmo, an ink panda: black and white is literally ink on paper, pandas are loved in both the PRC and Taiwan, and a dragon reads as authority, intimidating for something that corrects you. Design principles: protect 面子 (private, never graded, 'habits' not errors), 萌 mascot culture, 集章 stamp collecting, and 霞鹜文楷 for Chinese so notes read like a teacher's handwriting.

You

It's still lackluster, and the palette looks like the Claude colour scheme. Can we think of something much more?

Agent

Offered four palette worlds; you chose 珍奶 taro & boba, plus all four signature features. Built: a live demo hero (sentence types in, underlines draw, notes pop in); true margin notes positioned beside each line with an ink connector; lesson mode with tapioca-pearl progress and a share card; and a Mòmo companion dock that narrates, cheers and stamps 好.

▸ Write src/components/MarginPaper.tsx

Input

src/components/MarginPaper.tsx

Output

▸ Write src/components/LessonMode.tsx

Input

src/components/LessonMode.tsx

Output

You

Add a light/dark toggle. Bug: the line from words to note stays while I edit a paragraph. The hero demo grows and shrinks so the page jumps. Export my habits gives JSON, improve it. Credit the challenge and me in the footer. Make this a great finished product that would make us win!

Agent

Fixed all five, each verified in the browser: the toggle applies before first paint; editing hides that paragraph's notes and connector; the demo card reserves its final size (height constant across a full loop); a habit-report image and 集章 stamp book replace raw JSON; and the footer has credits. Extras: Word export with notes as real Word comments, friendly errors with retry, draft autosave, WCAG contrast fixes, OG card. A headless-Chrome script ran the whole flow on the live site and captured the README screenshots.

▸ Bash Capture production screenshots and demo GIF

Input

$ Capture production screenshots and demo GIF

Output

analysis done in 84.7s; all scenes captured

▸ Bash Final checks

Input

$ Final checks

Output

lint clean, 19 tests passed

Prize Categories

Best Use of Gemma: Gemma 4 is the only model, running locally (E4B and 12B via Ollama) and hosted (26B-A4B via AI Studio), with a measured size comparison and a guardrail built around its structured output.
Best Use of SerpApi: the Google Scholar engine powers the reference checker that catches sources which may not exist, using the author: operator to find the work itself rather than reviews of it.

Built with AI assistance (Claude Code). I reviewed, tested and edited everything, and the evaluation numbers come from real runs of the code in the repo.

Any Feedbacks on this?

Muhammad Murtuza Hussain — Fri, 02 Oct 2026 12:38:52 +0000

https://pizhu.onrender.com/

I have made this for the weekend 1 challenge, looking for UI/UX improvement.

> Recommend me skills below!

Cool social media

Muhammad Murtuza Hussain — Thu, 01 Oct 2026 12:53:27 +0000

How do you make friends here?