Demo-First Presentation Plan

Do it. Then explain why it worked.

Try It Live

Ask about structuring and executing live demos

explain

Click to ask:

Or ask your own question:

Press Cmd/Ctrl + Enter to submit

---

The Three Pillars

Everything we demo revolves around these:

Pillar	What	File
1. CLAUDE.md	Project context	./CLAUDE.md
2. Commands	Your workflows	.claude/commands/*.md
3. Rules	Always-on constraints	.claude/rules/*.md

"The difference isn't the prompt. The difference is the context."

---

Philosophy

OLD WAY: "Let me explain what Claude Code can do..."
NEW WAY: "Watch this." [does it] "Here's why that worked."

• Less slides, more terminal
• Less theory, more magic
• Demo first, demystify after
• Demo the Three Pillars live

---

Demo Flow (1 hour)

Structure

Demo	Pillar	Time
Clone-and-Go	CLAUDE.md	5 min
/plan command	Commands	10 min
/yolo run	Commands	15 min
Background Agents	(bonus)	5 min
Rules in Action	Rules	10 min
Custom Command	Commands	10 min
Full Monty	All Three	5 min

Demo 1: The Clone-and-Go (5 min)

What they see:

git clone https://github.com/bytesbysamu/claude-code-guide
cd claude-code-guide
claude

> "What can you do in this project?"

Claude responds knowing the project, commands, rules.

Demystify:

• "Claude read CLAUDE.md automatically"
• "The .claude/ folder has commands and rules"
• "Clone any repo with this setup, instant context"

---

Demo 2: The /plan Command (10 min)

What they see:

/plan add dark mode toggle to the docs site

Claude:

• Explores codebase (spawns Explore agent)
• Finds Docusaurus config
• Creates implementation plan
• Lists files to change
• Waits for approval

Demystify:

• Show .claude/commands/plan.md
• "This is just a markdown file"
• "You define the workflow once"

---

Demo 3: The /yolo Run (15 min)

What they see:

/yolo add a "copy code" button to all code blocks

Claude:

1. Plans it
2. Finds the right files
3. Implements
4. Runs build
5. Fixes errors
6. Shows diff
7. Waits for commit approval

Demystify:

• Show .claude/commands/yolo.md
• "allowed-tools: * means full access"
• "Still stops for approval before commit"

---

Demo 4: Background Agents (5 min)

What they see:

> Run the full test suite in background while we work on something else

> /tasks
[Shows running task]

> Meanwhile, find all TODO comments in the codebase
[Claude does this while tests run]

> /tasks
[Shows test results]

Demystify:

• "Subagents run in parallel"
• "Main context stays clean"
• "Check with /tasks anytime"

---

Demo 5: Rules in Action (10 min)

What they see:

> Add a new React component for user settings

Claude creates component with:

• standalone: true (from angular rule)
• Proper inject() pattern
• Observable naming with $

Then ask:

> Add a test for this component

Claude creates test with:

• AAA comments
• final var
• AssertJ assertions
• Fixture pattern

Demystify:

• Show .claude/rules/angular-frontend.md
• Show .claude/rules/java-testing.md
• "Rules are always on. No prompting needed."

---

Demo 6: Custom Command Creation (10 min)

What they see:

> Create a custom command /deploy that:
> 1. Runs build
> 2. Runs tests
> 3. Creates git tag
> 4. Pushes to remote

Claude creates .claude/commands/deploy.md

Then:

/deploy v1.0.0

Runs the whole workflow.

Demystify:

• Open the created file
• "You just taught Claude your deployment process"
• "Commit this, team has it forever"

---

Demo 7: The Full Monty (5 min)

Everything together:

/plan implement user preferences API endpoint

[Approve plan]

Implement it, following our backend rules

/review

/commit

Watch Claude:

• Plan with exploration
• Code with rules applied
• Review with checklist
• Commit with message

No demystify needed. It speaks for itself.

---

Backup Demos (if time/questions)

Web Search

> What's the latest way to do auth in Next.js 15? Search for current docs.

MCP Integration

> Connect to our GitHub repo and list open PRs

Hooks

// Show a hook that auto-formats on save

---

Key Messages (say between demos)

After Demo	Pillar	Say
Clone-and-Go	CLAUDE.md	"Pillar 1: CLAUDE.md. Claude reads it every session. The difference isn't the prompt. The difference is the context."
/plan	Commands	"Pillar 2: Commands. Instead of explaining your workflow every time, define it once."
/yolo	Commands	"Still Commands. Move fast, but don't break things."
Rules	Rules	"Pillar 3: Rules. Always-on constraints. You never ask for them."
Custom Command	Commands	"You just taught Claude. Commit it, team has it forever."
Full Monty	All Three	"CLAUDE.md for context. Commands for workflow. Rules for constraints. That's it."

---

What NOT to Do

• Don't read slides
• Don't explain before showing
• Don't apologize if something fails (debug live, it's teaching)
• Don't rush the magic moment

---

Setup Checklist

Before presentation:

• Clone fresh repo
• Terminal font size 18+
• Dark theme
• claude installed and logged in
• Network stable
• Backup demos ready (screenshots if offline)

---

The Closer

End with:

git clone https://github.com/bytesbysamu/claude-code-guide
cd claude-code-guide
claude

"Everything I showed you is in this repo. Clone it. Use it. Make it yours."

---

Timing Guide

Time	Demo	Duration
0:00	Clone-and-Go	5 min
0:05	/plan	10 min
0:15	/yolo	15 min
0:30	Background Agents	5 min
0:35	Rules in Action	10 min
0:45	Custom Command	10 min
0:55	Full Monty	5 min
1:00	Done	-

Flex time in /yolo if needed. Cut Background Agents if running long.