---
title: Storyline storyboard
summary: The 32-slide Storyline design, with variables, branching and a mock Claude Code screen. Designed and approved, not built.
---

# Storyline storyboard: One Task, Start to Finish

**Written for the Storyline plan.** This was written on 2026-10-12, before the course was built in Rise instead (Storyline runs only on Windows). The Rise script lists what changed. The pass mark was later raised to 90%, and the Rise quiz uses all 10 questions.

**Who it's for.** Any small business owner in the US. Nothing here is tied to one region; local versions can come later.

**Everything in the practice is simulated.** Cedar Row Architects, its fees, policies, clients and intake notes are made up. The Claude Code screens are mock-ups built in Storyline, not screenshots.

## At a glance

| Item | Plan |
|---|---|
| Learner | A small business owner who has never used Claude Code and doesn't know where to begin |
| The promise | One path to follow. Each step opens after you practice it, do it for real, and pass a check. |
| Length | About 20 minutes in the course, plus the real steps in the learner's own Claude Code, at their own pace |
| Story size | 16:9, 1280 × 720, modern player |
| Slides | 32, plus a 10-question bank |
| Scored | Final check: 6 questions drawn from 10, pass at 80%. Each step also has one gate question to answer right before the next step opens. |
| Tracking | SCORM 2004 4th edition, tracked by the Final check results slide. Resume saves the learner's place and everything they typed. |
| Narration | Text-to-speech on slides marked **[N]**, with captions created from the TTS |

