Mobile money is a reliability problem
M-Pesa, Airtel Money and Tigo Pesa callbacks can arrive late, twice or not at all. Design reconciliation, idempotency and an audit trail before the happy path.
ADVANCED COURSE · AI-ASSISTED ENGINEERING FOR EAST AFRICAN TEAMS
A free advanced vibe coding course for developers, tech leads and architects in Tanzania, Kenya, Uganda and across East Africa. Build production software with AI — and keep the judgment that makes it safe to ship.
Turn a WhatsApp brief, a donor document or a founder’s idea into testable requirements, explicit non-goals and a risk register.
Ask for plans, assumptions, small diffs, tests, evidence and rollback — instead of accepting the first confident answer.
Field notes on mobile money, low bandwidth, mixed Android devices, multi-currency data and handovers to local IT teams.
THE THREE RULES BEHIND EVERY PROMPT
Across all eighteen modules, the same discipline applies. Keep these three sentences beside you when you open your AI coding tool.
State the rule that must not change. It keeps a refactor from becoming a rewrite and a fix from creating a new bug.
Constrain the diff, name the files in scope, and make larger cleanup a separate, reviewable piece of work.
Demand the failure mode, the evidence you would see, and the test that would catch it before a user does.
THE COURSE PATH · 18 MODULES
Work in order or open the module you need today. Every module ends with a prompt library and a practice task for your own project.
Turn a vague ask into a testable spec, an honest scope, and a decision you can defend.
Choose a design by its trade-offs, failure modes and operating cost — not by confidence.
Constrain the diff, preserve the invariant, and make the agent show its assumptions.
Change the shape of the code without changing what users observe.
Replace guessing with hypotheses, evidence, and the first point of divergence.
Write the tests that would have caught the bug, not tests that confirm the code runs.
Make the agent disagree with you — specifically, with evidence, in priority order.
Measure first, name the bottleneck, and quantify the gain against the risk.
Think like an attacker at the boundary and an on-call engineer at 3 a.m.
Assume the deploy will go wrong; design the detection, the rollback and the blast radius.
Write for the reader who will make the decision or fix the system without you.
Prefer incremental coexistence to a heroic big-bang rewrite.
Design the schema around access patterns, then prove it with the query plan.
Improve every other prompt by changing how you direct the agent.
Ask for states, constraints and accessibility — not “a nice design”.
The questions that prevent systemic regressions after the immediate fix.
Run an audit that produces evidence and a sequenced remediation plan.
Improve a live feature without breaking the users already depending on it.
EAST AFRICA FIELD NOTES
The prompts are universal. The context is not. Each module includes a field note for teams building in Tanzania, Kenya, Uganda and the wider region.
M-Pesa, Airtel Money and Tigo Pesa callbacks can arrive late, twice or not at all. Design reconciliation, idempotency and an audit trail before the happy path.
A 2 GB Android phone on 3G is a real user, not an edge case. Measure payload size, design offline states, and test on the devices your users actually hold.
TZS, KES and UGX do not round the same way, and English or Swahili copy changes layout. Put money in integer minor units and test the longest string.
One maintainer is a bus factor, and the client’s IT officer may run the system after you leave. Write the README, ADR and runbook as deliverables.
THE COMPLETE PROMPT LIBRARY
Find a prompt by the problem you are facing — rollback, N+1, permissions, race condition, migration, empty state — then copy it with one click. No account needed.
VIBE CODING, AI PROMPTS & EAST AFRICA — FAQ
Straight answers about the course, the prompts and using AI coding agents on real projects in Tanzania, Kenya and Uganda.
It is a free advanced course and prompt library for people who build production software with AI coding agents. The playbook contains 18 modules and 392 prompts covering requirements, architecture, implementation, refactoring, debugging, testing, review, performance, security, deployment, documentation, migration, data, UI/UX and agent direction. Every prompt is copy-ready and includes a short explanation of why it works.
Yes. The course, the prompt library and the field notes are free to read and use. You do not need an account to copy a prompt. Your AI tool, model usage, hosting and any paid developer tools have their own costs.
The prompts are written for people who are accountable for real software, so you will get the most from them if you already work with code, APIs, databases or technical projects. If you are starting from zero, begin with our free Vibe Coding course, then come back to this playbook when you have a small project to practise on.
They work with ChatGPT, Claude, Gemini, Cursor, Windsurf, GitHub Copilot, Codex, OpenCode and any other assistant that accepts a text brief. The prompts are tool-neutral: they ask for plans, evidence, diffs and trade-offs rather than relying on one product's features.
The prompt patterns are universal, and each module adds an East African field note. The notes cover mobile money callbacks (M-Pesa, Airtel Money and Tigo Pesa), TZS, KES and UGX amounts, low-bandwidth users, mixed Android devices, WhatsApp-first workflows, multi-tenant data and handovers to local IT teams. They are practical engineering prompts, not legal advice.
Yes. Copy a prompt, replace the [bracketed] slots with your project context, and keep the invariant-and-evidence discipline the playbook teaches. Do not paste client secrets, personal data or production credentials into a tool your client has not approved.
Open any module or the full prompt library, press the Copy prompt button on a card, and paste it into your AI tool. Text in [square brackets] is a slot for your own context. On a module page you can also copy all of that module's prompts at once.
You can take this course online from Dar es Salaam, Nairobi, Kampala or anywhere with a browser. It is self-paced, free and mobile-friendly, so you can read a module, copy a prompt and practise in your own editor without travelling to a bootcamp. The field notes are written for teams working in Tanzania, Kenya, Uganda and the wider East African market.
Yes. It is prompt engineering for software delivery rather than generic chatbot tricks. You will learn how to write prompts that produce specifications, architecture options, small diffs, tests, reviews, runbooks, migrations and security checks — and how to verify the output instead of trusting it.
Ndiyo. Kozi, field notes na prompts zote ni bure kutumia. Huhitaji akaunti ku-copy prompt. Gharama za AI tool, model usage, hosting au zana nyingine za developer zinabaki kwa akaunti yako mwenyewe.
There are 18 modules and about 12 hours of reading and practice. You can work through it in order or use it as a reference during a project. Each module ends with a small practice task you can finish in your own repository.
Continue with Vibe Coding: Build with AI, Think Like an Engineer · Your first steps with AI & prompting · AI ni Nini na Kipato cha Nyumbani · AI kwa Wafanyabiashara Wadogo.
KWA KISWAHILI
Watengenezaji wa programu Tanzania, Kenya na Uganda wanaweza kutumia prompts zote bure. Kama unaanza kutoka sifuri, anza na kozi ya AI ni Nini au kozi ya Vibe Coding, kisha rudi hapa kwa playbook ya ujenzi wa mifumo halisi.