Presenter cheat sheets

One sheet per act, plus the intermission between Acts II and III; each prints on its own page. Anastasia leads Act I, the intermission, and Act IV; Emily leads Acts II and III. The workshop runs three hours: Act I 35 min, Act II 35, intermission 10, break 15 (the agent keeps working), Act III 35, Act IV 50. Times follow the step labels on each act's page.

◀ Workshop home

Act I · Passages · Twine

AnastasiaPaper · 35 min · act1-twine.html

They leave with: a paper prototype and a branching Harlowe story that uses at least one choice that counts.

Before

  • Index cards, string or yarn, tape, markers on every table.
  • twinery.org loads on the room Wi-Fi. Have the desktop app as a fallback.
  • Open files/twine/the-longarm.html in a browser to play, and import it into Twine once yourself (Library → Import).

Watch for

  • Lost work: browser Twine saves to that one browser. Say “Publish to File” early and often.
  • Orphan cards nothing links to. Ask: can a reader reach this?
  • Link typos make new empty passages. Spot the dashed-outline passages on the map.
  • Too many tiny branches: “Fewer, bigger choices.”

Run of show

0–101 · Paper prototypeStar card = Start. String from the clickable words. One full path to an ending.
10–152 · Open TwineNew story, keep Harlowe.
15–233 · Passages & links[[text->Passage]]. Follow the strings until every card is a passage.
23–304 · Choices that count(set:), (if:)/(else:), (either:). Demo The Longarm: try the “Go make tea” path.
30–355 · Play & publish, UnmakeBuild → Test shows variables. Publish to File.

Unmake (pick one)

Show: From Beyond (with John Murray, ELO 2015), a Twine story played on a sensor-equipped Ouija board, and Emily's BeadED Adventures, a STEM story whose solved puzzles earn real beads that go home as a bracelet: physical Twine, the cards and string taken further. Both photos are in the Unmake section of the act page.

“(either:) is a tiny grammar: one slot, a few options, a random pick. Hold onto that; Emily turns it into whole sentences next.”

Before handing off: ask everyone to rewrite the last passage of The Longarm with their own question; they come back to it in Act IV. Hand to Emily for Tracery.

Act II · Patterns · Tracery

EmilyTextile · 35 min (step 5 only if time) · act2-tracery.html

They leave with: their own Tracery grammar, plus a flat version saved as grammar.json for Act IV.

Before

  • The playground on the act page runs offline. Load starter, quilt blocks, and cryptex (flat) once to check.
  • Kate Compton's Tracery tutorial open in a tab to point people to.
  • files/tracery/generator.html open in a tab for the “put it somewhere” step.

Watch for

  • JSON errors: curly quotes from a word processor, a missing comma, or a comma after the last item. Most “it broke” moments are one of these.
  • ((symbol)) in the output means a #symbol# with no rule; check spelling.
  • One word showing up too often: it's in many lists, or its list is short.
  • Flat grammar: every list the same length, plain words only, no #rules# inside.

Run of show

