/orchestre:create (MCP)

Initialize a new Orchestre project with intelligent template selection and complete development environment setup.

Note: For existing projects, use /orchestre:initialize (MCP) instead.

Overview

Purpose: Smart project initialization
Category: Core Orchestration
Type: Dynamic prompt
MCP Tool: initialize_project

Syntax

bash

/orchestre:create (MCP) [template] [project-name] [path]
/orchestre:create (MCP) [repository-url] [project-name] [path]
/orchestre:create (MCP) . [template]  # Initialize in current directory

Parameters

Parameter	Required	Description	Options
`template`	Yes*	Template to use	`makerkit`, `cloudflare`, `react-native`
`repository-url`	Yes*	Git repository URL	Any valid Git URL
`project-name`	Yes**	Name of the project	Alphanumeric + hyphens or `.` for current dir
`path`	No	Target directory	Relative or absolute path

*Either template or repository-url is required **Use . as project-name to initialize in current directory

Usage Examples

Basic Project Creation

bash

# Create a SaaS application
/orchestre:create (MCP) makerkit my-saas-app

# Create an edge API
/orchestre:create (MCP) cloudflare edge-api

# Create a mobile app
/orchestre:create (MCP) react-native mobile-app

Custom Repository

bash

# Clone from a custom repository
/orchestre:create (MCP) https://github.com/makerkit/next-supabase-saas-kit-turbo my-saas

# Clone from private repository (requires Git authentication)
/orchestre:create (MCP) https://github.com/your-org/private-template my-project

Current Directory

bash

# Initialize template in current directory
/orchestre:create (MCP) . makerkit

# Initialize from custom repo in current directory
/orchestre:create (MCP) . https://github.com/user/template

What Happens

When you run /orchestre:create (MCP), the command:

Validates Input - Checks project name and template
Creates Structure - Sets up directory hierarchy
Installs Template - Copies template files
Configures Project - Sets up configuration
Installs Commands - Adds template-specific commands
Creates Documentation - Initial CLAUDE.md files

Template Selection

MakerKit (SaaS)

Best for:

Multi-tenant SaaS applications
Subscription-based products
Team collaboration tools
B2B platforms

Includes:

Authentication system
Billing integration
Team management
Admin dashboard

Cloudflare (Edge)

Best for:

High-performance APIs
Globally distributed apps
Serverless functions
Real-time applications

Includes:

Workers setup
KV storage
Durable Objects
R2 configuration

React Native (Mobile)

Best for:

Cross-platform mobile apps
Native mobile experiences
Offline-first applications
Mobile companions to web apps

Includes:

Expo configuration
Navigation setup
Native modules
Push notifications

Command Behavior

Discovery Phase

The command first explores:

Current directory structure
Existing projects
Available templates
System requirements

Execution Phase

typescript

// Internal flow
1. Call initialize_project tool
2. Create project structure
3. Copy template files
4. Install dependencies
5. Set up git repository
6. Create initial documentation

Output

🎭 Creating new Orchestre project...
📋 Template: makerkit
📁 Location: ./my-saas-app
✅ Project structure created
📚 Template files copied
🔧 Configuration complete
📖 Commands installed: 15
🎯 Knowledge pack ready

Next steps:
1. cd ./my-saas-app
2. Review CLAUDE.md for project context
3. Create requirements.md with your specifications
4. Run: /orchestrate requirements.md

Post-Creation

Immediate Next Steps

Navigate to Project
bash
```
cd ./my-saas-app
```
1
Review Documentation
- Read CLAUDE.md for template overview
- Check .orchestre/prompts.json for available prompts
Define Requirements
- Create requirements.md
- Describe your specific needs
Start Development
bash
```
/orchestrate requirements.md
```
1

Project Structure

After creation:

my-saas-app/
├── .orchestre/
│   ├── prompts.json      # Available prompts
│   ├── CLAUDE.md         # Orchestration memory
│   ├── patterns/         # Code patterns
│   └── memory-templates/ # Documentation templates
├── src/                  # Source code
├── tests/               # Test files
├── docs/                # Documentation
├── CLAUDE.md            # Project context
├── package.json         # Dependencies
└── README.md           # Human documentation

Best Practices

1. Choose Descriptive Names

bash

# Good names
/create makerkit customer-portal
/create cloudflare analytics-api
/create react-native fitness-tracker

# Poor names
/create makerkit app
/create cloudflare api
/create react-native myapp

2. Understand the Template

Before creating:

Review template features
Check included packages
Understand conventions
Consider requirements fit

3. One Project at a Time

Create and set up one project before starting another:

bash

/create makerkit project-1
cd project-1
# Set up and verify
cd ..
/create cloudflare project-2

Error Handling

Common Errors

Error	Cause	Solution
`Invalid project name`	Special characters	Use only letters, numbers, hyphens
`Template not found`	Typo in template	Check available templates
`Directory exists`	Name conflict	Choose different name
`Permission denied`	No write access	Check directory permissions

Recovery

If creation fails:

Check error message
Fix the issue
Delete partial creation
Run command again

Advanced Usage

Custom Target Directory

bash

# Specify location (coming soon)
/create makerkit my-app --target ./projects/saas/my-app

Template Inspection

Before creating, explore templates:

bash

# View available templates
/status templates

