# Keep Building

You finished the workshop with a working, personalized, published game.
Here's what to do with that.

---

## Right where you left off

Your project still has everything it had during the workshop — the full
game, both learning scenarios, and Claude Code ready to keep working with
you. Nothing expires. Open the folder, open Claude Code (desktop app or
`claude` in a terminal — whichever you used Sunday), and keep going
whenever you want. Questions about how any of this works? Check `FAQ.md`
first.

## The second scenario

This game shipped with **two** complete learning scenarios built in as
data, not just one:

- **Phishing inbox** — Bob's email, three tells to spot.
- **HIPAA redaction** — a form with three pieces of protected health
  information to catch before it goes out.

If you only played one during the workshop, try the other:

> Switch the active scenario to the one I haven't tried yet.

Then look at how it's built. Both scenarios live in the same data shape in
`deadline-run.html` and are documented in `scenarios/phishing.md` and
`scenarios/hipaa.md` — that's your template for scenario #3.

## Ideas, ranked by ambition

**Small (an evening):**
- Write a third scenario using your own real content — a compliance topic,
  a process check, anything with "spot the three problems" bones. Point
  Claude at the existing scenario files as a pattern and describe your new
  one in plain English.
- Swap in different enemy names, colors, or dialogue lines throughout.
- Adjust the difficulty curve — coffee cost, enemy speed, timer length —
  and ask Claude to re-tune the balance so it's still winnable.

**Medium (a weekend):**
- Add a new player character. Bring your own sprite sheet (or generate one
  with an AI image tool), and ask Claude to wire it in alongside the
  existing hero.
- Add a short, story-integrated ending beat instead of the current results
  screen — a single follow-up question about what to do next, not a
  multiple-choice quiz. Keep it in Bob or Kate's voice.
- Build a second level with a different environment (a warehouse, a
  hospital floor, a call center) reusing the same engine.

**Bigger (an ongoing project):**
- Package this for your LMS. Ask Claude Code to help you understand what a
  SCORM package needs and build a wrapper around this game — the game
  itself doesn't need to change, just how it's delivered.
- Build a small library of 60-second scenario games across a whole training
  curriculum, all sharing this same engine.
- Turn this into a template you reuse for every new compliance topic that
  comes across your desk.

## Where to get more assets

- **Characters and enemies:** `source-assets/` in this folder has the raw
  exports the current sprites were packed from — useful as a reference for
  what a new character or enemy sprite sheet needs to look like.
- **AI image/sprite generation:** if you want to create new characters or
  enemies from scratch, any AI image tool that can produce a consistent
  character across multiple poses works — ask Claude Code how to prep the
  output into a proper sprite sheet once you have the frames.
- **Document mockups** (for a new scenario): any design tool works — the
  game just needs a PNG and a set of click-region coordinates in
  `hotspots.json`, and Claude Code can help you generate those coordinates
  from a screenshot. Want the same authoring script Rachel used to build
  the two included documents? See `FAQ.md` — it's not in this folder by
  default, but ask Rachel about it (emdesigns.ai).

## How to reach Rachel

Building something with this and want a second set of eyes, or want a
version built around your own team's content?

**emdesigns.ai**

Rachel Weiss — Your AI Gamification Strategist