0–51 · Read a grammarOpen with Mad Libs: the origin is the story with blanks, the labels are symbols, and the friend calling out words is the list of options. Point to Kate Compton's tutorial. Then #hashes# and modifiers .capitalize .a .s .ed.
5–132 · PlaygroundEdit live; regenerate.
13–233 · Grow three rulesTheir own words. Several sentence shapes. Regenerate twenty times.
23–284 · Remember a choice[maker:#name#]: load quilt blocks.
(if time)5 · Put it somewheregenerator.html, Flores's template, Blue Bots, Done Quick!
28–356 · Flatten it, UnmakeSave the flat version as grammar.json. Read a few aloud; cut words that break sentences.

Unmake (pick one)

“Every block is a rule. A printed ring can't expand a rule, so for Act IV every word on one ring has to work next to every word on the others.”

Check before moving on: everyone has grammar.json saved somewhere they can find it. Hand to Anastasia for the intermission.

Intermission · Demo: Claude Code as power tool

AnastasiaBetween Acts II and III · 10 min, then a 15-min break while it runs on its own

The point: show the power tool at full speed. We build something complicated together, then let it finish on auto mode while the room keeps making. Act IV is the slow, approve-every-step version of the same tool.

Before

  • Pick the build and test the opening prompt the night before. Not linked on the workshop site.
  • A repository and a Claude Code session open on the projector machine, signed in.
  • Power and a machine that won't sleep for the next hour.

Watch for

  • Plan with the room in plan mode, then switch to auto mode and say so out loud.
  • Leave the session visible or minimized but running; don't close the laptop.
  • If it stalls or asks a question, note it for Act IV rather than fixing it live.

Run of show

0–5Build the ask togetherTake suggestions from the room. Read the plan aloud before approving it.
5–10Hand it the wheelSwitch to auto mode. Let it start; show the first few steps.
10–25Break15 minutes. Leave the session running on screen so people can watch it work.
Act IIIIt keeps goingEmily teaches p5.js; the agent works.
Act IVCome backOpen it at the start of Act IV: what did it make, what did it decide, what broke?

“This is the computerized pantograph: we chose the pattern, and now the machine stitches edge to edge. We'll check the back of the quilt in Act IV.”

Hand back to Emily for p5.js.

Act III · Sketches · p5.js

EmilyZine · 35 min · act3-p5.html

They leave with: a p5.js sketch running their grammar, with a credit comment at the top.

Before

  • Everyone signs in to openprocessing.org (free account) before the act starts; it needs Wi-Fi. Make one test sketch from first-sketch.js yourself.
  • Your printed cryptex and flower spinner to pass around in step 4.
  • A way to print saved stills and make buttons from them (printer, paper, button maker).

Watch for

  • Blank canvas: the first red line in OpenProcessing's console names the line number.
  • Pasting the grammar: it replaces the whole grammarSource = { … } object, braces included.
  • Edited but nothing changed: press ▶ again.
  • Paste the whole .js file over the starter code; in tracery-particles.js, Tracery is the long part at the bottom, so leave it there.

Run of show

0–51 · First sketchOpenProcessing: Create a Sketch, paste first-sketch.js, ▶. Show the fork button on a course sample.
5–132 · setup & drawChange the TRY lines. S saves the canvas. Breaking it is part of it.
13–233 · Add your grammartracery-particles.js as a new sketch: paste over grammarSource; click to release lines. Press S to save stills: we print them as buttons.
23–314 · A grammar you can spinflower-spinner.js. Pass the prints around: what can the screen do that the print can't?
31–355 · Fork & credit, UnmakeCredit comment at the top: Parrish → ENG 6819 → here. Download the sketch for Act IV.

Unmake (pick one)

“A p5.js sketch is a plain text file. You can read it, keep it, and open it in ten years without anyone's permission.”

Set up the turn: “These prints started as sketches like yours. Anastasia's going to show you how to get from the grammar to the object, with an agent, while keeping the decisions yours.” Hand to Anastasia for Agents.

Act IV · Agents · Claude Code + OpenSCAD

AnastasiaGame · 50 min · act4-agents.html

They leave with: a GitHub repository with their grammar, a 3D preview, a .scad print file, and a process log ending in a label they'd sign.

Before

  • Ask people to make a free GitHub account early; it's the slowest step.
  • Your own repository ready to demo, with CLAUDE.md in place and a session open in claude.ai/code.
  • files/p5/cryptex-3d.html open with the flat grammar loaded.
  • OpenSCAD installed on the demo machine if you'll show F5/F6.

Watch for

  • Mode: auto mode has been the default since August. Have everyone switch to approving each step, and plan mode for the first two prompts.
  • No subscription: use the free chat route on the page (paste, copy files, upload by hand).
  • The agent “fixing” their words: point to the house rule “My words are mine.”
  • Pages not showing: Settings → Pages → main branch; give it a minute.

Run of show

0–50 · Choose your modeFirst, open the intermission build: what did auto mode do? Then freehand vs. pantograph.
5–151 · Set up a repositoryUpload grammar.json, the sketch, CLAUDE.md, process-log.md.
15–202 · House rulesEdit CLAUDE.md: which steps stay yours?
20–253 · Plan before codePlan mode: read the grammar back first. The prompt is the source.
25–304 · Check every sentenceScript lists broken sentences; they choose the fixes.
30–355 · Preview in 3Dcryptex-3d.html vs. the agent's own preview.
35–456 · Make it printableDownload .scad, F5/F6, export STL. No printer: cardboard tubes on a pencil.
45–507 · Credit & label, Unmake“Written by / Coded by / Printed by.” They write the last line of CREDITS.md.

Unmake (pick one)

“The agent can't feel a ring bind. You can. Noticing the thread break and deciding where to start again is your work.”

Close: bring back the question they wrote at the end of The Longarm in Act I, and ask who wants to read theirs.