Commands
Pitch Smith provides 24 commands organized into four namespaces by purpose. All commands are invoked as slash commands in your AI coding assistant (Claude Code).
Smart Entry Point
The recommended starting point is /pitchsmith. It detects your current state and presents context-aware options:
- No theme configured — guides you to brand setup
- No decks created — offers create options (full deck, single slide, use template)
- Deck in progress — continue building, build all, edit, or start new
- All slides complete — plan a new deck or edit existing slides
/pitchsmith
Meta Commands (/pitchsmith:)
Help and status commands for orientation and progress tracking.
| Command | Description |
|---|---|
/pitchsmith:help | Show all available commands |
/pitchsmith:status | Display unified slide queue status dashboard |
/pitchsmith:help
Lists all available Pitch Smith commands with descriptions, organized by namespace.
Usage:
/pitchsmith:help
Example output: A formatted table of all commands grouped by category (Create, Manage, Brand, Meta).
/pitchsmith:status
Displays the unified slide queue status dashboard showing all decks with progress indicators and workflow configuration state.
Usage:
/pitchsmith:status
What you see:
- Overview mode (default): All decks sorted by last modified, with progress bars and status icons
- Detail mode (after selecting a deck): Slide-by-slide list with status icons, truncated descriptions, and a NEXT marker on the first pending slide
- Single mode: Current single slide plan details when in single-slide mode
- Workflow configuration: Lists which workflows are ejected (customized) vs. using plugin defaults
Brand Commands (/pitchsmith:)
Theme and brand management commands for setting up and maintaining your visual identity.
| Command | Description |
|---|---|
/pitchsmith:setup | Create brand theme from assets |
/pitchsmith:theme | Display current theme summary |
/pitchsmith:theme-edit | Modify existing theme via feedback |
/pitchsmith:setup
Creates your brand theme by extracting design primitives from brand assets such as a website URL, PDF brand guide, or images.
Usage:
/pitchsmith:setup
What it does:
- Collects brand assets (website URL, uploaded files, or manual input)
- Extracts colors, typography, shapes, and personality
- Generates a
theme.jsonfile - Creates sample slides for visual validation
- Enters a feedback loop for refinement
Prerequisites: None. This is typically the first command you run.
/pitchsmith:theme
Displays your current theme summary with formatted sections showing colors (with ANSI color swatches), typography, shapes, and available templates.
Usage:
/pitchsmith:theme
Prerequisites: Theme must exist at .slide-builder/theme.json. Run /pitchsmith:setup first if no theme exists.
/pitchsmith:theme-edit
Modifies your existing theme using natural language feedback. Uses a gestalt feedback approach — describe what you want changed in plain language and the system interprets and applies the changes.
Usage:
/pitchsmith:theme-edit
Workflow phases:
- Load & Backup — Current theme displayed and saved to version history
- Collect Feedback — Describe changes in natural language
- Apply Changes — System updates theme primitives
- Regenerate Samples — 6 sample slides generated showing changes
- Validation Loop — Review and provide more feedback or approve
- Save & Update — Theme saved, templates regenerated if needed
Example feedback:
"Make the headings bolder and increase contrast"
"Use warmer colors for backgrounds"
"The typography feels too corporate, make it more modern"
Prerequisites: Theme must exist at .slide-builder/theme.json.
Create Commands (/pitchsmith:)
Day-to-day deck creation workflow commands for planning, building, and editing slides.
| Command | Description |
|---|---|
/pitchsmith:plan | Smart router — asks single slide or full deck |
/pitchsmith:plan-one | Plan a single slide |
/pitchsmith:plan-deck | Plan a full presentation deck |
/pitchsmith:build-one | Build the next slide (or single planned slide) |
/pitchsmith:build-all | Build all remaining slides in deck plan |
/pitchsmith:edit | Edit slide layout via natural language |
/pitchsmith:edit-plan | Edit an existing deck plan via instruction |
/pitchsmith:add-slide | Add a new slide to an existing deck |
/pitchsmith:animate | Generate animation build groups |
/pitchsmith:use-template | Instantiate a deck template |
/pitchsmith:refresh | Regenerate viewer and manifest |
/pitchsmith:plan
Smart planning router that detects whether you want to create a single slide or a full deck and routes you to the appropriate planning workflow.
Usage:
/pitchsmith:plan
Routes to: /pitchsmith:plan-one or /pitchsmith:plan-deck based on your response.
/pitchsmith:plan-one
Plans a single standalone slide. Creates a simplified plan file with description, template selection, and key points.
Usage:
/pitchsmith:plan-one
Output: A plan.yaml file in .slide-builder/single/ with slide description, suggested template, and key points.
/pitchsmith:plan-deck
Plans a full presentation deck through an adaptive discovery process. Collects audience, purpose, and content details, then generates a structured deck plan with agenda sections and individual slide definitions.
Usage:
/pitchsmith:plan-deck
Discovery phases:
- Freeform opener — describe your presentation in natural language
- Context extraction and gap analysis
- Adaptive follow-up questions
- Presentation setting and length confirmation
- Agenda and slide plan generation
Output: A plan.yaml file in .slide-builder/deck/{deck-name}/ with all slides defined.
/pitchsmith:build-one
Builds the next pending slide (or a specific slide) from the plan. Generates the HTML slide file using the selected template and theme.
Usage:
/pitchsmith:build-one
What it does:
- Identifies the next pending slide in the plan
- Loads the template and theme
- Generates the HTML slide content
- Saves the output file and updates the manifest
/pitchsmith:build-all
Builds all remaining pending slides in the deck plan sequentially.
Usage:
/pitchsmith:build-all
What it does: Iterates through all slides with status: pending and builds each one. Supports resume — if some slides are already built, only the remaining ones are processed.
/pitchsmith:edit
Edits an existing slide's layout and content via natural language prompts. Describe the changes you want and the system modifies the slide HTML accordingly.
Usage:
/pitchsmith:edit
Example prompts:
"Move the title to the left and add more whitespace"
"Change the background to dark mode"
"Make the bullet points larger and add icons"
/pitchsmith:edit-plan
Applies a targeted natural language edit to an existing deck plan (plan.yaml). Modifies the plan structure, slides, or metadata based on your instruction.
Usage:
/pitchsmith:edit-plan <instruction>
Examples:
/pitchsmith:edit-plan Make the opening more compelling
/pitchsmith:edit-plan Add a slide about ROI after slide 3
/pitchsmith:edit-plan Change the audience to technical decision-makers
/pitchsmith:add-slide
Adds a new slide to an existing deck plan. Prompts for slide details and inserts it at the specified position.
Usage:
/pitchsmith:add-slide
/pitchsmith:animate
Generates animation build groups for a slide. Build groups control the progressive reveal of elements during presentation mode.
Usage:
/pitchsmith:animate
/pitchsmith:use-template
Instantiates a deck template with new content. Starts from a predefined deck structure and customizes it for your specific presentation.
Usage:
/pitchsmith:use-template
/pitchsmith:refresh
Regenerates the viewer HTML and manifest file for the current deck. Useful after manual file edits or when the viewer is out of sync.
Usage:
/pitchsmith:refresh
Manage Commands (/pitchsmith:)
Catalog and template management commands for maintaining your slide and deck template libraries.
| Command | Description |
|---|---|
/pitchsmith:add-slide-template | Create a new slide template |
/pitchsmith:add-deck-template | Create a new deck template |
/pitchsmith:edit-deck-template | Edit slides in a deck template |
/pitchsmith:delete-deck | Delete a deck and all its files |
/pitchsmith:eject-workflow | Copy a workflow for customization |
/pitchsmith:list-overrides | Show ejected vs. default workflows |
/pitchsmith:optimize-instructions | Optimize workflow instructions |
/pitchsmith:update-brand-assets | Manage brand asset catalog |
/pitchsmith:add-slide-template
Creates a new slide template through a guided conversation. The template is added to your slide template catalog for use in future slides.
Usage:
/pitchsmith:add-slide-template
/pitchsmith:add-deck-template
Creates a new deck template through a guided conversation. Deck templates define a reusable slide sequence that can be instantiated with /pitchsmith:use-template.
Usage:
/pitchsmith:add-deck-template
/pitchsmith:edit-deck-template
Add, edit, remove, or reorder slides within an existing deck template.
Usage:
/pitchsmith:edit-deck-template
/pitchsmith:delete-deck
Deletes a deck and all its associated files (plan, slides, manifest, viewer).
Usage:
/pitchsmith:delete-deck
/pitchsmith:eject-workflow
Copies a workflow from the plugin to your local .slide-builder/workflows/ directory, allowing you to customize its behavior without modifying the plugin.
Usage:
/pitchsmith:eject-workflow <workflow-name>
Example:
/pitchsmith:eject-workflow build-one
This copies the build-one workflow to .slide-builder/workflows/build-one/, where you can modify its instructions. The local version takes priority over the plugin default.
/pitchsmith:list-overrides
Displays which workflows are ejected (customized locally) versus using plugin defaults.
Usage:
/pitchsmith:list-overrides
Output: A list of all workflows showing their status (ejected or default) and summary count.
/pitchsmith:optimize-instructions
Transforms workflow instruction files using best practices for AI prompt engineering. Improves clarity, structure, and effectiveness of workflow instructions.
Usage:
/pitchsmith:optimize-instructions
/pitchsmith:update-brand-assets
Manages the brand asset catalog — add, remove, or update icons, logos, and images used in slide generation.
Usage:
/pitchsmith:update-brand-assets