Session 2 of AI Foundations, in 29 slides, moves from understanding the map to using it on your own ideas. It recaps the map, check, pick, build cycle, then turns the six worksheet questions into an audit that catches vague ideas before they become messy prompts - including the trap of a goal held together by the word "and". Next it converts a finished worksheet into a five-part prompt: role, input, output format, rules, and an instruction for what to do when information is missing. The meeting-notes example serves as the model, and an Amazon listing-rewrite prompt is built live. You will also see what happens when a prompt states no failure conditions and Claude invents fabric facts. The difference between an Artifact and a Skill is made concrete on four real clothing-business ideas by asking "will I OPEN this again, or DO this again?", with a trap about saving a Skill before testing it in chat. Four checks and two your-turn slides round the session out, and you leave with one finished mini-spec and one testable prompt. Nothing needs installing and no code is required; everything runs in the Claude app.
Subject: AI Foundations · 61 slides · applied lesson
Open the interactive version of this deck · Homework for this lesson
Title
Session 2 · AI Foundations · No-code-first track
Last week you learned the map. Today your own ideas go through it - and one comes out the other side as a real, testable prompt.
Objectives
You brought 2-3 tool ideas. Today we put them through the machine. By the end you can:
Warm-up
Discussion prompt
Before we open Turning AI Ideas into Buildable Prompts: without looking back, what was the main idea of Concepts, Tools & the Mapping Worksheet, and what could you do by the end of it that you could not do before?
Hint: One sentence for the idea, one for the skill. If the second one is blank, that is the part to revisit.
Answer:
The whole track in one deck: the concepts -> map -> build philosophy and the 'no garbage in, garbage out' north star; the landscape of what AI can build for you (chatbots, text processors, automations); the four ways to use Claude and when each fits (a one-off chat, a saved Artifact, a reusable Skill, the API) decided by how often and where a tool runs; and a full live walk of the mapping worksheet (Goal / Inputs / Outputs / Constraints / Success test / Reuse) applied to one running need - turning messy meeting notes into a clean action-item list. Two traps (building before mapping; using a one-off chat for a repeated job), two checks, a reusable fuzzy-idea-to-tool pattern, and a your-turn worksheet for the student's own idea.
Concept
The north star from Session 1: AI gives back the quality of what you put in. Same rule, your business this time:
| What you give it | What comes back |
|---|---|
| "Make my listings better." | Generic advice about listings - not YOUR listing. |
| "Rewrite THIS listing from THESE product facts: a title, 5 bullets, never invent materials." | A listing you could actually publish. |
Everything today is machinery for staying in the bottom row - on your ideas, not my examples.
Comparison
Comparison matrix
From Recap: no garbage in, garbage out: refill the What comes back column from what you know. The rest of the table is as it appeared.
| What you give it | What comes back |
|---|---|
| "Make my listings better." | Generic advice about listings - not YOUR listing. |
| "Rewrite THIS listing from THESE product facts: a title, 5 bullets, never invent materials." | A listing you could actually publish. |
Concept
Every idea you will ever have goes through the same four moves, in order:
Last week we lived in moves 1 and 2 with my example. Today: moves 1-4 on yours - and move 4 becomes an actual written prompt.
Matching
Match the pairs
From The four moves, one more time — match each one to what it actually does. The descriptions have been shuffled.
Why: 1 · Map, 2 · Check, 3 · Pick, 4 · Build are easy to tell apart while they are sitting next to their descriptions and much harder afterwards, which is what this checks.
Section
Part 1 · The worksheet as a detector
Concept
You know the six fields. Today each one becomes a pass/fail question you ask an idea. An idea that passes all six is ready to build; every fail is your next to-do.
| Field | The audit question |
|---|---|
| Goal | Can I say it in ONE sentence - with no "and" in it? |
| Inputs | Can I name exactly what I'll paste in, and where it comes from? |
| Outputs | Could a stranger sketch the output's shape from my description? |
| Constraints | What must it ALWAYS do - and what must it NEVER do? |
| Success test | Could I grade a result pass/fail in ten seconds? |
| Reuse | Once, repeated by hand, or automatic? |
Counterexample
Discussion prompt
You know the six fields. Today each one becomes a pass/fail question you ask an idea. An idea that passes all six is ready to build; every fail is your next to-do.
That is stated as though it always holds. Do one of two things: produce a case where it fails, or say precisely what rules such a case out. "It just does" is not on the menu.
Hint: Hunt at the extremes first — zero, one, negative, empty, equal. If every extreme survives, the reason they survive is the proof.
Picture it
Figure (svg): A worksheet of six fields where two are filled with question marks, with an arrow showing that each question mark becomes a guess Claude makes for you
Discussion prompt
Read the picture before the words. What is this showing, and what is the one thing it is built to make obvious? Commit to an answer, then read on.
Hint: Name the parts, then say what changes between them — and if nothing changes, say what is being held still.
Answer:
Why be this picky? Because Claude never leaves a blank blank. Whatever you don't specify, it fills in for you - confidently, plausibly, and by its own taste, not yours.
Intuition
Why be this picky? Because Claude never leaves a blank blank. Whatever you don't specify, it fills in for you - confidently, plausibly, and by its own taste, not yours.
Figure (svg): A worksheet of six fields where two are filled with question marks, with an arrow showing that each question mark becomes a guess Claude makes for you
So a blank isn't a failure. It's the worksheet pointing at the one thought you still owe the idea before it's worth building.
Analogy
Discussion prompt
Explain Every blank is a guess you outsourced by analogy to something with no AI Foundations in it at all — a queue, a recipe, a map, a bank balance, whatever fits. Then say where your analogy breaks.
Hint: An analogy that never breaks is not an analogy, it is the same idea wearing a hat. Find the seam — that is the part that is actually new.
Answer:
Why be this picky? Because Claude never leaves a blank blank. Whatever you don't specify, it fills in for you - confidently, plausibly, and by its own taste, not yours.
Ranking
Put in order
Put the moves of Audit a fuzzy idea, live into the order they have to happen.
Why: These are the moves of the worked example in the order it makes them, and each one is set up by the one before it. Not one checkable job. FAIL - and it's the most important fail, because every other field depends on it.
Worked example
Here's an idea the way ideas actually arrive: "I want AI to help with my Amazon listings." Run the audit with me - count the blanks as we go.
Goal: "help with my listings" - help HOW? Rewrite them? Grade them? Translate them?
Why: Not one checkable job. FAIL - and it's the most important fail, because every other field depends on it.
Inputs: which listing? The current text? The product facts? Photos?
Why: Nothing named that you could actually paste. FAIL.
Outputs: no shape at all - a rewrite? a score? a list of fixes?
Why: A stranger couldn't sketch it. FAIL.
Constraints and Success test: nothing yet - nothing to constrain until the goal exists.
Why: Two more blanks, both downstream of the vague Goal. FAIL, FAIL.
Reuse: this one we CAN answer - every new product, so repeated.
Why: PASS - one field out of six. The idea isn't bad; it's just five thoughts short of buildable.
Ten minutes of tightening turns this into: "Rewrite one product listing from facts I paste - title, 5 bullets, description - never inventing materials." Same idea, now buildable. That's the audit doing its job.
Reverse engineer
Discussion prompt
Work backwards. The example finished here:
Reuse: this one we CAN answer - every new product, so repeated.
What was it asked to do, and what must it have been given? Reconstruct the problem from its answer.
Hint: Every quantity in the result had to enter somewhere. Account for each one.
Answer:
Here's an idea the way ideas actually arrive: "I want AI to help with my Amazon listings." Run the audit with me - count the blanks as we go.
Anomaly
Predict first
A student writes this, and it looks reasonable:
Goal: "A tool that rewrites my listings and tracks my weekly sales and plans seasonal inventory."
It is wrong. Say what breaks — and say it before you turn the page.
Correct: Three jobs need three different inputs and three different output shapes - the worksheet jams immediately.
Split at every "and": three one-sentence goals, three small tools.
Why: Three jobs need three different inputs and three different output shapes - the worksheet jams immediately.
Trap
Goal: "A tool that rewrites my listings and tracks my weekly sales and plans seasonal inventory."
Try to fill Inputs: product facts? sales numbers? last year's inventory? All three?
Why: Three jobs need three different inputs and three different output shapes - the worksheet jams immediately.
Result: one mega-prompt that does all three jobs badly
Why: Each "and" quietly doubled what Claude has to guess about which job you meant right now.
Split at every "and": three one-sentence goals, three small tools.
Pick the highest-value one to build first: "Rewrite one product listing from facts I paste."
Why: One job = one input, one output shape, one success test. The worksheet fills in minutes.
Result: the other two goals go on the idea list - they're next sessions, not lost
Why: Small single-job tools ship and get used. Mega-tools stay half-built forever.
Worked example
Your turn. Take the first idea you brought. Read each of the six audit questions out loud and answer it - and when you can't, say "blank" out loud too. Predict before you start: how many of the six will pass?
Hint: start with the two fastest tests. Can you say the Goal in one sentence with no "and"? And can you name one real thing you would literally paste in as Input? If either fails, fix those two before touching the rest.
What a finished audit looks like - here's the listing idea after tightening:
| Field | Answer | Verdict |
|---|---|---|
| Goal | Rewrite one product listing from facts I paste. | PASS |
| Inputs | Product facts: fabric, sizes, colors, fit, care. | PASS |
| Outputs | Title + 5 benefit bullets + short description. | PASS |
| Constraints | Only my facts; never invent materials or measurements. | PASS |
| Success test | Every claim traceable to a fact I gave; right shape. | PASS |
| Reuse | Every new product -> repeated, by hand, in the app. | PASS |
Trade off
Comparison matrix
From Your turn: audit your first idea: every row here is a choice with a cost. Fill the Verdict column, then say which row you would actually pick and what you give up for it.
| Field | Answer | Verdict |
|---|---|---|
| Goal | Rewrite one product listing from facts I paste. | PASS |
| Inputs | Product facts: fabric, sizes, colors, fit, care. | PASS |
| Outputs | Title + 5 benefit bullets + short description. | PASS |
| Constraints | Only my facts; never invent materials or measurements. | PASS |
| Success test | Every claim traceable to a fact I gave; right shape. | PASS |
| Reuse | Every new product -> repeated, by hand, in the app. | PASS |
Section
Part 2 · The conversion
Concept
Here's the payoff for the mapping work: you don't write a prompt from scratch - you convert the worksheet you already filled in. Five parts, and each one comes straight from a field:
| Prompt part | What it does | Comes from |
|---|---|---|
| Role | One sentence: who Claude is for this job. | Goal |
| Input | What you'll paste, announced up front. | Inputs |
| Output format | The exact shape of what comes back. | Outputs |
| Rules | The always / never lines. | Constraints |
| Missing-info instruction | What to do INSTEAD of guessing. | Constraints + Success test |
Notice what's not in the prompt: the Success test stays with you. It's your grading pen - you judge every output against it; you don't hand it to Claude.
Comparison
Comparison matrix
From A prompt is the worksheet, re-worn: refill the Comes from column from what you know. The rest of the table is as it appeared.
| Prompt part | What it does | Comes from |
|---|---|---|
| Role | One sentence: who Claude is for this job. | Goal |
| Input | What you'll paste, announced up front. | Inputs |
| Output format | The exact shape of what comes back. | Outputs |
| Rules | The always / never lines. | Constraints |
| Missing-info instruction | What to do INSTEAD of guessing. | Constraints + Success test |
Intuition
When you just chat, you nudge and re-nudge until the output looks right - and then all that nudging evaporates. Next week you negotiate from zero again, and the result drifts.
A written prompt is a contract: same words in, same shape out. When something's wrong, you edit one clause and keep the rest - instead of starting the whole negotiation over.
And this is the whole point of writing it down: a prompt you can paste is a prompt you can test, improve, and eventually save as a Skill. A great chat you had once is none of those things.
Explain it
Discussion prompt
Explain A chat is a negotiation. A prompt is a contract. to a student a year behind you. No notation, no jargon they have not met — and it still has to be true.
Hint: If your explanation needs a symbol they have never seen, you are describing the notation rather than the idea.
Answer:
When you just chat, you nudge and re-nudge until the output looks right - and then all that nudging evaporates. Next week you negotiate from zero again, and the result drifts.
Ranking
Put in order
Put the moves of The model conversion: meeting notes -> prompt into the order they have to happen.
Why: These are the moves of the worked example in the order it makes them, and each one is set up by the one before it. The one-sentence goal IS the role sentence - that's why we insisted on one sentence.
Worked example
Session 1's finished worksheet, one more time - now watch it become a prompt, field by field:
| Field | Answer |
|---|---|
| Goal | Turn my raw meeting notes into a clean action-item list. |
| Inputs | The notes I paste after the meeting. |
| Outputs | Numbered list: task - owner - due date. |
| Constraints | Always an owner; never invent a date. |
| Success test | Every action appears once; nothing invented. |
| Reuse | Most weeks -> a Skill, eventually. |
Goal becomes the Role: "You are my meeting-notes assistant. Your job: turn my raw notes into a clean action-item list."
Why: The one-sentence goal IS the role sentence - that's why we insisted on one sentence.
Inputs and Outputs become the INPUT and OUTPUT lines - announced before any notes appear.
Why: Claude formats best when it knows the target shape BEFORE it reads the material, not after.
Constraints become RULES, and the never-invent rule gets a partner: what to do INSTEAD.
Why: "Never invent a date" alone leaves a hole - Claude still has to put SOMETHING there. "Write UNKNOWN" fills the hole safely.
You are my meeting-notes assistant. Your job: turn my raw
notes into a clean action-item list.
INPUT: I will paste raw meeting notes below.
OUTPUT: A numbered list. Each item on one line:
task - owner - due date.
RULES:
- Always name an owner for every task.
- Never invent a date or owner that is not in the notes.
IF SOMETHING IS MISSING: write UNKNOWN in that spot.
Do not guess.
NOTES:
[paste notes here]Five parts, every one traceable to a worksheet field. And the Success test - every action once, nothing invented - stays in your pocket to grade what comes back.
Trade off
Comparison matrix
From The model conversion: meeting notes -> prompt: every row here is a choice with a cost. Fill the Answer column, then say which row you would actually pick and what you give up for it.
| Field | Answer |
|---|---|
| Goal | Turn my raw meeting notes into a clean action-item list. |
| Inputs | The notes I paste after the meeting. |
| Outputs | Numbered list: task - owner - due date. |
| Constraints | Always an owner; never invent a date. |
| Success test | Every action appears once; nothing invented. |
| Reuse | Most weeks -> a Skill, eventually. |
Estimation
Predict first
Now the tightened listing idea from Part 1 - the worksheet passed all six, so the conversion is mechanical:
Commit before you compute: what does Same conversion, your domain: the listing rewriter come out to? A rough magnitude and the right form is enough — the point is to have something concrete to be wrong about.
Correct: Read it once more and name each part: role, input, output, rules, missing-info instruction.
Why: A prediction you can defend turns the computation into a check rather than a leap of faith — and an answer that contradicts it is caught on the spot. If you can point to all five, the prompt is structurally complete - anything still wrong is a wording tweak, not a rebuild.
Worked example
Now the tightened listing idea from Part 1 - the worksheet passed all six, so the conversion is mechanical:
| Field | Answer |
|---|---|
| Goal | Rewrite one product listing from facts I paste. |
| Inputs | Product facts: fabric, sizes, colors, fit, care. |
| Outputs | Title + 5 benefit bullets + short description. |
| Constraints | Only my facts; never invent materials or measurements. |
| Reuse | Every new product -> repeated. |
You are an e-commerce copywriter for my Amazon clothing
store.
INPUT: I will paste the product facts below (fabric, sizes,
colors, fit, care).
OUTPUT: One Amazon listing: a title, 5 benefit-focused
bullet points, and a short description paragraph.
RULES:
- Use only the facts I give you.
- Never invent materials, measurements, or care
instructions.
- Plain language a shopper can skim in seconds.
IF A FACT IS MISSING: ask me for it at the top of your
reply instead of writing around it.
PRODUCT FACTS:
[paste facts here]Read it once more and name each part: role, input, output, rules, missing-info instruction.
Why: If you can point to all five, the prompt is structurally complete - anything still wrong is a wording tweak, not a rebuild.
This prompt is reusable verbatim: next product, same prompt, new facts pasted at the bottom. That's what "buildable" meant all along.
Comparison
Comparison matrix
From Same conversion, your domain: the listing rewriter: refill the Answer column from what you know. The rest of the table is as it appeared.
| Field | Answer |
|---|---|
| Goal | Rewrite one product listing from facts I paste. |
| Inputs | Product facts: fabric, sizes, colors, fit, care. |
| Outputs | Title + 5 benefit bullets + short description. |
| Constraints | Only my facts; never invent materials or measurements. |
| Reuse | Every new product -> repeated. |
Anomaly
Predict first
A student writes this, and it looks reasonable:
Keep it short: "You are a copywriter. Write a great Amazon listing for this hoodie."
It is wrong. Say what breaks — and say it before you turn the page.
Correct: It was told to produce a finished listing at all costs, so it fills every gap with something plausible.
Same ask, plus two lines: "Use only the facts I give you. If a fact is missing, ask me at the top of your reply."
Why: It was told to produce a finished listing at all costs, so it fills every gap with something plausible. Plausible is not true.
Trap
Keep it short: "You are a copywriter. Write a great Amazon listing for this hoodie."
You never stated the fabric - so Claude writes "100% organic cotton, buttery soft"
Why: It was told to produce a finished listing at all costs, so it fills every gap with something plausible. Plausible is not true.
Result: copy that reads beautifully and lies about the product
Why: On a real store that's returns, bad reviews, and policy trouble - the most expensive kind of garbage out.
Same ask, plus two lines: "Use only the facts I give you. If a fact is missing, ask me at the top of your reply."
Claude's first reply opens: "Before I write: what is the fabric? What are the care instructions?"
Why: You gave it a legal move OTHER than guessing - so it takes it. The gap surfaces to you instead of into the copy.
Result: one extra exchange, and every line in the listing is true
Why: A never-rule plus an instead-instruction is what turns "don't lie" from a hope into a mechanism.
Break the constraint
Discussion prompt
The rule this trap just fixed:
You gave it a legal move OTHER than guessing - so it takes it. The gap surfaces to you instead of into the copy.
Now break it on purpose. Build a case that violates it and follow the consequences until something visibly fails. Where does the failure first show up — and would you have noticed it if you had not been looking?
Hint: The dangerous rules are the ones whose violation still produces an answer. If yours fails loudly, try to find one that fails quietly.
Answer:
It was told to produce a finished listing at all costs, so it fills every gap with something plausible. Plausible is not true.
Worked example
Your turn. Take the idea you audited in Part 1 and write the prompt - full sentences, in a note you can paste from later. Before you start, predict: which of the five parts will be hardest to write from your worksheet?
Hint: convert in order - Goal -> role sentence, Inputs -> INPUT:, Outputs -> OUTPUT:, Constraints -> RULES: - then add the fifth part yourself: what should Claude do instead of guessing when something's missing? (Ask you? Write UNKNOWN? Skip the item?) Your Success test stays out of the prompt.
Stuck? Use the listing prompt as your model - it's the answer key. Match your draft against its skeleton: role sentence first, then INPUT, OUTPUT, RULES, IF-MISSING, then the paste slot at the bottom.
Section
Part 3 · Picking the home
Concept
Session 1 gave you all four ways to use Claude. The two that get confused are Artifact and Skill - here's the distinction that settles it:
| Artifact | Skill | |
|---|---|---|
| What it is | A thing Claude made that you KEEP: a document, template, checklist, mini-app. | Saved instructions Claude FOLLOWS: your repeated task, done your way. |
| You interact by | Opening it again - reading, editing, reusing. | Running it again - on fresh input each time. |
| The value lives in | The output itself. | The repeatable process. |
| The one question | "Will I OPEN this again?" | "Will I DO this again?" |
That last row is the whole decision. Open again -> Artifact. Do again -> Skill. Everything else is detail.
Analogy
Discussion prompt
Explain The working distinction by analogy to something with no AI Foundations in it at all — a queue, a recipe, a map, a bank balance, whatever fits. Then say where your analogy breaks.
Hint: An analogy that never breaks is not an analogy, it is the same idea wearing a hat. Find the seam — that is the part that is actually new.
Answer:
Session 1 gave you all four ways to use Claude. The two that get confused are Artifact and Skill - here's the distinction that settles it:
Picture it
Figure (svg): Three ascending steps labeled chat, artifact, and skill: try the prompt in chat, keep the good output as an artifact, save the repeated process as a skill
Discussion prompt
Read the picture before the words. What is this showing, and what is the one thing it is built to make obvious? Commit to an answer, then read on.
Hint: Name the parts, then say what changes between them — and if nothing changes, say what is being held still.
Answer:
An Artifact is a document: it sits there, holding its value, waiting to be opened. A Skill is a habit: it holds no content at all - it's a way of doing that fires every time the situation comes up.
Intuition
An Artifact is a document: it sits there, holding its value, waiting to be opened. A Skill is a habit: it holds no content at all - it's a way of doing that fires every time the situation comes up.
Figure (svg): Three ascending steps labeled chat, artifact, and skill: try the prompt in chat, keep the good output as an artifact, save the repeated process as a skill
The ladder matters more than the labels: nothing starts as a Skill. It starts as a chat that worked, becomes a template worth keeping, and earns Skill status by being repeated. You never have to pick perfectly on day one.
Ranking
Put in order
Put the moves of Classify four ideas from your own shelf into the order they have to happen.
Why: These are the moves of the worked example in the order it makes them, and each one is set up by the one before it. The process repeats with fresh facts each run; the old outputs don't get reopened.
Worked example
Four plausible tools for an Amazon clothing business. For each, ask the one question - open again, or do again? Decide each one before its step reveals.
Product-listing rewriter -> DO again, every new product -> Skill
Why: The process repeats with fresh facts each run; the old outputs don't get reopened. (It's the prompt we just wrote - it starts life pasted into chat.)
Weekly sales summary from pasted Seller Central numbers -> DO again, every Monday -> Skill
Why: Identical shape weekly, new data each time. Exactly the repeated-by-hand pattern Skills exist for.
Seasonal inventory checklist -> OPEN again, twice a year -> Artifact
Why: The value is the document itself - you reopen it, tick it, edit it as seasons teach you things. Nothing repeats often enough to be a habit.
Vendor-facing product sheet generator -> both, in sequence -> Artifact template first, Skill if vendors multiply
Why: Design the sheet's skeleton once as an Artifact; if you find yourself generating one per vendor per month, the PROCESS has become the value - promote it.
Notice none of these needed the API: nothing here runs automatically inside other software. That stays true until you want it to fire without you - and that's a later session, only if a project demands it.
Reverse engineer
Discussion prompt
Work backwards. The example finished here:
Vendor-facing product sheet generator -> both, in sequence -> Artifact template first, Skill if vendors multiply
What was it asked to do, and what must it have been given? Reconstruct the problem from its answer.
Hint: Every quantity in the result had to enter somewhere. Account for each one.
Answer:
Four plausible tools for an Amazon clothing business. For each, ask the one question - open again, or do again? Decide each one before its step reveals.
Anomaly
Predict first
A student writes this, and it looks reasonable:
The prompt is written - immediately save it as a Skill. It's going to be a weekly job, after all.
It is wrong. Say what breaks — and say it before you turn the page.
Correct: You're now debugging two things at once: the wording of the instructions AND the packaging around them.
The prompt is written - paste it into a plain chat first.
Why: You're now debugging two things at once: the wording of the instructions AND the packaging around them.
Trap
The prompt is written - immediately save it as a Skill. It's going to be a weekly job, after all.
First real run: the output shape is wrong - so you edit the saved Skill, re-run, edit again...
Why: You're now debugging two things at once: the wording of the instructions AND the packaging around them.
Result: the 10-tweak loop the worksheet was supposed to kill - just relocated into your Skill settings
Why: Premature packaging turns cheap experiments into slow ones.
The prompt is written - paste it into a plain chat first.
Run it 2-3 times on REAL inputs; grade each run against your Success test; tweak the wording between runs
Why: A chat is the cheapest possible test bench - each experiment costs one paste.
Result: only the version that passes gets saved as the Skill
Why: Packaging is the LAST step of building, not the first. You save what works, not what you hope works.
Two truths and a lie
Sort into buckets
Some of these hold up and some are the exact mistakes this lesson is built to prevent. Sort them.
Ranking
Put in order
These are the steps of The full recipe: idea -> tested tool, scrambled. Put them back in order before the next slide shows you.
Why: This is the order the recipe itself gives. Recalling the sequence without the slide in front of you is the difference between recognising the method and being able to run it — most of what goes wrong in practice is a step done out of turn.
Pattern
Everything today, as one recipe you can run on any idea forever:
Map, check, pick, build - same four moves as always. Today just gave moves 3 and 4 their machinery.
Edge cases
Discussion prompt
The full recipe: idea -> tested tool works on the cases you have just seen. Push it to the edge: what is the most degenerate input it still handles — empty, zero, one item, everything equal — and what is the first case where it stops being true? Name the case, not just "it breaks".
Hint: Try the smallest legal input, then the largest, then the one where two things collide. Methods are specified at their edges; the middle takes care of itself.
Answer:
Everything today, as one recipe you can run on any idea forever:
Elimination
Eliminate the wrong options
A worksheet reads - Goal: "Summarize my weekly sales." Inputs: "the numbers I copy from Seller Central each Monday." Outputs: "a useful summary." Constraints: "never invent numbers." Reuse: "every week." Which field fails the audit?
3 of these 4 are wrong. Strike them one at a time, and say what rules each one out before you strike the next. The survivor is the answer.
Survives elimination: C
Why: "A useful summary" is exactly the kind of blank Claude fills by taste - one week you get paragraphs, the next a table, and you can't grade either. The fix is a sketchable shape: e.g. "total revenue, top 3 products by units, and any product down 20% or more from last week." Every other field passes: one-sentence goal, a nameable paste-able input, a real never-rule, and a clear reuse answer.
Check
Run the audit in your head before you tap.
Check your understanding
A worksheet reads - Goal: "Summarize my weekly sales." Inputs: "the numbers I copy from Seller Central each Monday." Outputs: "a useful summary." Constraints: "never invent numbers." Reuse: "every week." Which field fails the audit?
Answer: C
Why: "A useful summary" is exactly the kind of blank Claude fills by taste - one week you get paragraphs, the next a table, and you can't grade either. The fix is a sketchable shape: e.g. "total revenue, top 3 products by units, and any product down 20% or more from last week." Every other field passes: one-sentence goal, a nameable paste-able input, a real never-rule, and a clear reuse answer.
Prediction
Predict first
Your listing prompt keeps producing "100% organic cotton" for a hoodie whose fabric you never provided. Which change targets the actual failure?
Answer it in your own words, now, with nothing to choose from. The options are on the next slide — and picking the right one off a list is an easier skill than producing it.
Correct: Add: "Use only the facts I give you. If the fabric is missing, ask me instead of guessing."
Why: The failure is a missing rule plus a missing instead-instruction: nothing told Claude that inventing facts is out of bounds, or gave it a legal move (ask) when a fact is absent. A never-rule with an escape hatch turns "don't lie" into a mechanism. Role, output length, and re-rolling all leave the actual gap open.
Check
Think about WHICH prompt part owns this failure before you tap.
Check your understanding
Your listing prompt keeps producing "100% organic cotton" for a hoodie whose fabric you never provided. Which change targets the actual failure?
Answer: A
Why: The failure is a missing rule plus a missing instead-instruction: nothing told Claude that inventing facts is out of bounds, or gave it a legal move (ask) when a fact is absent. A never-rule with an escape hatch turns "don't lie" into a mechanism. Role, output length, and re-rolling all leave the actual gap open.
Prediction
Predict first
The weekly sales summary - same format every Monday, fresh numbers pasted each time, run by hand in the Claude app. Once the prompt passes its success test, where should it live?
Answer it in your own words, now, with nothing to choose from. The options are on the next slide — and picking the right one off a list is an easier skill than producing it.
Correct: A Skill - saved instructions you run on new numbers each week
Why: This is DO-again, not OPEN-again: the process repeats weekly with fresh input, and the old summaries aren't the ongoing value - the repeatable process is. Saved instructions run on new data each time is the definition of a Skill.
Check
One question decides it: open again, or do again?
Check your understanding
The weekly sales summary - same format every Monday, fresh numbers pasted each time, run by hand in the Claude app. Once the prompt passes its success test, where should it live?
Answer: B
Why: This is DO-again, not OPEN-again: the process repeats weekly with fresh input, and the old summaries aren't the ongoing value - the repeatable process is. Saved instructions run on new data each time is the definition of a Skill.
Elimination
Eliminate the wrong options
The seasonal inventory checklist: built once, reopened twice a year before each buying season, ticked off and edited as you learn what to watch for. Where should it live?
3 of these 4 are wrong. Strike them one at a time, and say what rules each one out before you strike the next. The survivor is the answer.
Survives elimination: C
Why: This is OPEN-again: the checklist document itself is the value - your accumulated edits and lessons live in it, and twice a year you return to that same object. Nothing repeats often enough to be a habit, and nothing runs without you. Kept, reopened, edited = Artifact.
Check
Same one question. Careful - this one flips.
Check your understanding
The seasonal inventory checklist: built once, reopened twice a year before each buying season, ticked off and edited as you learn what to watch for. Where should it live?
Answer: C
Why: This is OPEN-again: the checklist document itself is the value - your accumulated edits and lessons live in it, and twice a year you return to that same object. Nothing repeats often enough to be a habit, and nothing runs without you. Kept, reopened, edited = Artifact.
Concept
You're leaving with a finished worksheet and a written prompt. This week, put the prompt on the bench:
Next session we take what passed and what didn't, refine the wording together, and save the winner as your first real Skill or Artifact. Failures are the most useful thing you can bring.
Counterexample
Discussion prompt
You're leaving with a finished worksheet and a written prompt. This week, put the prompt on the bench:
That is stated as though it always holds. Do one of two things: produce a case where it fails, or say precisely what rules such a case out. "It just does" is not on the menu.
Hint: Hunt at the extremes first — zero, one, negative, empty, equal. If every extreme survives, the reason they survive is the proof.
Connect it up
Draw it
One page, no notation unless you need it: draw how these connect — Audit Your Ideas · Worksheet -> Prompt · Artifact or Skill?. Put an arrow wherever one of them is what makes another possible, and label the arrow with why.
Recap
| The move | The shortcut |
|---|---|
| Catch a vague idea | Six audit questions; count the blanks |
| Write the prompt | Convert fields in order; add the IF-MISSING line |
| Keep it honest | Success test stays with YOU, as the grading pen |
| Pick Artifact vs Skill | OPEN again vs DO again |
| Make it permanent | Pass the test in chat first, THEN save |
This week: 2-3 real runs, graded in writing. Next session: we refine together and save your first Skill. You're past learning the map - you're using it.
Want this taught 1-on-1? Alexander tutors AI Foundations — $55/session, free consultation.