/showroom:create-demo

🎬 Demo Content Creation

Create presenter-led demo content where YOU present and customers watch.

Is This The Right Skill?

Use create-demo when

YOU present, customers watch

  • Like presenting PowerPoint — you drive
  • You want Know → Show structure
  • One presenter showing features
Use create-lab instead when

Customers DO hands-on activities

  • Customers click buttons, run commands
  • Multiple participants following step-by-step
💡
Not sure? Demos are presentational (you drive). Labs are interactive (customers drive).

What You’ll Need Before Starting

Required Inputs

🎯

Demo Topic

Example: "OpenShift AI capabilities"

⭐

Key Features

Features to highlight

📊

Number of Sections

Typically 3–4 segments

👥

Target Audience

Technical, business, or executive

What The AI Will Create

✅
Generated Files:
  • Navigation page (index.adoc)
  • Section files (one per demo segment)
  • Know/Show structure for each section
  • Presenter notes and customer-facing content
ℹ️
You DON'T need: Git knowledge, coding experience, or AsciiDoc expertise. The AI handles all technical aspects.

Quick Start

  1. Open Your IDE

    Launch Claude Code (or VS Code with Claude extension)

  2. Invoke Skill

    Type /showroom:create-demo in the chat

  3. Answer Questions

    Provide demo title, description, technologies, sections, and audience level

  4. Review & Customize

    Add screenshots and customize content

What It Creates

content/modules/ROOT/
├── pages/
│   ├── index.adoc              # Navigation home
│   ├── section-01.adoc         # First section
│   ├── section-02.adoc         # Second section
│   └── section-03.adoc         # Third section
└── partials/
    └── _attributes.adoc        # Demo metadata

Common Workflow

  1. Invoke Skill

    ``` /showroom:create-demo → Skill loads prompts from showroom/prompts/ ```

  2. Demo Details

    Answer prompts for demo title, abstract, technologies, audience level, and number of sections.

  3. Provide Showroom Repository Path

    Skill asks for your Showroom repo. You can provide a local path or a GitHub URL — the skill auto-clones GitHub URLs to /tmp/:

    ``` # Local path ~/work/showroom-content/your-demo-showroom # GitHub URL (auto-cloned to /tmp/your-demo-showroom) https://github.com/rhpds/your-demo-showroom ```

  4. Showroom Scaffold (site.yml + ui-config.yml)

    Skill configures the two key infrastructure files:

    ``` site.yml # Antora playbook — fix title, ui-bundle theme ui-config.yml # Split view + tabs (view_switcher.enabled: true) ```
    ℹ️
    Showroom 1.5.3+ required for split-view and OCP console embedding. Clone from showroom_template_nookbag as your starting template.

  5. Generate Section Content

    Skill generates index.adoc and one file per demo section using Know/Show structure. UserInfo attributes are written once in _attributes.adoc.

  6. Verify Content

    ``` /showroom:verify-content → Check quality and standards ```

  7. Generate Blog Post (Optional)

    ``` /showroom:blog-generate → Transform to blog format ```

Section Structure Pattern

Know → Show

Each section follows this proven demonstration pattern:

📖

Know Section

  • Explains what you'll demonstrate
  • Provides context and business value
  • Sets up the "why"
👁️

Show Section

  • Step-by-step demo script
  • What to click/type/show
  • Expected results and talking points
  • Screenshots with annotations

Tips & Best Practices

📊

Section Count

Start with 3–4 sections for new demos

⏱️

Timing

Each section should take 5–10 minutes

🎯

Focus

Keep Show sections focused on one main feature

📝

Presenter Notes

Include timing and transition notes

📸

Screenshots

Use screenshots to guide the flow

🎬

Practice

Run through demo before presenting

Troubleshooting

Skill not found? - Restart Claude Code or VS Code - Verify installation: `ls ~/.claude/skills/create-demo` (Claude Code) or `ls ~/.cursor/skills/showroom-create-demo` (Cursor) - Check the [Troubleshooting Guide](../reference/troubleshooting.html)
Generated content looks wrong? - Check your demo template is up to date - Verify you're in the correct directory - Run `/showroom:verify-content` to check standards compliance
Demo vs Lab confusion?
💡
Quick Decision Guide:
  • Use /showroom:create-demo for presenter-led content (Know/Show)
  • Use /showroom:create-lab for hands-on workshops (Know/Do/Check)
Think: "Am I showing, or are they doing?"

/showroom:verify-content

Validate generated content

/showroom:create-lab

Create hands-on workshops instead

/showroom:blog-generate

Convert to blog post format
← Back to Skills Next: /showroom:verify-content →