# Research template features
/research "MakerKit Next.js features"

Batch Setup

For multiple related projects:

bash

# Create workspace
mkdir my-workspace && cd my-workspace

# Create projects
/create cloudflare api-gateway
/create makerkit admin-portal
/create react-native mobile-client

Integration with Other Commands

Typical Workflow

Command Chaining

bash

# Initialize and plan
/create makerkit my-app && cd my-app && /orchestrate "E-commerce platform with subscriptions"

# Quick start
/create cloudflare api && /execute-task "Create health check endpoint"

Prompt Adaptation

This prompt dynamically adapts based on:

Context Discovery

Current Directory: Checks if already in a project
Available Templates: Discovers installed templates
Git Status: Understands repository state
System Capabilities: Adapts to OS and tools available

Intelligence Patterns

Detects existing projects to prevent conflicts
Suggests appropriate templates based on description
Adapts initialization for monorepo vs standalone
Configures based on detected development environment
Learns from previous project setups

Template Intelligence

Each template brings its own command set
Commands are discovered, not hardcoded
Adapts to template-specific conventions
Evolves as templates are updated

Memory Integration

This prompt actively uses and updates distributed memory:

Creates

CLAUDE.md - Root project context
.orchestre/CLAUDE.md - Orchestration memory
.orchestre/prompts.json - Available prompts configuration
.orchestre/templates/ - Memory templates
docs/[feature]/CLAUDE.md - Feature contexts

Initializes

Project philosophy and principles
Technical stack decisions
Development conventions
Team structure (if specified)

Memory Templates

Each template includes memory structures
Pre-configured for common patterns
Extensible for project specifics
Git-tracked for team sharing

Template Commands

Each template adds specialized prompts:

MakerKit Commands

/add-feature - Add new features
/setup-stripe - Configure payments
/add-team-feature - Multi-tenancy
See all 22 commands →

Cloudflare Commands

/add-worker-cron - Scheduled jobs
/add-r2-storage - Object storage
/implement-queue - Message queuing
See all 10 commands →

React Native Commands

/add-screen - New screens
/add-offline-sync - Offline capability
/setup-push-notifications - Push setup
See all 9 commands →

Direct Invocation

This is a dynamic prompt that Claude executes directly:

bash

# Simply type the command
/create makerkit my-saas

# Claude will:
# 1. Call the initialize_project MCP tool
# 2. Create complete project structure
# 3. Install template-specific prompts
# 4. Initialize distributed memory
# 5. Set up development environment

Tips and Tricks

Quick Validation

Validate project name before creation:

javascript

// Valid: letters, numbers, hyphens
const valid = /^[a-z0-9-]+$/.test(projectName);

Template Comparison

Not sure which template?

bash

/research "Compare MakerKit vs Cloudflare for SaaS development"

Clean Restart

If you need to start over:

bash

rm -rf ./my-app
/create makerkit my-app

/initialize command - For existing projects
initialize_project tool - Underlying MCP tool
/orchestrate command - Next step after creation
Templates Guide - Detailed template documentation
Getting Started - First project tutorial

/orchestre:create (MCP) ​

Overview ​

Syntax ​

Parameters ​

Usage Examples ​

Basic Project Creation ​

Custom Repository ​

Current Directory ​

What Happens ​

Template Selection ​

MakerKit (SaaS) ​

Cloudflare (Edge) ​

React Native (Mobile) ​

Command Behavior ​

Discovery Phase ​

Execution Phase ​

Output ​

Post-Creation ​

Immediate Next Steps ​

Project Structure ​

Best Practices ​

1. Choose Descriptive Names ​

2. Understand the Template ​

3. One Project at a Time ​

Error Handling ​

Common Errors ​

Recovery ​

Advanced Usage ​

Custom Target Directory ​

Template Inspection ​

Batch Setup ​

Integration with Other Commands ​

Typical Workflow ​

Command Chaining ​

Prompt Adaptation ​

Context Discovery ​

Intelligence Patterns ​

Template Intelligence ​

Memory Integration ​

Creates ​

Initializes ​

Memory Templates ​

Template Commands ​

MakerKit Commands ​

Cloudflare Commands ​

React Native Commands ​

Direct Invocation ​

Tips and Tricks ​

Quick Validation ​

Template Comparison ​

Clean Restart ​

Related ​

/orchestre:create (MCP)

Overview

Syntax

Parameters

Usage Examples

Basic Project Creation

Custom Repository

Current Directory

What Happens

Template Selection

MakerKit (SaaS)

Cloudflare (Edge)

React Native (Mobile)

Command Behavior

Discovery Phase

Execution Phase

Output

Post-Creation

Immediate Next Steps

Project Structure

Best Practices

1. Choose Descriptive Names

2. Understand the Template

3. One Project at a Time

Error Handling

Common Errors

Recovery

Advanced Usage

Custom Target Directory

Template Inspection

Batch Setup

Integration with Other Commands

Typical Workflow

Command Chaining

Prompt Adaptation

Context Discovery

Intelligence Patterns

Template Intelligence

Memory Integration

Creates

Initializes

Memory Templates

Template Commands

MakerKit Commands

Cloudflare Commands

React Native Commands

Direct Invocation

Tips and Tricks

Quick Validation

Template Comparison

Clean Restart

Related