All books | Heidelberg AI Curriculum

Progress is saved in this browser only.

21 books

Foundations & judgement1

T01-L03Build the Smallest Thing Your Colleagues Can Run Without YouA working build for one recurring job (a saved prompt, form, automation or app) with a one-page README, a known-answer test with expected results and a decision paragraph naming two rejected options and a trigger; it passes when your deputy runs the test and one real job from the README alone, without asking you.Builder19 min read

Chat & assistants1

T02-L03Build a Shared Assistant Your Team Can Test and Take OverA shared assistant for one recurring team job, with a usage note, a test set of at least ten known-answer questions and a change log; it passes when your deputy replaces one source, reruns the test set, publishes the new version and a colleague gets the updated answer, all without your help.Builder18 min read

Prompting & context1

T03-L03Put a Test Set Under the Prompt Your Team Depends OnA test folder for one shared prompt: the contract, at least 15 cases with known answers, the Promptfoo configuration with pinned versions, the before-and-after results and a README; it passes when a colleague reruns it from the README alone and gets the same pass or fail on every case.Builder18 min read

Your documents & knowledge1

T04-L03Test and Fix the Document Assistant Your Group Relies OnA test folder for your group's document assistant (test questions with expected passages and answers, the settings record, a before-and-after result for one change, and a README), which passes when a colleague adds or changes one document, reruns the check from the README alone, and gets PASS or explains every failure.Builder22 min read

Automation1

T05-L03Chain Checked Steps Into a Weekly Digest Your Team Can RerunA published n8n pipeline that produces a weekly digest draft for a named reviewer, with a test data table of six to eight cases and their expected end states, the model ID and workflow version in a README, and a note naming maintainer and deputy; it passes when the deputy runs the test set from the README alone and every case ends where the table says.Builder17 min read

Build apps1

T06-L03Turn Your Team App Into One Colleagues Can Depend OnA published Base44 app with two roles, a test copy with known-answer records, a one-page test sheet and an operating note; it passes when a colleague who didn't build it runs the whole test sheet through the testing link and every line matches, and the deputy publishes one small change without your help.Builder20 min read

Agents1

T07-L03Build a Small Agent Your Colleagues Can Run, Test and StopAn agent folder (instructions, permissions file, reference files, test cases with expected results, check script, README naming maintainer and deputy) that a colleague clones and runs; it passes when their check run prints PASS, nothing outside the output folder changed, and they produce one real draft from the README without asking you.Builder20 min read

Write code1

T08-L03Write the Spec First, So an AI Assistant Can Change Code Your Team Depends OnA repository with SPEC.md, known-answer tests, the changed script, CHANGES.md and a version tag; it passes when a colleague, on their own computer and using only the README, runs the tests and all pass, and can point to the rule in SPEC.md behind every changed block of code.Builder24 min read

Create media1

T09-L03Build a Caption Pipeline Your Team Can Rerun Every WeekA pipeline folder (script, settings, glossary, manifest, test recordings with known transcripts, check script, README) plus one week of reviewed captions; it passes when the deputy runs the check and one week's recordings on their own computer from the README alone, the check passes, and every published caption file has a named reviewer.Builder20 min read

Data & analysis1

T10-L03Build an Analysis Your Colleague Can Rerun and Get the Same NumbersA Git repository with the analysis script, settings per month, a lockfile, a sample with a hand-checked expected summary, a check script and a README; it passes when a colleague clones it on their own computer, the check prints PASS, and their rerun of one real month gives a summary identical to yours.Builder20 min read

Run your own AI1

T11-L03Local AI Apps Your Colleagues Can Rely OnA one-page run note for one app (what it produces, who reads it, how to start, stop, back up and restore it, and what happens when it fails), plus a restore of your latest backup on a second computer; it passes when a colleague follows the note without your help and the restored app shows your real data.Builder24 min read

Security, privacy & governance1

T12-L03Give an Unattended Workflow Limits and a Stop a Colleague Can UseA published n8n workflow with its one-page operating rule and a filled-in test sheet for the five tests. It passes when all five tests pass, the credential can't perform any action the rule forbids, and the deputy stops the workflow from the rule alone while you watch without helping.Builder22 min read

Adoption & enablement1

T13-L03Write a One-Page AI Rule Your Team Can Use Without Asking YouA one-page AI working rule, approved by the person accountable for the team, with its eight test cards and the results of three colleagues who didn't write it. It passes when every red card is stopped, each tester gets at least seven of eight right, the edge-case question gets an answer from the named person or deputy, and the deputy runs the card test with someone new without you.Builder18 min read

Connect your tools1

T14-L03Turn a Connector Brief Into a Routine Colleagues Can RerunA saved routine (instructions, scope, inputs, output format), a test sheet with a fixed test week and four more cases with expected results, each colleague's run of the test week, and a README with maintainer, deputy and manual fallback; it passes when a colleague runs the routine from the README under their own account, their test-week file list matches yours or every difference is explained, and they produce the week's brief without asking you.Builder18 min read

AI in research1

T15-L03Get an AI Step on Participant Data Reviewed, Then Build It Inside the ApprovalOne review request with its data-flow map and the reviewers' answer, plus the working AI step: README, run record, the hand-coded test set and a colleague's rerun. It passes when no real data went anywhere before the answer, the test result meets the threshold you wrote down in advance, and the colleague reruns the step from the README and gets the same labels.Builder18 min read

Choose tools1

T16-L03Test a Tool on Your Own Work Before Your Team Depends on ItAn evaluation pack for one tool and one recurring job: the workload card, a case pack of at least 15 cases with known answers, the scoring rule, the results, and a one-page decision with a routing rule, a fallback and re-test triggers; it passes when a colleague reruns two cases and the fallback from the pack alone and reaches the same scores.Builder17 min read

Structure & understand1

T17-L03Explore What Already Exists Before You BuildA two-page exploration note with how it's done today, what exists, a checked source for every claim, one experiment and a revised problem statement, which passes when a colleague can open every source and find the claim it supports, and the two people who signed the original statement accept the revision.Builder18 min read

AI for lab data1

T18-L03Build a Cell-Counting Pipeline Your Group Can Rerun and CheckA pipeline folder (script, settings file, pinned requirements, sample images, expected counts, check script, README) that a colleague sets up and runs on their own computer from the README alone; it passes when their check prints PASS, or any difference is explained and written into the README.Builder17 min read

Share & review code1

T19-L03Propose, Review and Merge Changes With Pull RequestsA protected main, an issue and a merged pull request that fixes it, with at least one line comment, one Request changes, a new commit answering it and an Approve; the merge closed the issue, and a direct push to main is refused.Builder15 min read

AI harnesses1

T20-L03Run a Harness on a Model You Control: Local Server or Team GatewayA half-page set-up guide: approved model and where it runs, the four values per harness, the practice task result (2.000) per harness, and one provoked failure with how each harness reported it.Builder18 min read

Delegate desk work1

T21-L03Share Skills and Connections With Your Team, and Decide Who Gets WhatA one-page library sheet: each shared skill and connector with who can use it, who can change it, how people sign in and what the agent can do through it; where the service runs and who agreed to that; one change made by copy, test and replace, with its date; and the result of removing one colleague's access. It passes when a second colleague ran the shared skill without help, and the skill was gone from the removed colleague's Library after a refresh.Builder19 min read