Corporate Trainer

# CLAUDE.md — Corporate Trainer
> Version: 2026-02-17 | Difficulty: beginner

## What Your AI Can Now Do
- Design a complete workshop — agenda, activities, facilitator notes, and handouts — in 20 minutes instead of a full day
- Generate fresh exercises for any skill, group size, and time constraint on demand
- Build Kirkpatrick Level 1-4 evaluation materials automatically after every delivery
- Track which activities land with which audiences so your toolkit sharpens with every engagement
- Send pre-work to participants 5 days before delivery without manual follow-up

---

## Quick Start
1. Paste this file as `CLAUDE.md` in your training project root
2. Create your first workshop folder: `workshops/clients/[company]/`
3. Run `/workshop-design [topic] [audience] [duration]` to scaffold your next engagement
4. Add your best exercises to `workshops/activities/` so Claude can recommend them
5. After delivery, run `/evaluation [workshop]` to generate and send participant surveys

---

## About Me
Corporate trainer delivering 8-12 workshops per month on leadership, communication, and team dynamics. Clients range from 20-person startups to Fortune 500 organizations. 60% in-person, 40% virtual. Every workshop is customized — no two deliveries are identical.

---

## Pre-Built Commands

| Command | What It Does |
|---------|-------------|
| `/workshop-design [topic] [audience] [duration]` | Outputs timed agenda, learning objectives, activities with facilitator notes, debrief questions, and materials list |
| `/activity [skill] [group-size] [time]` | Generates a fresh exercise with setup instructions, facilitation guide, debrief questions, and variations |
| `/evaluation [workshop]` | Builds assessment materials covering reaction survey, knowledge check, 30-day behavior plan, and business impact metrics |
| `/needs-assessment [company]` | Creates a structured discovery template for understanding what the client actually needs before you design anything |
| `/pre-work [workshop]` | Generates and sends participant pre-work packet 5 business days before delivery |

---

## How Claude Connects to Your Tools

| Tool | Why You Need It |
|------|----------------|
| Google Workspace | Workshop docs, slide decks, client scheduling, shared handouts, and evaluation forms |
| Memory | Tracks which activities work with which audiences across all your engagements |
| Resend | Sends pre-work packets, post-workshop follow-ups, and evaluation survey links |

### Setup
```bash
# Required in .env
GOOGLE_WORKSPACE_CREDENTIALS=your-credentials
RESEND_API_KEY=your-api-key
MEMORY_STORAGE_PATH=./memory
```

---

## Training Design Rules
- **MUST:** Follow Tell-Show-Do-Review for every concept — introduce, demonstrate, let them practice, debrief
- **MUST:** Never lecture for more than 10 minutes — alternate format every 10 min or you lose the room
- **MUST:** Every concept needs a concrete application exercise — no theory without practice
- **SHOULD:** Breakout groups of 3-4 people max — larger groups create passengers
- **MUST:** Virtual delivery needs engagement every 7 minutes — poll, chat prompt, or annotation
- **SHOULD:** Design for the weakest participant — if they cannot do the exercise, the design failed
- **MUST:** Write facilitator notes as if a stranger will deliver the workshop tomorrow
- **SHOULD:** Debrief questions matter more than content slides — the learning happens in reflection

---

## Project Structure
```
workshops/
  clients/
    [company]/
      needs-assessment.md    # What they asked for vs what they actually need
      agenda.md              # Timed agenda with facilitator notes
      materials/             # Slides, handouts, exercise sheets
      results.md             # Post-delivery evaluation results
  templates/                 # Reusable workshop frameworks
    half-day.md
    full-day.md
    multi-session.md
  activities/                # Exercise library organized by skill
    leadership/
    communication/
    team-dynamics/
  evaluations/               # Survey templates and collected results
  handouts/                  # Participant-facing materials
```

### What These Folders Mean
- **clients/** — One subfolder per company engagement. Claude reads needs-assessment and past results before designing new workshops.
- **templates/** — Workshop structures by duration. Claude uses these as starting scaffolds.
- **activities/** — Your exercise library. Claude pulls from here when building agendas and suggests new exercises to fill gaps.
- **evaluations/** — Survey templates and historical results. Claude references past scores to improve future designs.
- **handouts/** — Participant materials. Claude generates these as part of workshop design.

---

## Automation

| When | What Happens | If It Fails |
|------|-------------|-------------|
| New workshop created | Auto-generates pre-work email and schedules send for 5 days before delivery | Run `/pre-work [workshop]` manually and send via email |
| Workshop date minus 24 hours | Sends facilitator checklist and materials reminder | Review the agenda file and print materials list yourself |
| Workshop completed | Triggers Level 1 evaluation survey to all participants | Send the evaluation link manually within 2 hours — response rate drops fast |
| 30 days post-workshop | Sends Level 3 behavior follow-up survey to participants and their manager | Set a calendar reminder to send the follow-up survey manually |
| Low evaluation scores flagged | Highlights activities that scored below 3.5/5 for replacement | Review `evaluations/` folder and compare against your activity library |

---

## Gotchas
- **MUST:** Never skip the needs assessment call — assumptions about "what they need" are wrong 80% of the time
- **MUST:** Send post-workshop surveys within 2 hours while energy is high — after 48 hours response rate drops to 30%
- **SHOULD:** Use "professional warm-ups" not ice-breakers — childish activities destroy credibility with senior leaders
- **MUST:** Virtual breakout rooms need written instructions on screen — verbal-only instructions create chaos every time
- **SHOULD:** If the room is quiet after a question, wait 7 full seconds — silence is processing, not failure
- **MUST:** Always end modules with: "What will you do differently starting Monday?" — transfer to work is the whole point

---

## Memory & Learning
Claude builds context over time:
- Which activities work best with specific audience types and seniority levels
- Client preferences, org culture notes, and recurring feedback themes
- Your facilitation style and timing patterns
- Evaluation scores by activity so weak exercises get flagged for replacement
- What debrief questions create the deepest reflection

To save something important: just say "remember that [fact]" in conversation.
To review saved memories: use the `/memory` command to open the memory editor.