delivery-classroom

Files (1)

• SKILL.md

SKILL.md (first lines)

# Delivery — Classroom

This skill adapts instructional design principles for synchronous, instructor-led classroom delivery of developer education. It covers live coding demonstrations, managing group dynamics, real-time pacing, immediate feedback loops, and engagement in shared learning spaces (physical or virtual).

## Features

- **Live Coding Demonstrations**: Structured instructor walkthroughs that show thinking, not just finished code
- **Real-Time Pacing**: Matching pace to group comprehension, reading the room, adjusting on the fly
- **Immediate Feedback**: Live Q&A, quick checks, pair feedback, and correction in the moment
- **Group Dynamics**: Managing participation equity, preventing dominance, building psychological safety
- **Engagement Strategies**: Polling, think-pair-share, live participation, discussion facilitation
- **Structured Breaks**: Strategic pauses protecting attention and enabling cognitive consolidation

## When To Use

- Designing instructor-led training, bootcamps, or courses
- Planning live coding sessions or technical workshops
- Preparing synchronous online classes (Zoom, Teams, etc.)
- Designing for in-person conference talks or training

## Guidelines

### Session Structure (General)
- [ ] Clear learning objectives stated at the start
- [ ] 15-20 min max for any single segment before interaction/break
- [ ] Mix of instructor input, guided practice, independent work
- [ ] Closing recap with next steps and resources
- [ ] Time explicitly reserved for Q&A

### Live Coding Demonstrations
- [ ] Code typed live, not pasted (shows real-time thinking)
- [ ] Mistakes introduced and debugged on the fly (models error recovery)
- [ ] Narrate the "why" behind each step (think-aloud protocol)
- [ ] Use version control or clear state transitions so learners can follow
- [ ] Avoid scripts—allow for improvisation and tangential questions
- [ ] Project code on large screen with high contrast, large font (minimum 16-18pt)
- [ ] Pause frequently for questions; silence is OK
- [ ] Record sessions so learners can replay at their pace

### Real-Time Pacing

**Signs you're going too fast**:
- Confused faces, lack of note-taking, few questions
- Learners asking "wait, what was that?"
- Multiple hands raised with similar clarification questions

**Signs you're going too slow**:
- Fidgeting, side conversations, checking phones
- Early finishers waiting passively
- Questions veering off-topic (sign of attention drift)

**Pacing strategies**:
- Poll the room: "How many followed that? Show with fingers 1-5."
- Graduated complexity: easy example → slightly harder → challenging extension
- Offer parallel tracks mentally: "If you're comfortable, try X; otherwise stick with Y"
- Build in 5-minute buffer before hard deadline for recap/catch-up

### Immediate Feedback Loops

- [ ] Frequent quick checks: polls, thumbs up/down, raised hands
- [ ] Normalize mistakes: "Let me break this on purpose to show the error"
- [ ] Pair-and-share model: "Turn to your neighbor and explain what just happened"
- [ ] Open Q&A with no penalty: "Any question? It probably helps 3 others"
- [ ] Live chat moderation (for virtual): monitor for confusion, answer publicly
- [ ] Post-activity: "What was confusing? Raise your hand or chat"

### Group Dynamics & Inclusion

**Preventing dominance**:
- [ ] Intentional hand-raising process: wait, give thinkers time, go to non-dominant hands first
- [ ] Structured turn-taking: "We'll hear from 3 people, then move on"
- [ ] Breakout rooms: pair or small-group discussion before whole-group sharing
- [ ] Think-pair-share: solo reflection → pair discussion → share (avoids cold-calling)
- [ ] Written responses: poll or chat allows introverts to participate without verbal pressure

**Building psychological safety**:
- [ ] Model mistakes early: "I usually forget the import statement too"
- [ ] Normalize struggle: "This is legitimately hard; confusion is the learning"
- [ ] Use "we" language: "We're learning this together"
- [ ] Respond to wrong answers constructively: "Good thinking; here's where it diverges"
- [ ] No ridicule or rushed corrections; frame errors as valuable insights

**Accessibility & Neurodiversity**:
- [ ] Captions/transcripts available (especially for neurodivergent learners processing audio)
- [ ] Visual + auditory: slides, code, whiteboarding, not audio-only
- [ ] Advance warning of cold-calling or surprise activities (ADHD, autism)
- [ ] Option to engage via chat/written response (not just verbal)
- [ ] Quiet breaks: "Mute video, grab water, no pressure to engage for 5 min"
- [ ] Recording available so learners can process asynchronously

### Engagement Strategies

**Think-Pair-Share Protocol**:
1. **Think** (2 min): Individual reflection or problem-solving
2. **Pair** (3-4 min): Discuss with neighbor or breakout partner
3. **Share** (5 min): Volunteers report back to whole group
- Dramatically increases participation vs. cold-calling

**Live Polling**:
- Multiple-choice question displayed; learners vote via hand, chat, or tool
- Show results, discuss the misconceptions revealed
- Use to diagnose where the group is struggling
- "Most said B—let's trace why that's incorrect"

**Pair Programming in Real-Time** (for coding workshops):
- Screen share: one codes, other navigates (provides direction, spots bugs)
- Swap every 5-10 minutes
- Instructor circulates, asks questions, unblocks pairs
- Reduces performance anxiety; distributed expertise

**Whiteboarding & Sketching**:
- Visual representation of abstract concepts (especially for kinesthetic learners)
- Problem-solving before code: flowchart, pseudocode, data structure sketch
- Reduce cognitive load by externalizing thinking

### Breaks & Consolidation

- [ ] 10-minute break every 50-60 minutes (not just at meals)
- [ ] 5-minute micro-breaks every 15-20 minutes (shift position, look away)

From caraya/agent-skills, MIT.

More from caraya/agent-skills