Orchestre Prompts Reference

Welcome to the Orchestre prompts reference documentation. This section provides comprehensive information about Orchestre's MCP prompt-based architecture and how to use it effectively.

MCP Prompt System

Orchestre uses the Model Context Protocol (MCP) to provide dynamic prompts that adapt to your project context. When using Claude Desktop/Code:

• Type / to see all available commands
• Orchestre prompts appear as /orchestre:[command] (MCP)
• Example: /orchestre:create (MCP), /orchestre:orchestrate (MCP)

How MCP Prompts Work

Unlike traditional slash commands, MCP prompts:

• Are served dynamically by the Orchestre MCP server
• Adapt their behavior based on project context
• Can access resources and tools as needed
• Update instantly when Orchestre is updated

The 20 Essential Prompts

📘 Project Setup (3 prompts)

• /orchestre:create (MCP) - Initialize new projects with templates
• /orchestre:initialize (MCP) - Add Orchestre to existing projects
• /orchestre:orchestrate (MCP) - Analyze requirements and create plans

🚀 Development & Execution (4 prompts)

• /orchestre:execute-task (MCP) - Execute specific development tasks
• /orchestre:compose-saas-mvp (MCP) - Rapid SaaS prototyping
• /orchestre:generate-implementation-tutorial (MCP) - Generate comprehensive implementation tutorials
• /orchestre:task-update (MCP) - Update task tracking files to reflect progress

🏢 Enterprise & Production (3 prompts)

• /orchestre:security-audit (MCP) - Comprehensive security scanning
• /orchestre:add-enterprise-feature (MCP) - Add enterprise-grade features
• /orchestre:migrate-to-teams (MCP) - Convert to multi-tenant architecture

📚 Knowledge Management (7 prompts)

• /orchestre:document-feature (MCP) - Create contextual documentation
• /orchestre:discover-context (MCP) - Analyze and understand existing code
• /orchestre:research (MCP) - Research technical topics and best practices
• /orchestre:extract-patterns (MCP) - Extract patterns from existing codebase
• /orchestre:status (MCP) - Show comprehensive project status with insights
• /orchestre:update-memory (MCP) - Update project contextual memory and documentation
• /orchestre:update-project-memory (MCP) - Intelligently update project docs to current Orchestre state

🔍 Code Quality (1 prompt)

• /orchestre:review (MCP) - Multi-LLM consensus code review

🛠️ Additional Commands (2 prompts)

• /orchestre:setup-parallel (MCP) - Set up parallel development with Git worktrees
• /orchestre:template (MCP) or /orchestre:t (MCP) - Execute template-specific commands

Reference Documents

📘 API Reference

Complete reference for all 20 Orchestre prompts including:

• Detailed argument specifications
• Resource inclusions
• Response formats
• Usage examples

🚀 Quick Reference

Fast lookup guide with:

• Prompt cheat sheet
• Common workflows
• Argument quick reference
• Template-specific commands

📝 Memory Templates

Reference for Orchestre's distributed memory system:

• Memory structure overview
• Template specifications
• Usage by commands
• Customization guide

🎯 Common Patterns

Real-world usage patterns including:

• Project initialization patterns
• Development workflows
• Production readiness patterns
• Anti-patterns to avoid

🔧 Resource Reference

Complete guide to Orchestre's resource system:

• URI scheme documentation
• Available resource types
• Content examples
• Custom resource creation

Quick Start Examples

# Create a new project
/orchestre:create (MCP)
# Then provide: makerkit-nextjs my-saas . claude

# Analyze and plan a feature
/orchestre:orchestrate (MCP)
# Then provide: "Multi-tenant SaaS with subscription billing"

# Execute a development task
/orchestre:execute-task (MCP)
# Then provide: "Implement user authentication with OAuth"

# Add enterprise features
/orchestre:add-enterprise-feature (MCP)
# Then provide: sso

Key Concepts

Dynamic Context Adaptation

Orchestre prompts automatically adapt based on:

• Your project's template (MakerKit, Cloudflare, React Native)
• Existing code patterns and architecture
• Project phase (MVP, scaling, production)
• Previously documented decisions in CLAUDE.md files

Resource Access

Prompts can access contextual resources:

• Memory Resources: Project knowledge and history
• Pattern Resources: Best practices and implementations
• Template Resources: Template-specific components
• Context Resources: Current working state

Intelligent Orchestration

Each prompt:

• Discovers your project context
• Adapts its approach based on findings
• Leverages MCP tools when needed
• Updates project memory for future reference

Getting Help

1. Check the Quick Reference: For fast command lookup
2. Review Common Patterns: For workflow examples
3. Consult API Reference: For detailed specifications
4. Explore Memory Templates: For documentation structure

Version Compatibility

• Orchestre Version: 5.0.0+
• Claude Desktop/Code: Latest version with MCP support
• Supported Editors: claude, windsurf, cursor

See Also

• Architecture Overview
• MCP Prompts Architecture
• Installation Guide