Orchestre Quick Reference

How to Use MCP Prompts

In Claude Desktop/Code, Orchestre prompts appear with the MCP protocol format:

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

Prompt Cheat Sheet

Project Setup & Planning

# Create new project with template
/orchestre:create (MCP)
# Arguments: template, projectName, targetPath, editor
# Example: makerkit-nextjs my-saas . claude

# Create from custom repository  
/orchestre:create (MCP)
# Arguments: repository URL as template, projectName, targetPath, editor
# Example: https://github.com/org/repo my-app . claude

# Add Orchestre to existing project
/orchestre:initialize (MCP)
# Arguments: path (optional), editor
# Example: . claude

# Analyze requirements and create plan
/orchestre:orchestrate (MCP)
# Arguments: requirements (file path or text)
# Example: requirements.md

Development & Execution

# Execute specific development task
/orchestre:execute-task (MCP)
# Arguments: task description
# Example: "Add user authentication with OAuth"

# Create SaaS MVP quickly
/orchestre:compose-saas-mvp (MCP)
# Arguments: requirements
# Example: "Project management tool with teams and billing"

# Generate implementation tutorial
/orchestre:generate-implementation-tutorial (MCP)
# Arguments: project description or folder path
# Example: "AI-powered code review platform"

Enterprise & Production

# Run security audit
/orchestre:security-audit (MCP)
# Arguments: scope (optional: full, dependencies, code, infrastructure)
# Example: full

# Add enterprise features
/orchestre:add-enterprise-feature (MCP)
# Arguments: feature (audit-logs, sso, rbac, data-export, compliance)
# Example: sso

# Migrate to multi-tenancy
/orchestre:migrate-to-teams (MCP)
# Arguments: strategy (optional: shared-db, db-per-tenant, hybrid)
# Example: shared-db

Knowledge Management

# Document a feature
/orchestre:document-feature (MCP)
# Arguments: feature name, format (optional: technical, user, api)
# Example: "authentication-system" technical

# Analyze existing codebase
/orchestre:discover-context (MCP)
# Arguments: focus (optional: architecture, patterns, decisions, all)
# Example: architecture

Code Quality

# Multi-LLM code review
/orchestre:review (MCP)
# Arguments: files/patterns (optional: recent changes if empty)
# Example: src/*.js or "." for recent changes

Command Arguments Reference

Required vs Optional Arguments

Prompt	Required Arguments	Optional Arguments
create	template, editor	projectName, targetPath
initialize	editor	path
orchestrate	requirements	-
execute-task	task	-
compose-saas-mvp	requirements	-
generate-implementation-tutorial	description	-
security-audit	-	scope
add-enterprise-feature	feature	-
migrate-to-teams	-	strategy
document-feature	feature	format
discover-context	-	focus

Editor Options

• claude - Claude Desktop/Code
• windsurf - Windsurf IDE
• cursor - Cursor editor

Template Options

• makerkit-nextjs - Full-stack SaaS with Next.js
• cloudflare-hono - Edge-first API platform
• react-native-expo - Cross-platform mobile app
• Custom repository URL (e.g., https://github.com/org/repo)

Common Workflows

Starting a New SaaS Project

1. /orchestre:create (MCP)
   # Choose: makerkit-nextjs my-saas . claude

2. /orchestre:orchestrate (MCP)
   # Provide: "Multi-tenant SaaS with subscription billing"

3. /orchestre:execute-task (MCP)
   # Start with: "Set up authentication and user management"

Adding Enterprise Features

1. /orchestre:security-audit (MCP)
   # Run: full

2. /orchestre:add-enterprise-feature (MCP)
   # Add: sso

3. /orchestre:add-enterprise-feature (MCP)
   # Add: audit-logs

4. /orchestre:document-feature (MCP)
   # Document: "enterprise-features" technical

Converting to Multi-tenant

1. /orchestre:discover-context (MCP)
   # Analyze: architecture

2. /orchestre:migrate-to-teams (MCP)
   # Strategy: shared-db

3. /orchestre:execute-task (MCP)
   # Implement: "Update all queries for team isolation"

Tips for Effective Use

1. Always specify editor: The editor argument is required for setup commands
2. Use full paths: When referencing files, use relative or absolute paths
3. Be specific: More detailed task descriptions yield better results
4. Check context: Use discover-context before major changes
5. Document as you go: Use document-feature after completing features

Troubleshooting

Prompt Not Found

• Ensure Orchestre MCP server is running
• Restart Claude Desktop/Code
• Check server logs for errors

Missing Arguments

• Prompts will indicate which arguments are required
• Refer to the arguments reference above

Context Issues

• Run /orchestre:discover-context (MCP) to understand current state
• Check .orchestre/CLAUDE.md for project context
• Ensure template detection is working correctly