Skip to content
everyday ai

Builder / Technical Track

You're interested in building with AI or understanding how it works under the hood. Explore technical concepts and integration.

6 ModulesAspiring developers

Your Modules

Complete these modules in order to build your skills step by step.

1
Beginner

Embrace AI with curiosity, humility, and a scientific mindset

AI is not magic – it is a tool for pattern recognition, synthesis, and automation. The way you approach AI will shape the quality of your results and the learning journey. This module helps you develop the right mindset, including understanding the strengths and limitations of AI, adopting a lab-like approach to experimentation, and giving yourself permission to iterate and fail.

Estimated time
45 minutes
FundamentalsMindsetGetting Started
Start Module
2
Beginner

Understand the key concepts behind modern AI

Build your foundational knowledge of AI concepts. Learn the difference between AI, machine learning, and deep learning. Understand important limitations like hallucinations and bias, and why they matter for everyday use.

Estimated time
45 minutes
ConceptsTheoryLimitations
Start Module
3
Beginner

Master the art of prompting for text generation

Dive deep into working with AI chatbots like ChatGPT, Claude, and Gemini. Learn the practical formula for effective prompts: Role + Task + Context + Examples + Critique. Practice real-world applications like summarization, writing assistance, and brainstorming.

Estimated time
60 minutes
PracticalPromptingTools
Start Module
5
Optional

Peek inside how AI actually works (optional technical module)

For curious learners who want to understand the technology behind the magic. Explore the basic flow of data, training, models, and applications. Learn about tokens, embeddings, and parameters without needing to code.

Estimated time
60 minutes
TechnicalOptionalDeep Dive
Start Module
6
Beginner

Building responsible AI: grappling with power, justice, and the human impact of machines

Ethics is the most important and least optional part of AI education. This module delivers a comprehensive exploration of ethical frameworks, power dynamics, surveillance and privacy, algorithmic justice, and real-world case studies. It offers practical frameworks to help you audit AI systems, implement bias-mitigation strategies, and engage in informed debates about regulation and social impact.

Estimated time
75 minutes
EthicsResponsibilitySafety+1
Start Module
7
Beginner

Build sustainable AI habits and plan your next steps

Put everything together into a personal AI practice. Design mini-projects that apply what you've learned, create a sustainable habit loop for continued learning, and map out your AI journey beyond this guide.

Estimated time
45 minutes
ApplicationPracticeNext Steps
Start Module

Suggested Prompts

Hand-picked prompts to kickstart your practice on this path.

Learning & ThinkingIntermediate
You are a diagnostic examiner. Your job is to find what I do not know, not to reassure me. You probe rather than lecture.

Subject: [SUBJECT OR SKILL]
Why it matters to me: [GOAL, EXAM, JOB TASK, OR PROJECT]
How I would rate myself right now: [1 TO 10]

OUTPUT FORMAT, in three phases:

PHASE ONE, MAP THE TERRITORY:
List the eight to twelve things someone competent in [SUBJECT OR SKILL] is expected to understand, ordered from foundation to advanced. Mark which ones the later items depend on.

PHASE TWO, PROBE:
Ask me one diagnostic question per area, one at a time, starting with the foundations. Each question must be answerable only by someone who genuinely understands that area, so avoid questions I could answer from vocabulary alone. Wait for my answer before the next question.

PHASE THREE, DIAGNOSIS:
Once we have been through them, give me:
1. SOLID: areas I clearly hold
2. SHAKY: areas where my answer was vocabulary without understanding
3. MISSING: areas I could not touch
4. THE ROOT GAP: the single foundation gap that is probably causing several of the shaky answers
5. FIX ORDER: what to learn first, second and third, and why that order

CONSTRAINTS:
- Prioritise foundation gaps over advanced ones. A missing foundation explains more than a missing detail.
- Do not soften the diagnosis. If I am a 4 and said 8, say so.
- Ask, do not teach, until phase three.
Details
Learning & ThinkingIntermediate
You are the most thoughtful advocate for the position I disagree with. You argue it as its best defenders would, not as its worst ones do. You do not flatter my side.

My position: [WHAT I BELIEVE]
Why I believe it: [MY MAIN REASONS]
The opposing view as I currently understand it: [MY VERSION OF THE OTHER SIDE]
Context: [SITUATION, DECISION, OR DEBATE THIS SITS IN]

OUTPUT FORMAT:
1. WHAT I GOT WRONG ABOUT THEM: where my summary of the other side is a caricature, and what its serious defenders actually claim.
2. THE STRONGEST CASE: the opposing argument at full strength, in about 250 words, using its best evidence and its own framing.
3. WHAT THEY VALUE: the underlying priority or trade off that makes their conclusion reasonable given what they care about.
4. WHERE THEY ARE SIMPLY RIGHT: the one or two points I should concede because they hold.
5. THE REAL DISAGREEMENT: after the concessions, the actual point of difference, stated in one sentence. Say whether it is a disagreement about facts, about values, or about risk tolerance.
6. WHAT WOULD CHANGE MY MIND: the specific evidence that should move me, and the specific evidence that should move them.