**The framework** (Dean's five steps, one per section):

1. Pick one task that repeats.
2. Give Claude the details of the task.
3. Run the task and check the result.
4. Update the instructions.
5. Save it for next time.

**Every step follows the same four beats:** Learn, Practice (in a mock Claude Code screen), Do it for real (in the learner's own Claude Code), Check (a gate question). The learner can stop after any beat and pick up where they left off.

## How the course tracks and judges

This is the point of the course, so it's built into every step:

- **One locked path.** A step's tab stays Locked until the step before it is Done.
- **The learner's own task, carried through.** In step 1 they type the task they'll hand off (`%MyTask%`). It comes back in every later step's prompts and in their plan at the end.
- **Do it for real, then confirm.** Each step has a checklist of what to do in their own Claude Code. Continue opens once every box is checked and the text boxes are filled in.
- **A gate at every step.** One question, answered right, opens the next step. A wrong answer explains why and lets them try again.
- **A scored final check** that reports to the LMS.
- **A plan to keep.** The last slide shows everything they typed: their task, what they told Claude, their rule, their skill's name, and when they'll run it. They can print it.

## Flow

```
Start          1.1 Where do you start? -> 1.2 How this course works -> 1.3 Get Claude Code open
Step 1 Pick    2.1 Learn -> 2.2 Practice: sort tasks -> 2.3 Do it: name your task -> 2.4 Check
Step 2 Details 3.1 Learn -> 3.2 Practice: what to share, and the CLAUDE.md -> 3.3 Do it -> 3.4 Check
Step 3 Run     4.1 Learn -> 4.2 Practice: ask and approve -> 4.3 Practice: check the draft -> 4.4 Do it -> 4.5 Check
Step 4 Update  5.1 Learn -> 5.2 Practice: three fixes -> 5.3 Do it -> 5.4 Check
Step 5 Save    6.1 Learn -> 6.2 Practice: save the skill -> 6.3 Practice: the next project -> 6.4 How your fixes held
               -> 6.5 Do it -> 6.6 Check
Final check    7.1 Intro -> 7.2 Draw 6 of 10 -> 7.3 Results (Retry draws a new set)
Wrap           8.1 Your one-task plan -> 8.2 and 8.3 Two quick questions
```

**The branch that plays out across steps.** In step 4 the learner chooses how to fix three problems: a specific rule, a vague rule, or a hand fix. In step 5, the next project's draft brings back every problem that didn't get a specific rule. The choice is made in one scene and its consequence shows up in another, driven by variables.

## The practice business (fictional)

**Cedar Row Architects**, a three-person firm that designs homes, additions and remodels. The learner plays the principal. The repeating task: turning a client's intake notes into a fee proposal.

**fee-schedule.xlsx**

| Item | Rate |
|---|---|
| Principal architect | $185 per hour |
| Project architect | $140 per hour |
| Drafter | $95 per hour |
| Site visit | $250 each |
| Optional, only if the client asks: interior finish selections | Billed hourly at the project architect rate |
| Optional, only if the client asks: 3D renderings | $600 per view |

**policies.docx**

- A 20% retainer starts the work. We bill the rest monthly for hours worked.
- Proposals are good for 30 days.
- The city sets permit timing. We send our design schedule once the retainer is in.

**intake-notes-lee.txt** (step 3)

- Kitchen and family room remodel, single-family home
- Services: design through the permit set
- Estimated hours: principal 10, project architect 32, drafter 56
- One site visit to measure
- Client asked if we can have the permit by March

**intake-notes-kim.txt** (step 5)

- Detached garage with a studio above, new construction
- Services: design through the permit set
- Estimated hours: principal 14, project architect 40, drafter 60
- Two site visits
- Client asked if we can guarantee the permit by June

**Correct proposals** (checked by a test script):

| Line | Lee | Kim |
|---|---|---|
| Principal | 10 hrs × $185 = $1,850.00 | 14 hrs × $185 = $2,590.00 |
| Project architect | 32 hrs × $140 = $4,480.00 | 40 hrs × $140 = $5,600.00 |
| Drafter | 56 hrs × $95 = $5,320.00 | 60 hrs × $95 = $5,700.00 |
| Site visits | 1 × $250 = $250.00 | 2 × $250 = $500.00 |
| Estimated fee | $11,900.00 | $14,390.00 |
| Retainer to start (20%) | $2,380.00 | $2,878.00 |

## Visual system

**Type.** Source Sans 3 for everything; Source Code Pro for file names, commands and the CLAUDE.md file. Titles 32 pt, body 20 pt, mock-screen text 18 pt minimum.

**Colors.** All text colors pass 4.5:1 on both backgrounds (measured).

| Token | Hex | Use | On white #FFFFFF | On panel #F4F6F8 |
|---|---|---|---|---|
| Ink | #1F2A44 | Body text, section bar | 14.3:1 | 13.2:1 |
| Muted | #4A5568 | Labels, Claude's activity lines | 7.5:1 | 7.0:1 |
| Teal | #0F6E6E | Buttons, links | 6.0:1 | 5.6:1 |
| Red | #B3261E | "Problem" marks | 6.5:1 | 6.0:1 |
| Green | #1E6B34 | "Fixed", "Done", correct | 6.6:1 | 6.0:1 |
| Amber | #8A5A00 | Permission prompts, warnings | 5.9:1 | 5.5:1 |
| Focus | #1D4ED8 | Keyboard focus outline | 6.7:1 | 6.2:1 |

White text on Teal is 6.0:1 and on Ink 14.3:1.

**Every status pairs an icon with a word:** Problem, Fixed, Matches, Locked, Done. Color is never the only signal.

**The mock Claude Code screen.** One reusable layout built from Storyline shapes and real text:

- a title bar reading "Claude · Code · Proposals folder" and a small "Simulated" tag
- a left sidebar listing the files in the folder
- the main pane: the learner's request, Claude's activity lines in Muted monospace ("Read intake-notes-lee.txt"), and Claude's replies
- permission prompts as an amber-edged card naming the action, with Allow and Deny buttons
- a message box at the bottom

It should look like Claude Code without copying it exactly: no Anthropic logo, and no pixel-for-pixel copy of the app. Before building, open the current desktop app and match the wording of the Code tab, the folder picker and the permission prompts, because they change often.

**Layout.** On mock-screen slides the screen takes the left 60%. The right 40% is a reference panel (#F4F6F8) with tabs for Notes, Fees and Policies, so the learner can check the draft against the firm's own details.

**Motion.** Fade entrances only, 0.25 s. No timers.

## Variables

| Variable | Type | Start | Set on | Used for |
|---|---|---|---|---|
| CurrentSection | Number | 1 | The button that leads into each section, and each tab click | Section bar "Current" state |
| S1Done to S7Done | True/False | False | Last slide of Start, steps 1 to 5, and Final check (on passing) | Section bar Done and Locked states |
| HookChoice | Number | 0 | 1.1 | Callback on 8.1 |
| MyTask | Text | (blank) | 2.3 | Prompts in every later step; plan on 8.1 |
| MyFrequency | Number | 0 | 2.3 | Nudge toward a task that comes up often |
| NudgeSeen | True/False | False | 2.3 | Show the nudge only once |
| MyDetails | Text | (blank) | 3.3 | Plan on 8.1 |
| MyProblem | Text | (blank) | 4.4 | 5.3 prompt |
| MyRule | Text | (blank) | 5.3 | Plan on 8.1 |
| MySkill | Text | (blank) | 6.5 | Plan on 8.1 |
| MyWhen | Text | (blank) | 6.5 | Plan on 8.1 |
| ToneChoice, MissingChoice, SaveChoice | Number | 0 | 3.2 | The CLAUDE.md builder |
| AllowedFeeEdit | True/False | False | 4.2 | Debrief line on 4.3 |
| FixedCount | Number | 0 | 4.3 | Approve button on 4.3 |
| FalseFlags | Number | 0 | 4.3 | Debrief line on 4.3 |
| Fix1, Fix2, Fix3 | Number | 0 | 5.2 | 1 = specific rule, 2 = vague rule, 3 = fixed by hand. Drives the Kim draft on 6.3 |
| KimProblems | Number | 0 | 6.3 | How many problems came back |
| KimFixed | Number | 0 | 6.3 | Approve button on 6.3 |

Text entry variables update when the field loses focus. Put the Continue check on the button click, not on the field.

## Slide master, section bar and player

**Section bar (custom menu).** Eight tabs on the slide master: Start, 1 Pick, 2 Details, 3 Run, 4 Update, 5 Save, Final check, Wrap. The five step tabs are numbered circles joined by a line, so the path reads as one route. The built-in player menu is off.

Tab states: Normal (available), Current (teal fill, white text), Done (check icon plus "Done"), Locked (lock icon plus "Locked", greyed, not clickable).

Master triggers, in this order, for each tab n (tab 3 shown, which is "2 Details"):

1. When the timeline starts: change the state of Tab3 to Locked.
2. When the timeline starts: change the state of Tab3 to Normal if S2Done = True.
3. When the timeline starts: change the state of Tab3 to Done if S3Done = True.
4. When the timeline starts: change the state of Tab3 to Current if CurrentSection = 3.
5. When the user clicks Tab3: set CurrentSection = 3, then jump to slide 3.1, if the state of Tab3 is not Locked.

Tab 1 (Start) is always available. Set CurrentSection in the trigger that leads into a section, not on the section's first slide, so the master triggers already see the new value.

**Player.** Modern player. Menu off, seekbar off, Previous and Next on, captions button on, volume on. Resume: prompt to resume. Turn on accessible text. On slides with a task to finish, Next starts Disabled through a trigger and opens when the task is done.

**Copy buttons.** "Copy prompt" buttons run a JavaScript trigger that copies the prompt text (with the learner's `MyTask` filled in) to the clipboard, then change the button to a "Copied" state. The prompt is also shown on screen as selectable text, so the learner can copy it by hand.

```js
var p = GetPlayer();
var text = "I'd like your help with a task I do often: " + p.GetVar("MyTask") + ". Interview me about how I do it, one question at a time. When you have what you need, write it into CLAUDE.md and show me.";
navigator.clipboard.writeText(text);
```

---

## Start

### 1.1 Where do you start? [N]

**Screen.** A kitchen table at night. A laptop shows the Claude desktop app, open and empty. Top right: "8:04 p.m." On the table, five sticky notes, each a button:

> - Watch "50 Claude Code tips"
> - Learn the terminal first
> - Connect Claude to all my apps
> - Build an app for my business
> - Pick one task I do over and over

**On-screen text.**

> You've heard Claude Code can take work off your plate. Tonight you finally sit down to try it.
>
> The proposal you promised this afternoon still isn't written.
>
> **Where do you start?**

**Narration.** The on-screen text.

**Layers.**

- **Lost** (any of the first four notes): the clock reads 11:15 p.m. Text: "You learned a lot. The proposal still isn't written, and tomorrow there's more to watch."
- **Focused** (the fifth note): Text: "Good instinct. That's step 1."
- Both layers end with: "This course gives you one path: five steps, in order, on a task of your own. Each step opens when you've done the one before." and [Continue].

**Triggers.**

1. Notes 1 to 4: set HookChoice to the note's number, show layer Lost.
2. Note 5: set HookChoice = 5, show layer Focused.
3. Continue: jump to 1.2.

**Accessibility.** Focus order: clock, the paragraph, the question, the five notes top to bottom. The table photo is decorative; the laptop's screen is described in the paragraph.

### 1.2 How this course works [N]

**On-screen text.**

> # One path, five steps
>
> 1. Pick one task that repeats.
> 2. Give Claude the details of the task.
> 3. Run the task and check the result.
> 4. Update the instructions.
> 5. Save it for next time.
>
> Dean learned these five steps by making the mistakes first, so you don't have to.
>
> **Every step goes the same way.** Learn it, practice it here, then do it for real in your own Claude Code. Pass a short check, and the next step opens.
>
> **About 20 minutes here.** The real steps happen in your own Claude Code, at your pace.
>
> *The practice uses a made-up business, Cedar Row Architects. The Claude Code screens are simulated.*

**Visual.** The five steps as the same numbered path as the section bar, with step 1 open and the rest Locked.

**Narration.** "One path, five steps. Dean learned them by making the mistakes first, so you don't have to. Learn each step, practice it, then do it for real. Pass a short check, and the next step opens."

### 1.3 Get Claude Code open

**On-screen text.**

> # Before step 1: get Claude Code open
>
> Check each box when it's true.
>
> - [ ] I have a paid Claude plan. (Pro is about $20 a month, paid to Anthropic.)
> - [ ] I installed the Claude desktop app from claude.ai/download.
> - [ ] I can open the Code tab and choose a folder.
>
> [Prefer the terminal?] [Open Anthropic's setup guide]

**Layer: Prefer the terminal?** "Everything here works in the terminal too. Open a terminal in your task folder and type `claude`." [Close]

**Triggers.**

1. When the timeline starts: change the state of Next to Disabled.
2. When the state of all three checkboxes is Selected: change the state of Next to Normal.
3. Open Anthropic's setup guide: opens Anthropic's Claude Code documentation in a new tab.
4. Next: set S1Done = True, set CurrentSection = 2, jump to 2.1.

**Accessibility.** The checkboxes are Storyline checkbox controls, so screen readers announce checked and unchecked.

---

## Step 1: Pick one task

### 2.1 Learn: a good first task [N]

**On-screen text.**

> # Step 1: Pick one task that repeats
>
> Start with a task you can finish and check. A good first task:
>
> - **comes up often**, every day or every week
> - **has steps you could explain to a new hire**
> - **can be checked in a few minutes** against something you trust
> - **goes past you before it reaches a customer**
>
> **Examples:** a proposal from a client's request, each morning's pickup list, replies to the questions customers ask most, *and more.*

**Visual.** Four small icons beside the four points: calendar, list, magnifier, person.

**Narration.** The heading and the four points.

### 2.2 Practice: sort the tasks

**Question type.** Freeform drag-and-drop, 2 attempts, not on the results slide.

> A bakery owner wants to hand something off to Claude. Sort each task.

**Drop targets.** "Good first task" and "Later."

| Drag item | Correct target |
|---|---|
| Each morning, turn the new custom orders into a pickup list | Good first task |
| A Monday summary of last week's sales and orders | Good first task |
| Replies to "Do you do gluten-free?" and the other questions customers ask most | Good first task |
| Redo the whole website | Later |
| Write a marketing plan for next year | Later |
| Answer all customer email on its own, with nobody checking | Later |

**Feedback.**

- Correct: "Right. The good ones come up often, and she sees each one before a customer does."
- Try again: "Look for tasks that repeat and that she can check. Big one-time projects come later."
- Incorrect (attempt 2): show the correct sort, with "Big one-time projects, and anything that skips her check, come later."

**Accessibility.** Give each drop target alt text ("Drop area: Good first task"). Run a keyboard-only pass; if Storyline's keyboard drag-and-drop fails it, swap in a Pick Many with the same items.

### 2.3 Do it for real: name your task

**On-screen text.**

> # Your task
>
> What's the task you'll hand to Claude? Write it the way you'd say it.
>
> [text entry: "For example: write proposals from my client intake notes"]
>
> How often does it come up?
> ( ) Every day ( ) Every week ( ) Every month ( ) Less often
>
> [Continue]

**Layer: Not often** (Every month or Less often):

> A task that comes up often is easier to learn on, and it pays off sooner. Is there a daily or weekly one you could start with? You can come back to this one later.
>
> [Pick a different task] [Keep this one]

**Triggers.**

1. Every day / Every week / Every month / Less often: set MyFrequency = 1 / 2 / 3 / 4.
2. Continue, checked in this order:
   - if MyTask is blank: show "Write your task first." beside the field;
   - else if MyFrequency = 0: show "Pick how often it comes up.";
   - else if MyFrequency is 3 or 4 and NudgeSeen = False: set NudgeSeen = True, show layer Not often;
   - else jump to 2.4.
3. Pick a different task: hide the layer, set MyTask to blank, put focus on the text entry.
4. Keep this one: hide the layer, jump to 2.4.

**Accessibility.** The text entry's label is "Your task." The radio buttons are a button set with the label "How often does it come up?"

### 2.4 Check: step 1

**Question type.** Multiple choice, unlimited attempts, feedback by choice, not on the results slide. The next step opens only on the right answer.

> Which of these is the best first task to hand to Claude?

| Choice | Feedback |
|---|---|
| **Turn each week's crew notes into Monday's job schedule.** (correct) | Yes. It comes up every week, and you see it before your crew does. |
| Plan the business for next year. | A big one-time project, and hard to check. Start with something that repeats. |
| Answer every customer call from now on. | That skips your check. Start with a task you see before anyone else does. |

**Triggers.** Continue (on the correct layer): set S2Done = True, set CurrentSection = 3, jump to 3.1.

---

## Step 2: Give Claude the details

### 3.1 Learn: one folder and the details [N]

**On-screen text.**

> # Step 2: Give Claude the details of the task
>
> Claude Code works inside a folder on your computer. Make one for this task.
>
> Then tell Claude how you do it, the way you'd explain it to a new hire. Start with the steps, then add your rules and an example you were happy with.
>
> Type it in, or point Claude to files you already have. Share what this task needs. Passwords and card numbers stay with you.
>
> Claude writes what it learns into an instructions file, **CLAUDE.md**, and reads it every time it works in that folder.
>
> **The easy way to start:** ask Claude to interview you about the task, one question at a time.

**Visual.** A folder labeled "Proposals" with CLAUDE.md highlighted inside it, and a chat bubble from Claude: "How do you estimate hours for a remodel?"

**Narration.** Paragraphs one, two and four, then the easy way to start.

### 3.2 Practice: set up proposals for Cedar Row Architects

**Screen.** Eight cards on the left. Two areas on the right: "Share with Claude" and "Keep with you."

**Part 1: what to share.** Freeform Pick Many, 2 attempts, not on the results slide.

> Cedar Row Architects is setting up fee proposals in Claude Code. Select what Claude needs to know.

| Detail | Share? | Why (shown after submit) |
|---|---|---|
| How you estimate hours for each phase | Share | Every proposal starts with it. |
| Your fee schedule (fee-schedule.xlsx) | Share | Every rate in a proposal comes from here. |
| Your retainer, billing and scheduling policies | Share | Every proposal ends with them. |
| 3 past proposals you were happy with | Share | They show Claude how your proposals look and sound. |
| Clients' card numbers | Keep with you | A proposal works without them. |
| Your bank login | Keep with you | Passwords stay with you. |
| Last year's tax return | Keep with you | Proposals work without it. |
| Your staff's home addresses | Keep with you | Other people's details, and proposals work without them. |

**Part 2: finish the CLAUDE.md** (layer, after Part 1 is correct). Claude has interviewed the principal and drafted the file. A mock text editor shows it, with three choices to make. Each choice is a button set; the chosen line appears in the file.

```
# Cedar Row Architects: fee proposals

We're a three-person firm. We design homes, additions and remodels.
[TONE]
Use the rates in fee-schedule.xlsx.
[WHEN SOMETHING IS MISSING]
End every proposal with the retainer and billing terms from policies.docx.
[SAVING]
```

| Slot | Choices (correct first) | Feedback if wrong |
|---|---|---|
| Tone | **Write the way we talk to clients: friendly, plain and short.** / Write formally. / Use exciting sales language. | "Your clients know how you talk. Proposals should sound like you." |
| When something is missing | **If the intake notes leave something out, ask me before you write the proposal.** / Make your best guess. / Skip that part. | "A guess in a proposal becomes a fee you have to honor. Have Claude ask." |
| Saving | **Save each proposal as a draft for me to approve and send.** / Send each proposal when it's done. | "You approve every proposal before it goes out. That's step 3." |

[Check my file] shows Correct ("That's a good start. Claude reads this every time it works in the Proposals folder.") or highlights each slot that needs another look, with its feedback.

**Triggers.** Next is Disabled until Check my file passes. The three button sets set ToneChoice, MissingChoice, SaveChoice (1, 2, 3); Check my file passes when all three are 1.

**Accessibility.** Each slot's button set has a label ("Tone line", "When something is missing", "Saving"). The file preview is real text, so screen readers read the finished file.

### 3.3 Do it for real: tell Claude about your task

**On-screen text.**

> # Now in your own Claude Code
>
> Your task: **%MyTask%**
>
> 1. Make a folder for this task, and choose it in the Code tab.
> 2. Paste this prompt:
>
> > I'd like your help with a task I do often: %MyTask%. Interview me about how I do it, one question at a time. When you have what you need, write it into CLAUDE.md and show me.
>
> [Copy prompt]
>
> 3. Answer Claude's questions. If you already have a price list or past examples, tell Claude where they are.
> 4. Read the CLAUDE.md it writes, and correct anything that's off.
>
> - [ ] I made a folder and chose it in the Code tab.
> - [ ] I told Claude how I do the task.
> - [ ] I shared what the task needs, and kept passwords and card numbers to myself.
> - [ ] I read every line of the CLAUDE.md Claude wrote.
>
> What did you tell Claude about?
> [text entry: "For example: my rates and two past proposals"]

**Triggers.** Next is Disabled until all four boxes are Selected and MyDetails is not blank. Next: jump to 3.4.

**Accessibility.** The prompt is a text box readers can select. The Copy prompt button's accessible name is "Copy the prompt to your clipboard."

### 3.4 Check: step 2

**Question type.** Multiple choice, unlimited attempts, feedback by choice, not on the results slide.

> You're setting up a task for writing customer replies. What should you share with Claude?

| Choice | Feedback |
|---|---|
| **Your answers to the questions customers ask most, and two replies you were happy with** (correct) | Right. That's what Claude needs to write the way you do. |
| Your customer list, card numbers included | Replies work without card numbers. Share what the task needs. |
| Everything on your computer, so it has all it needs | More isn't better. Share what this task needs. |

**Triggers.** Continue (on the correct layer): set S3Done = True, set CurrentSection = 4, jump to 4.1.

---

## Step 3: Run it and check it

### 4.1 Learn: ask plainly, read the prompts, check the result [N]

**On-screen text.**

> # Step 3: Run the task and check the result
>
> **Ask for one thing, plainly.** Name the job, the details to use, and what to save: "Write a proposal for the Lee project from intake-notes-lee.txt using fee-schedule.xlsx. Save it as a draft."
>
> **Read every permission prompt.** Claude asks before it creates or changes a file. A new draft in your folder is a yes. Pause when it wants to change your fee schedule or anything outside the folder.
>
> **Check the result before you approve it.** Compare every number with your own details, then read for anything Claude promised or added on its own.

**Narration.** The three bold lines, with a short gloss of each.

### 4.2 Practice: ask and approve

**Screen.** The mock Claude Code screen with the Proposals folder open. The sidebar lists fee-schedule.xlsx, policies.docx, CLAUDE.md, three past proposals, and intake notes for Lee, Kim and Ortiz.

**Part A: the request.** "Pick the request you'd type." Three buttons:

| Request | Result |
|---|---|
| "Write a proposal." | Claude replies: "Which project? I see intake notes for Lee, Kim and Ortiz." Text: "Claude needs to know which project. Pick another request." The button goes Disabled. |
| **"Write a proposal for the Lee project from intake-notes-lee.txt using fee-schedule.xlsx and policies.docx. Save it as a draft called proposal-lee.md."** (correct) | Claude's activity lines appear: "Read intake-notes-lee.txt", "Read fee-schedule.xlsx", "Read policies.docx". Go to Part B. |
| "Write proposals for every project in the folder and email them to the clients." | Text: "That's three projects at once, and it skips your approval. One project, one draft, and you approve it. Pick another request." The button goes Disabled. |

**Part B: the first permission prompt.**

> **Claude wants to create a file:** proposal-lee.md
> [Allow] [Deny]

- Allow: go to Part C.
- Deny: "Claude needs this to save the draft. A new draft in your task folder is what you asked for." The learner picks again.

**Part C: the second permission prompt.**

> **Claude wants to edit a file:** fee-schedule.xlsx
> "Your fee schedule says $185 per hour for the principal. Your 2024 proposal for the Silva project used $170. Update the fee schedule to $170?"
> [Allow] [Deny]

- **Deny** (correct): "Right. Your fee schedule is the source. Old proposals can have old rates." Then [See the draft], which jumps to 4.3.
- **Allow:** set AllowedFeeEdit = True. "Claude changed your fee schedule to an old rate. Every proposal from now on would come out low. Undo it, and keep the fee schedule as your source." [Undo], then [See the draft], which jumps to 4.3.

**Accessibility.** Each permission card gets focus when it appears, and its accessible name starts with "Permission request."

### 4.3 Practice: check the draft

**Screen.** The mock Claude Code screen shows the draft proposal-lee.md. The draft is a set of segment buttons, one per line. The reference panel on the right has tabs for Notes, Fees and Policies. Below the draft: "Fixed: %FixedCount% of 3" and [Approve draft] (Disabled).

> Claude finished a draft. Check every line against the notes, fees and policies. Select any line that looks off.

**The draft.**

| Line | Text | Problem? |
|---|---|---|
| L1 | Proposal for the Lee residence: kitchen and family room remodel, design through the permit set | No |
| L2 | Principal: 10 hrs × $140 = $1,400.00 | **P1.** $140 is the project architect rate. The principal rate is $185. |
| L3 | Project architect: 32 hrs × $140 = $4,480.00 | No |
| L4 | Drafter: 56 hrs × $95 = $5,320.00 | No |
| L5 | Site visit to measure: 1 × $250 = $250.00 | No |
| L6 | Interior finish selections: included | **P2.** Not in the notes, and it's an optional service with a fee. Claude added it on its own. |
| L7 | Estimated fee: $11,450.00. Retainer to start (20%): $2,290.00. | Depends on L2 (see below) |
| L8 | You'll have your permit by March. | **P3.** The city sets permit timing. The policy is to send the design schedule once the retainer is in. |
| L9 | This proposal is good for 30 days. | No |

**Fix layers.** Selecting L2, L6 or L8 opens its fix layer: "Fix this line," three choices in a button set, [Apply fix] and [Cancel]. A wrong choice shows its feedback and the learner tries again. The right choice sets the line to Fixed, adds 1 to FixedCount and closes the layer.

**P1 (L2).** When fixed, L7 also changes to its Corrected state: "Estimated fee: $11,900.00. Retainer to start (20%): $2,380.00."

| Choice | Feedback |
|---|---|
| **Principal: 10 hrs × $185 = $1,850.00** (correct) | (closes and marks Fixed) |
| Principal: 10 hrs × $170 = $1,700.00 | That's the old rate from the 2024 proposal. The fee schedule says $185. |
| Leave it. The rates are close. | Each role has its own rate. The principal's is $185. |

**P2 (L6).** The Fixed state reads "(Removed: interior finish selections, which the client didn't ask for.)" in muted italics.

| Choice | Feedback |
|---|---|
| **Remove the line.** (correct) | (closes and marks Fixed) |
| Interior finish selections: 8 hrs × $140 = $1,120.00, added to the fee | The client didn't ask for it. Leave it off their fee. |
| Keep it. Clients like extras. | It's a paid service on your fee schedule, and nobody asked for it. |

**P3 (L8).**

| Choice | Feedback |
|---|---|
| **The city sets permit timing. We'll send our design schedule once your retainer is in.** (correct) | (closes and marks Fixed) |
| We'll do our best to get your permit by March. | Softer, and still a promise about the city's timing. |
| Remove the line. | The client asked about timing, so answer it the way your policy does. |

**Lines that are fine** (L1, L3, L4, L5, L9): selecting one changes it to Checked, with a "Matches" tag, and adds 1 to FalseFlags if it wasn't already Checked.

**L7 before P1 is fixed:** a note appears under it: "The math adds up, but it's built on the principal line. Check that line." After P1 is fixed, selecting it shows "Matches."

**Approve draft:** changes to Normal when FixedCount = 3. Selecting it shows the Approved layer:

> # Approved
>
> You caught a wrong rate. Then you took out a service Claude added on its own, and replaced a promise about the city's timing with your policy.

Two text boxes have states shown by condition:

- If FalseFlags > 0: "You also checked %FalseFlags% lines that were fine. That's the job."
- If AllowedFeeEdit = True: "And remember the fee schedule: read every permission prompt before you allow it."

[Continue], which jumps to 4.4.

**Accessibility.** Focus order: the instruction, L1 to L9, the counter, Approve draft, then the reference tabs. Each line's accessible name is its text plus its state ("Fixed", "Matches"). On a fix layer, focus starts at "Fix this line," and Cancel returns focus to the line. No time limits.

**Rise reuse.** Publish 4.2 and 4.3 as their own small Storyline file for the Storyline block in the Rise refresher.

### 4.4 Do it for real: run your task

**On-screen text.**

> # Now run yours
>
> Your task: **%MyTask%**
>
> > Do %MyTask% for the next one that's due, using the details in this folder. Save it as a draft for me to approve.
>
> [Copy prompt]
>
> - [ ] I ran the task once in my own Claude Code.
> - [ ] I read every permission prompt before I allowed it.
> - [ ] I checked the result against my own details, line by line.
>
> What did it get wrong? Write "nothing" if it was all right.
> [text entry]

**Triggers.** Next is Disabled until all three boxes are Selected and MyProblem is not blank. Next: jump to 4.5.

### 4.5 Check: step 3

**Question type.** Multiple choice, unlimited attempts, feedback by choice, not on the results slide.

> While drafting a proposal, Claude asks: "Allow edit to fee-schedule.xlsx?" What do you do?

| Choice | Feedback |
|---|---|
| Allow it. It's in your folder. | Being in your folder doesn't make the change right. Every proposal depends on your fee schedule. |
| **Deny it, and find out why Claude wanted to change it.** (correct) | Right. A change to your fee schedule changes every proposal after it. |
| Allow it, and look at the fee schedule later. | By then the wrong rate may already be in a proposal. Read the prompt before you allow it. |

**Triggers.** Continue (on the correct layer): set S4Done = True, set CurrentSection = 5, jump to 5.1.

---

## Step 4: Update the instructions

### 5.1 Learn: put the fix in CLAUDE.md [N]

**On-screen text.**

> # Step 4: Update the instructions
>
> A fix made by hand stays in that one draft.
>
> Put the fix in CLAUDE.md, and it carries into every run after. A new session starts fresh, and CLAUDE.md loads every time.
>
> Tell Claude what was off and ask it to add a rule. Then run the task again and see if the rule worked.
>
> **Make the rule specific.** Say exactly what to do.
>
> | Vague | Specific |
> |---|---|
> | Be careful with rates. | Bill each role at its own rate from fee-schedule.xlsx. Check every rate before you total. |

**Narration.** The first three paragraphs and "Make the rule specific. Say exactly what to do."

### 5.2 Practice: three fixes

**On-screen text.**

> You approved the Lee proposal after fixing 3 problems. Now decide how to handle each one next time.

Three rows, one per problem. Each row has three buttons in a button set, in this authoring order (shuffle the order across rows so the specific rule isn't always in the same spot). Claude's reply appears under the row when a choice is made.

| Problem | Hand fix (Fix = 3) | Vague rule (Fix = 2) | Specific rule (Fix = 1) |
|---|---|---|---|
| 1. Principal billed at the wrong rate | Fix the draft by hand. | Add a rule: "Be careful with rates." | Add a rule: "Bill each role at its own rate from fee-schedule.xlsx. Check every rate before you total." |
| 2. Added a service on its own | Fix the draft by hand. | Add a rule: "Keep proposals simple." | Add a rule: "Include the services in the intake notes. List anything else under Optional services, with its fee." |
| 3. Promised a permit date | Fix the draft by hand. | Add a rule: "Be careful with dates." | Add a rule: "For timing, say the city sets permit timing and we'll send our design schedule once the retainer is in." |

**Claude's replies** (a text box under each row, with one state per choice):

- Hand fix: "You fixed it in the draft. CLAUDE.md stays the same."
- Either rule: "Added to CLAUDE.md:" followed by the rule.

> You'll see how these hold up on the next project, in step 5.

No right or wrong is shown here. The consequence plays out on 6.3.

**Triggers.**

1. Each button sets its row's variable (Fix1, Fix2 or Fix3) to 1, 2 or 3, and changes the reply box to the matching state.
2. When the timeline starts: change the state of Next to Disabled.
3. When Fix1, Fix2 and Fix3 are all not 0: change the state of Next to Normal.
4. Next: jump to 5.3.

**Accessibility.** Each row is a button set with a label ("Fix for problem 1: principal billed at the wrong rate"). The reply boxes are announced because focus moves to each one after a choice.

### 5.3 Do it for real: add your first rule

**On-screen text.**

> # Now update yours
>
> What was off in your run: **%MyProblem%**
>
> > Add a rule to CLAUDE.md that handles this next time: %MyProblem%. Make it specific, and show me the new rule.
>
> [Copy prompt]
>
> Then run the task again. If it was all right the first time, run it on another one and add a rule for anything you had to fix.
>
> - [ ] Claude added a rule to my CLAUDE.md, and I read it.
> - [ ] I ran the task again, and the rule worked.
>
> The rule you added:
> [text entry]

**Triggers.** Next is Disabled until both boxes are Selected and MyRule is not blank. Next: jump to 5.4.

### 5.4 Check: step 4

**Question type.** Multiple choice, unlimited attempts, feedback by choice, not on the results slide.

> Claude's proposals keep adding services the client didn't ask for. What's the best fix?

| Choice | Feedback |
|---|---|
| Delete the extras by hand each time. | That fixes this proposal. On the next one they come back. |
| Add to CLAUDE.md: "Be more careful." | Careful about what? A vague rule leaves Claude guessing. |
| **Add to CLAUDE.md: "Include the services in the intake notes. List anything else under Optional services."** (correct) | Right. It's specific, and it loads every time. |

**Triggers.** Continue (on the correct layer): set S5Done = True, set CurrentSection = 6, jump to 6.1.

---

## Step 5: Save it

### 6.1 Learn: save it as a skill [N]

**On-screen text.**

> # Step 5: Save it for next time
>
> Once the task comes out right, ask Claude to save the steps as a **skill**: a saved set of steps with a short name.
>
> Next time, type the name, like **/proposal**, and the intake notes file. Claude starts from the same steps and the same instructions.
>
> **Your part stays the same:** read the result, then approve it.

**Narration.** The first three paragraphs.

### 6.2 Practice: save the skill

**Screen.** The mock Claude Code screen, after the approved Lee proposal.

> Pick the request that saves this task the right way.

| Request | Result |
|---|---|
| "Remember this for next time." | Claude: "Got it." Text: "That leaves out what to save and what to call it. Pick another request." The button goes Disabled. |
| **"Save what we just did as a skill called proposal. It should read the intake notes file I give it, use fee-schedule.xlsx and the rules in CLAUDE.md, and save the proposal as a draft for me to approve."** (correct) | A permission prompt: "Claude wants to create a file: .claude/skills/proposal/SKILL.md" with Allow (correct) and Deny. Allowing shows a short preview of the skill file, then "Saved. Next time, type /proposal and the intake notes file." |
| "Send a proposal to every new client automatically." | Text: "That skips your approval. Every proposal still goes past you. Pick another request." The button goes Disabled. |

**Skill file preview** (monospace, abbreviated):

```
---
name: proposal
description: Write a fee proposal from a project's intake notes
---
1. Read the intake notes file the principal names.
2. Use the rates in fee-schedule.xlsx and the rules in CLAUDE.md.
3. Save the proposal as a draft named proposal-<client>.md.
4. Leave it as a draft. The principal approves and sends every proposal.
```

**Triggers.** [The next project] appears after the skill is saved and jumps to 6.3.

### 6.3 Practice: the next project [N]

**Screen.** The mock Claude Code screen. A banner: "A new project comes in. New session." The learner selects the message box, which fills in `/proposal intake-notes-kim.txt`, then [Send].

**Sequence.**

1. Activity lines: "Read intake-notes-kim.txt", "Read fee-schedule.xlsx", "Read CLAUDE.md".
2. Permission prompt: "Claude wants to create a file: proposal-kim.md" [Allow] [Deny]. Allow continues; Deny explains as on 4.2.
3. The draft proposal-kim.md appears as segment buttons, with the reference panel showing the Kim notes, fees and policies.

**When the timeline starts** (in this order):

1. Set KimProblems = 0. Add 1 to KimProblems if Fix1 is not 1. Add 1 if Fix2 is not 1. Add 1 if Fix3 is not 1.
2. Set the states of K2, K6, K7 and K8 from Fix1, Fix2 and Fix3 (table below).

**The draft.**

| Line | If the specific rule was added in step 4 | If it wasn't (hand fix or vague rule) |
|---|---|---|
| K1 | Proposal for the Kim residence: detached garage with a studio above, design through the permit set | (same) |
| K2 (Fix1) | Principal: 14 hrs × $185 = $2,590.00 | **Problem:** Principal: 14 hrs × $140 = $1,960.00 |
| K3 | Project architect: 40 hrs × $140 = $5,600.00 | (same) |
| K4 | Drafter: 60 hrs × $95 = $5,700.00 | (same) |
| K5 | Site visits: 2 × $250 = $500.00 | (same) |
| K6 (Fix2) | Hidden | **Problem:** 3D renderings: included |
| K7 (Fix1) | Estimated fee: $14,390.00. Retainer to start (20%): $2,878.00. | Estimated fee: $13,760.00. Retainer to start (20%): $2,752.00. |
| K8 (Fix3) | The city sets permit timing. We'll send our design schedule once your retainer is in. | **Problem:** We can guarantee your permit by June. |
| K9 | This proposal is good for 30 days. | (same) |

K7 isn't a separate problem: it follows from the principal line, so it corrects itself when K2 is fixed, as L7 did on 4.3.

**Checking.** On screen: "New project, new session. Check it the same way: every line against the notes, fees and policies."

- Selecting a problem line opens a two-choice fix layer:
  - "Fix it by hand again." Feedback: "That's what happened on the Lee proposal. Add the rule so the fix carries forward."
  - **"Add the specific rule to CLAUDE.md, then fix this draft."** (correct) The line changes to Fixed and KimFixed goes up by 1. If it was K2, K7 changes to its correct state too.
- Selecting a line that's fine shows "Matches." Selecting K7 while K2 is still off shows: "The math adds up, but it's built on the principal line. Check that line."
- A checkbox: "I checked every line against the details."
- [Approve draft] becomes Normal when KimFixed = KimProblems and the checkbox is Selected.

Approve draft jumps to 6.4.

**Narration.** The banner and the instruction only.

**Accessibility.** Same as 4.3. Hidden lines (K6 when Fix2 = 1) are hidden objects, so they're left out of the focus order.

### 6.4 How your fixes held up

**On-screen text.**

> # How your fixes held up

One row per problem. The "Next project" column is a text box with two states, picked from the Fix variable.

| Problem | What you did in step 4 | Next project |
|---|---|---|
| Wrong rate | (hand fix / vague rule / specific rule, from Fix1) | Held: the rate was right. / Came back: principal billed at $140 again. |
| Added a service | (from Fix2) | Held: nothing extra. / Came back: 3D renderings "included." |
| Promised a permit date | (from Fix3) | Held: timing handled the policy's way. / Came back: "guarantee your permit by June." |

A closing line with three states, from KimProblems:

- 0: "All three held. Specific rules in CLAUDE.md carry a fix forward."
- 1 or 2: "Your specific rules held. The others came back: a hand fix stays in one draft, and a vague rule leaves Claude guessing."
- 3: "All three came back: a hand fix stays in one draft, and a vague rule leaves Claude guessing. Now they're specific rules, and they carry forward."

**Triggers.** Next: jump to 6.5.

### 6.5 Do it for real: save yours

**On-screen text.**

> # Save yours
>
> Your task: **%MyTask%**
>
> Pick a short name for it, like *proposal* or *morning-summary*: [text entry]
>
> > Save what we just did as a skill called %MySkill%. It should use the details and rules in this folder and save a draft for me to approve.
>
> [Copy prompt]
>
> - [ ] Claude saved the skill.
> - [ ] I ran it once with /%MySkill%, and checked the result.
> - [ ] I put a reminder in my calendar for when it's due.
>
> When will you run it? For example: every morning, or every Monday.
> [text entry]

**Triggers.** Next is Disabled until MySkill is not blank, all three boxes are Selected, and MyWhen is not blank. Next: jump to 6.6.

**Accessibility.** Both text entries have labels: "Skill name" and "When will you run it?"

### 6.6 Check: step 5

**Question type.** Multiple choice, unlimited attempts, feedback by choice, not on the results slide.

> Your /proposal skill works. What's your part each time?

| Choice | Feedback |
|---|---|
| Nothing. It runs itself now. | Saving makes the task quick to start. Your approval is still the last step. |
| **Run /proposal, check the draft against your details, then approve it.** (correct) | Right. Claude does the drafting, and you approve every proposal before it goes out. |
| Look at the total only. | A right total can still promise a permit date or add a service. Check every line. |

**Triggers.** Continue (on the correct layer): set S6Done = True, set CurrentSection = 7, jump to 7.1.

---

## Final check

### 7.1 Final check [N]

> # Final check
>
> 6 questions, drawn at random from a set of 10, two from each step. Get 5 right to pass (80%). If you need another try, retry with a new set. Each question tells you why after you answer.
>
> [Start]

### 7.2 Question draw

Draw 6 at random from the "Final check" bank. Each question: multiple choice, 1 attempt, feedback by choice, answers shuffled, 10 points. Set the draw slide to "When revisiting: Reset to initial state" so a retry draws a new set.

### 7.3 Results

Results slide, tracking only the 7.2 draw. Passing score 80%.

- **Success layer:** "You passed. You scored %Results.ScorePercent%%." [Review answers] [Continue]. Continue: set S7Done = True, set CurrentSection = 8, jump to 8.1.
- **Failure layer:** "Not yet. You scored %Results.ScorePercent%%. You need 80%. Look over the questions you missed, then retry with a new set." [Review answers] [Retry]. Retry: reset the results, jump to 7.2.

### Final check question bank

**Q1 (step 1).** A landscaper wants to hand something to Claude. Which first task fits best?

| Choice | Feedback |
|---|---|
| **Turn each week's crew notes into Monday's job schedule.** | Right. It repeats, and the owner sees it before the crew does. |
| Decide whether to open a second location. | A big one-time decision. Start with something that repeats. |
| Answer every customer call from now on. | That skips the owner's approval. |

**Q2 (step 1).** Why start with one task instead of five?

| Choice | Feedback |
|---|---|
| **One task gets finished, and you learn the steps on it.** | Right. After the first one, the next goes faster. |
| Claude can only do one task at a time. | It can do many. Starting with one is about you finishing something. |
| Five tasks cost more. | Cost isn't the reason. Focus is. |

**Q3 (step 2).** What should you give Claude for writing fee proposals?

| Choice | Feedback |
|---|---|
| **Your fee schedule and policies, plus a few past proposals you were happy with** | Right. That's what you'd hand a new hire. |
| Every file on your computer, so Claude has everything | More isn't better. Share what the task needs. |
| Only last month's proposal | One example is a start, and the rates need to come from your fee schedule. |

**Q4 (step 2).** What is CLAUDE.md for?

| Choice | Feedback |
|---|---|
| **Standing instructions Claude reads every time it works in that folder** | Right. It's where your rules live. |
| A log of everything Claude did | It's instructions you and Claude write, not a log. |
| Your client list | Keep client details out unless the task needs them. |

**Q5 (step 3).** Which request will get the best first draft?

| Choice | Feedback |
|---|---|
| "Write a proposal." | Claude has to ask which project and which details. |
| **"Write a proposal for the Lee project from intake-notes-lee.txt using fee-schedule.xlsx. Save it as a draft."** | Right. One project, the details to use, and what to save. |
| "Write proposals for all the projects and send them." | Too much at once, and it skips your approval. |

**Q6 (step 3).** A draft proposal looks right at a glance. What do you check before you approve it?

| Choice | Feedback |
|---|---|
| **Each rate and hour count against your details, then anything it promised or added** | Right. A proposal can look fine and still carry a wrong rate or a promise you can't keep. |
| The spelling | Spelling matters least. Check the numbers and promises first. |
| Nothing. Claude checked it. | You know your rules best. Yours is the check that counts. |

**Q7 (step 4).** You fixed a wrong rate in the draft by hand. What happens next time?

| Choice | Feedback |
|---|---|
| **The same mistake can come back, because the instructions stayed the same.** | Right. Put the fix in CLAUDE.md so it loads every time. |
| Claude remembers your fix. | A new session starts fresh. A hand fix stays in that one draft. |
| Nothing. One fix is enough. | One fix covers one draft. A rule covers every one after it. |

**Q8 (step 4).** Which rule will work best in CLAUDE.md?

| Choice | Feedback |
|---|---|
| "Be careful with dates." | Careful how? It leaves Claude guessing. |
| **"For timing, say the city sets permit timing and we'll send our design schedule once the retainer is in."** | Right. It says exactly what to do. |
| "Dates matter." | True, and it gives Claude nothing to do. |

**Q9 (step 5).** What does saving the task as a skill give you?

| Choice | Feedback |
|---|---|
| **The same steps and instructions, ready whenever you need them** | Right. It's quick to start, and you still approve the draft. |
| Proposals that send themselves | The skill saves a draft, and you approve it. |
| A guarantee of no mistakes | Nothing guarantees that. Your approval is still the last step. |

**Q10 (step 5).** Your skill has run well for a month. Then a client points out a wrong rate on a proposal. What do you do first?

| Choice | Feedback |
|---|---|
| **Send the client a corrected proposal, then update the rule that let the wrong rate through.** | Right. Fix what the client has first, then fix the instructions, same as step 4. |
| Stop using Claude. | A mistake you can trace is a rule you can add. |
| Delete the skill and write proposals by hand again. | You'd lose the steps that work. Update the rule that let this through. |

---

## Wrap

### 8.1 Your one-task plan [N]

**On-screen text.**

> # Your one-task plan
>
> **Your task:** %MyTask%
> **What you told Claude:** %MyDetails%
> **The rule you added:** %MyRule%
> **Your skill:** /%MySkill%
> **When you'll run it:** %MyWhen%
>
> **Each time:** run it, read every line, approve it. When something's off, update the instructions.
>
> [Print my plan] [Download the job aid (PDF)]

A callback text box with two states, from HookChoice:

- HookChoice 1 to 4: "At 8:04 p.m. you reached for one of the big things. Now you have a task set up and saved."
- HookChoice = 5: "At 8:04 p.m. you picked one task. Now it's set up and saved."

**Narration.** "Here's your plan. Each time: run it, read every line, approve it. When something's off, update the instructions."

**Triggers.**

1. Print my plan: a JavaScript trigger runs `window.print()`.
2. Download the job aid: open the attached file `one-task-job-aid.pdf` (packaged with the published output).
3. Next: jump to 8.2.

**Accessibility.** The plan is real text in reading order. The download button's accessible name is "Download the job aid, PDF, 1 page."

### 8.2 Two quick questions: worth it?

**Question type.** Survey, Pick One, not scored and not on the results slide. Survey answers go to the LMS with the course data.

> # Two quick questions
>
> Was this course worth your time?
>
> ( ) Yes ( ) Somewhat ( ) Not really
>
> [Submit]

**Triggers.** Submit: jump to 8.3. A [Skip] button also jumps to 8.3.

### 8.3 Two quick questions: hardest step

**Question type.** Survey, Pick One, not scored and not on the results slide.

> Which step was hardest?
>
> ( ) 1. Pick one task that repeats
> ( ) 2. Give Claude the details of the task
> ( ) 3. Run the task and check the result
> ( ) 4. Update the instructions
> ( ) 5. Save it for next time
>
> [Submit]

**Layer: Thanks** (after Submit): "Thanks. That helps us improve the course." [Exit]

**Triggers.**

1. Submit: show layer Thanks.
2. A [Skip] button shows layer Thanks too.
3. Exit: exit the course.

**Accessibility.** Each set of choices is a button set labeled with its question. Skip and Submit are both reachable by keyboard.

---

## What the sample proves (scope check)

| The scope's "must prove" item | Where |
|---|---|
| Real Storyline interactions: variables, triggers, states, layers, conditional branching | Section bar states, text entry carried through the course, the Kim draft's states driven by step 4 choices (6.3), permission prompt layers (4.2), JavaScript copy and print triggers |
| Rise done cleanly, and when to use Rise vs Storyline | The Rise refresher (outline made); the case study explains the split |
| Scenario-based, performance-focused design | 4.2, 4.3, 5.2 and 6.3: decisions with consequences that play out on the next project |
| Assessment with meaningful feedback, and tracking | Five gate questions, the 10-question bank with feedback on every choice, two reaction questions (8.2, 8.3), SCORM 2004 |
| Accessibility built in and documented | Accessibility notes on every slide, the list below, and the conformance note (plan step 9) |
| Clean visual design with a consistent system | Visual system above; one reusable mock-screen layout |
| Responsible AI use, with the checks shown | The whole course: checking output line by line, reading permission prompts, sharing what the task needs, a person approves every draft. Plus the AI-use log in the case study |

## Publishing and tracking

- **LMS output:** SCORM 2004 4th edition, tracked by the 7.3 results slide.
- **SCORM Cloud test:** fail once, retry, then pass; close mid-course and relaunch to test resume, and check the typed answers came back. Screenshot the registration report.
- **Web output:** HTML5 for the portfolio.
- **Review 360:** one link for recruiters.
- **Rise block:** the separate file for 4.2 and 4.3.
- **Reviewers:** a recruiter can click through the "Do it for real" checklists in seconds. The checklists are the accountability for real learners; the practice is what a reviewer comes to see.

## Accessibility build list

- Name every slide; screen readers announce the slide title.
- Set the focus order on every slide. The slides above list it where it isn't plain top to bottom.
- Alt text on every meaningful image; hide decorative images and icons that sit beside text labels.
- Every text entry and button set has a label.
- Captions created from the TTS on every [N] slide; read them once for errors.
- Every status uses an icon plus a word.
- All text colors meet 4.5:1 (table under Visual system).
- Every interaction works with Tab, Enter and Space. Run a keyboard-only pass, then a screen reader pass (NVDA on Windows, VoiceOver on the published web output).
- No time limits anywhere.

## Assets

| Asset | Where | Source | Alt text |
|---|---|---|---|
| Kitchen table at night with a laptop (photo) | 1.1 | Content Library 360 | Decorative (the scene is described in the text) |
| Sticky notes | 1.1 | Storyline shapes | Real text |
| Step icons: calendar, list, magnifier, person, folder | 2.1, 3.1 | Content Library 360 icons | Decorative (each has a text label) |
| Problem, Fixed, Matches, Locked, Done icons | Throughout | Content Library 360 icons | Decorative (each has a text label) |
| Mock Claude Code screen, cards, text editor | 3.2, 4.2, 4.3, 6.2, 6.3 | Built from Storyline shapes | Real text |
| Job aid PDF | 8.1 | To write: "One task, start to finish" | Tagged, accessible PDF |