Skip to main content

Demo Scenarios

Live demo examples centered on the Three Pillars.

Try It Live

Ask about presenting and demonstrating Claude Code

explain

Press Cmd/Ctrl + Enter to submit

The Three Pillars Framework​

Every demo shows one or more pillars:

PillarWhatDemo Focus
CLAUDE.mdProject contextClone-and-Go, Before/After
CommandsYour workflows/plan, /review, /commit
RulesAlways-on constraintsCode patterns, test style

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

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

Pillar: CLAUDE.md

Goal: Show instant context from CLAUDE.md

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

"What can you do in this project?"

What happens:

  • Claude reads CLAUDE.md automatically
  • Knows the project, commands, rules
  • No setup explanation needed

Key message: "Pillar 1 is CLAUDE.md. Claude reads it every session. The difference isn't the prompt—the difference is the context."

Demo 2: The CLAUDE.md Difference (5 min)​

Pillar: CLAUDE.md

Goal: Show before/after with CLAUDE.md

Without CLAUDE.md​

"Add a new API endpoint for user preferences"
→ Claude asks: What framework? What patterns? Where?

With CLAUDE.md​

"Add a new API endpoint for user preferences"
→ Claude: Creates files in the right places, follows patterns

Key message: "Claude goes from guessing to knowing."

Try it Live​

CLAUDE.md Demo
beginner
📁 new-project/
📄 └── (empty)
*Initialized. No CLAUDE.md found.*
>
💡Without CLAUDE.md, Claude doesn't know your tech stack, patterns, or preferences.

Demo 3: The /plan Command (10 min)​

Pillar: Commands

Goal: Show workflow automation

/plan add dark mode toggle to the docs site

Claude:

  1. Explores codebase (spawns Explore agent)
  2. Finds relevant files
  3. Creates implementation plan
  4. Lists files to change
  5. Waits for approval

Demystify: Show .claude/commands/plan.md

Key message: "Pillar 2 is Commands. Instead of explaining your workflow every time, define it once."

Try it Live​

Commands Demo
beginner
📁 my-app/
📄 ├── CLAUDE.md✓
📁 └── .claude/commands/✓
*Initialized. Found CLAUDE.md, 1 command.*
>
💡Your /plan command tells Claude to explore first, plan second, and wait for approval.

Demo 4: Rules in Action (10 min)​

Pillar: Rules

Goal: Show automatic constraint enforcement

"Add a new component for user settings"

Claude creates code with:

  • Your component patterns
  • Your naming conventions
  • Your file structure

Then:

"Add a test for this component"

Claude creates test with:

  • Your test structure (AAA pattern)
  • Your assertion style
  • Your fixture patterns

Demystify: Show .claude/rules/*.md files

Key message: "Pillar 3 is Rules. Always-on constraints. You never ask for them."

Try it Live​

Rules Demo
beginner
📁 typescript-app/
📄 ├── CLAUDE.md✓
📁 └── .claude/rules/✓
*Initialized. Found CLAUDE.md, 2 rules.*
>
💡Your rules no-any.md and testing.md are loaded. Watch them get applied automatically.

Demo 5: Custom Command Creation (10 min)​

Pillar: Commands

Goal: Show teaching Claude your workflows

"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 use it:

/deploy v1.0.0

Key message: "You just taught Claude your process. Commit it, team has it forever."

Demo 6: The Full Monty (5 min)​

Pillar: All Three

Everything together:

/plan implement user preferences API endpoint

[Approve plan]

Implement it, following our backend rules

/review

/commit

Watch all three pillars work:

  • CLAUDE.md - knows the codebase
  • Commands - /plan, /review, /commit workflows
  • Rules - code patterns applied automatically

No explanation needed. It speaks for itself.

Presentation Flow (1 hour)​

TimeDemoPillarDuration
0:00Clone-and-GoCLAUDE.md5 min
0:05Before/AfterCLAUDE.md5 min
0:10/plan commandCommands10 min
0:20Rules in ActionRules10 min
0:30Custom CommandCommands10 min
0:40Full MontyAll Three5 min
0:45Q&A-15 min

Troubleshooting​

If demo fails​

  1. /clear - Reset context
  2. Debug live - "This is a teaching moment"
  3. Show the relevant .md file instead

If Claude is slow​

  • "Claude is exploring the codebase..."
  • Talk through what's happening
  • Show /tasks for background work

If output is unexpected​

  • "Great teaching moment!"
  • Show how to course-correct
  • "This is why checkpoints matter"

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. CLAUDE.md for context. Commands for workflow. Rules for constraints. Clone it. Use it. Make it yours."