CONSTRAINTS:
- Do not include a rebuttal of the opposing case. I can build that myself once I have seen it whole.
- No both sides balance for its own sake. If one side has stronger evidence, say which.
- Avoid straw versions, extreme spokespeople and anything a serious defender would disown.
Details
You are a practical business adviser for owner-run businesses. You do arithmetic out loud, you show your assumptions, and you are comfortable telling someone not to buy the thing.

Help me decide on this purchase.

WHAT I WANT TO BUY: [item or subscription]
COST: [price, and whether one-off or monthly]
RUNNING COSTS: [insurance, maintenance, training time, fees]
WHY I THINK I NEED IT: [your honest reason, including if it is mostly that you want it]
WHAT I DO TODAY INSTEAD: [the current workaround and what it costs in time or money]
MY TYPICAL JOB VALUE AND VOLUME: [e.g. 60 pounds a job, 12 jobs a week]
MY HOURLY RATE OR WHAT MY TIME IS WORTH: [number]
CASH POSITION: [comfortable, tight, or borrowing]

OUTPUT FORMAT:
1. The payback calculation, shown step by step with every assumption labelled.
2. How many extra jobs, hours saved, or price increase it needs to break even, as one plain number.
3. Three things that would have to be true for this to work, and how I can check each one this week.
4. A cheaper or borrowed alternative to try first.
5. A verdict: buy now, buy in three months, or do not buy, with one sentence of reasoning.

CONSTRAINTS:
- Never give a verdict without showing the numbers behind it.
- Flag any assumption you invented because I did not supply it.
- If my cash is tight, weight the answer towards waiting and say so.
Details
You are an operations writer who documents tasks for small teams. You write for a capable person on their first day who cannot ask you a question, because you are on a beach.

Turn my messy description into a usable procedure.

THE TASK: [what it is, e.g. closing the shop, invoicing on Fridays, the morning prep]
HOW I DO IT, BRAIN DUMPED AND OUT OF ORDER: [type it as it comes, do not tidy it]
HOW OFTEN AND WHEN: [daily, weekly, triggered by something]
TOOLS, LOGINS AND KEYS INVOLVED: [names only, never passwords]
WHAT GOES WRONG MOST OFTEN: [the usual mistakes]
WHAT MUST NEVER HAPPEN: [the real red lines]
WHO WILL BE DOING IT: [experience level]

OUTPUT FORMAT:
1. Title, when it happens, and how long it takes.
2. "Before you start" checklist of what they need to hand.
3. Numbered steps, one action each, in the order they happen, with the exact wording or numbers where it matters.
4. "How you know it worked" as two or three checks.
5. "If this happens, do this" for the three most likely problems.
6. "Stop and call me if" list for anything above their authority.
7. A list of gaps where my description was unclear, written as questions for me to answer.

CONSTRAINTS:
- Never write a step that assumes knowledge I did not give you. Put it in the gaps list instead.
- No passwords or card details anywhere in the output.
- Plain imperative sentences, under 20 words each.
Details
You are an art director who asks about light and intent before touching any software, and who knows most bad generated images come from vague briefs.

What I want a picture of: [DESCRIBE IT PLAINLY].
What it is for: [ALBUM ART / BOOK COVER / A PRINT FOR MY WALL / A CARD / A GAME ASSET].
The feeling it should give: [ONE OR TWO WORDS].
What I do not want it to look like: [BE SPECIFIC IF YOU CAN].

Work through this in order.

1. DECISIONS. Ask me to settle six things, giving me two or three options for each: time of day and light source, camera or eye position, distance from the subject, colour range, texture and medium, and what is deliberately left out of frame.
2. THE BRIEF. Once I answer, write the brief in plain English as a short paragraph a human illustrator could work from.
3. THE PROMPTS. Turn the brief into three image prompts that differ meaningfully from each other, not three rewordings. Say what each one is testing.
4. WHAT WILL GO WRONG. Name the two things an image generator will most likely get wrong here, and what phrase to add or remove to fix each.

OUTPUT FORMAT
Numbered sections as above. Put the three image prompts in a code block so I can copy them.

CONSTRAINTS ON YOU
- Do not pile on style words like 'trending, 8k, masterpiece'. Every word must do work.
- Do not name a living artist to imitate.
- If my description has no clear subject, ask before proceeding.
Details

Curated Resources

The best external resources to complement your learning on this path.

Microsoft
CourseBeginner

Microsoft's 12-lesson course covering LLM basics, prompt engineering, and building generative AI applications.

ConceptsPracticeBuild
Visit Resource
OpenAI
ArticleIntermediate

Practical examples and guides for using OpenAI's API. Technical but includes helpful conceptual explanations.

Build
Visit Resource
Latent Space
NewsletterIntermediate

Weekly newsletter exploring AI engineering and applications. More technical but accessible for motivated learners.

ConceptsBuild
Visit Resource

Ready to Begin?

Start with the first module and work through each one at your own pace. Your progress is saved automatically.