/create - Smart Project Initialization

Purpose

The /create prompt initializes new projects using Orchestre's MCP tool with built-in templates or custom repositories. It sets up the complete Orchestre infrastructure including memory templates, commands, and project structure.

How It Actually Works

Parses Arguments: Extracts template/repository, project name, path, and editor
Shows License Notice: For MakerKit templates, displays commercial license requirement
Calls MCP Tool: Invokes mcp__orchestre__initialize_project to create project
Sets Up Infrastructure: Creates .orchestre/ folder, installs commands, initializes memory

Use Cases

Template-Based Projects: Start with pre-configured templates
Repository Cloning: Initialize from any Git repository
Editor-Specific Setup: Configure for Claude Code, Windsurf, or Cursor
Current Directory Init: Use "." to initialize in current location
Team Standards: Initialize with organizational templates

Argument Structure

/create <template|repository-url> <project-name> [target-path] <editor>

Arguments

template|repository-url (required)
- Built-in templates: cloudflare-hono, makerkit-nextjs, react-native-expo
- Repository URL: https://github.com/user/repo
- Use "." for current directory initialization
project-name (required)
- Name for your new project
- Derived from template/repo if not provided
- Use "." to skip project directory creation
target-path (optional)
- Where to create the project
- Defaults to current directory + project name
editor (required)
- Must be one of: claude, windsurf, or cursor
- Determines command installation location

Examples

bash

# Standard template creation
/create cloudflare-hono my-api claude

# With specific path
/create makerkit-nextjs my-saas ./projects/saas windsurf

# Custom repository
/create https://github.com/makerkit/next-supabase-saas-kit-turbo my-startup cursor

# Initialize in current directory
/create . makerkit-nextjs claude

# All parameters
/create cloudflare-hono my-api ./projects/api windsurf

MakerKit License Notice

For MakerKit templates (makerkit-nextjs, react-native-expo), you'll see:

📋 MakerKit License Required
MakerKit is a commercial product that requires a valid license.
Perpetual license - use forever once purchased
Build commercial applications, but not resell MakerKit
Visit makerkit.dev to purchase

Technical Details

MCP Tool Integration

The prompt calls mcp__orchestre__initialize_project with:

template: Template name or "custom" for repositories
projectName: Parsed or derived project name
targetPath: Target directory path
repository: Repository URL (if custom)
editor: Editor choice (claude/windsurf/cursor)

What Gets Created

Project Structure:
- Complete template or repository contents
- .orchestre/ directory with all subdirectories
- .claude/commands/ with installed prompts
- Initial CLAUDE.md files

Orchestre Infrastructure:

project/
├── CLAUDE.md                    # Project context
├── .orchestre/
│   ├── CLAUDE.md               # Orchestration memory
│   ├── prompts.json            # Available prompts
│   ├── commands-index.md       # Command reference
│   ├── templates/              # Memory templates
│   ├── knowledge/              # Discovery insights
│   ├── plans/                  # Development plans
│   ├── tasks/                  # Task tracking
│   └── sessions/               # Session history
└── .claude/
    └── commands/               # Installed prompt files

Template-Specific Setup:
- Dependencies installation
- Configuration files
- Example code and patterns
- Documentation

Memory Usage

Created Memory Structure

project/
├── CLAUDE.md                    # Project context
├── .orchestre/
│   ├── CLAUDE.md               # Orchestration memory
│   ├── templates/              # Memory templates
│   └── knowledge/              # Discovery insights
└── .claude/
    └── commands/               # Installed prompts

Memory Content

The prompt automatically documents:

Project purpose and goals
Technology choices and rationale
Initial architecture decisions
Setup configuration
Template customizations

Example Memory Entry

markdown

# Project: my-saas-app

## Setup
- Created: 2024-01-15
- Template: makerkit-nextjs
- Purpose: B2B SaaS platform for team collaboration

## Technology Stack
- Framework: Next.js 14 with App Router
- Database: Supabase (PostgreSQL)
- Authentication: Supabase Auth
- Payments: Stripe
- Styling: Tailwind CSS

## Initial Decisions
- Chose MakerKit for rapid SaaS development
- Using serverless architecture for scalability
- Implemented team-based multi-tenancy from start

Workflow Examples

SaaS Application Setup

bash

# 1. Create from MakerKit template
/create makerkit-nextjs acme-platform

# 2. Orchestrate development plan
/orchestrate "B2B platform for document collaboration with team workspaces"

# 3. Start implementation
/execute-task "Set up authentication with team invitations"

Custom Repository Workflow

bash

# 1. Clone company template
/create https://github.com/acme/saas-template team-portal

# 2. Discover existing patterns
/discover-context ./src

# 3. Add enterprise features
/add-enterprise-feature sso "Okta SAML integration"

Mobile App Creation

bash

# 1. Create React Native project
/create react-native-expo fitness-tracker

# 2. Plan mobile-specific features
/orchestrate "Fitness tracking app with offline support and health kit integration"

# 3. Implement core features
/execute-task "Set up offline data sync with SQLite"

Intelligent Features

Smart Defaults

Detects Node.js version requirements
Configures appropriate package managers
Sets up Git with proper .gitignore
Initializes with sensible linting rules

Dependency Resolution

Analyzes template dependencies
Checks for version conflicts
Suggests updates for security
Configures development tools

Environment Setup

Creates .env.example files
Documents required API keys
Sets up development databases
Configures local development

Error Handling

Common Issues

Directory Exists
- Prompt suggests alternative names
- Offers to initialize existing directory
- Provides cleanup instructions
Repository Access
- Handles private repository authentication
- Suggests SSH vs HTTPS setup
- Provides Git configuration help
Template Not Found
- Lists available templates
- Suggests similar alternatives
- Offers custom repository option

Recovery Strategies

The prompt includes recovery for:

Partial installations
Network failures
Permission issues
Dependency conflicts

Integration Points

With Other Prompts

→ /orchestrate: Natural next step for planning
→ /initialize: For existing projects
→ /discover-context: To understand cloned repos
→ /execute-task: To start development

With MCP Tools

Uses initializeProject tool
Configures installCommands automatically
Prepares for analyzeProject workflow
Sets up for generatePlan execution

Best Practices

Provide Context

bash

# Good: Clear purpose
/create makerkit-nextjs "ai-writing-assistant" "AI-powered content creation platform"

# Basic: Just names
/create makerkit-nextjs my-app

Use Descriptive Names

bash

# Good: Indicates purpose
/create cloudflare-hono api-gateway

# Vague: No context
/create cloudflare-hono backend

Consider Repository URLs

bash

# For team templates
/create https://github.com/company/standard-api payment-service

# For specific versions
/create https://github.com/vercel/next.js/tree/v14.0.0 next-14-app

Advanced Usage

Custom Repository Features

bash

# Clone specific branch
/create https://github.com/user/repo#feature-branch my-experiment

# Private repositories (requires auth)
/create https://github.com/company/private-template secure-app

Template Composition

bash

# Start with template, then customize
/create makerkit-nextjs marketplace
/execute-task "Add vendor management system"
/add-enterprise-feature "multi-vendor-payments"

Monorepo Setup

bash

# Create in monorepo structure
/create cloudflare-hono api ./packages/api
/create react-native-expo mobile ./packages/mobile
/orchestrate "Monorepo with shared types and utilities"

Tips

Let Discovery Work: Don't over-specify initially
Use Templates Wisely: They're starting points, not constraints
Document Intent: The prompt captures your purpose
Leverage Patterns: Templates include best practices
Think Long-term: Consider scalability from the start

/create - Smart Project Initialization ​

Purpose ​

How It Actually Works ​

Use Cases ​

Argument Structure ​

Arguments ​

Examples ​

MakerKit License Notice ​

Technical Details ​

MCP Tool Integration ​

What Gets Created ​

Memory Usage ​

Created Memory Structure ​

Memory Content ​

Example Memory Entry ​

Workflow Examples ​

SaaS Application Setup ​

Custom Repository Workflow ​

Mobile App Creation ​

Intelligent Features ​

Smart Defaults ​

Dependency Resolution ​

Environment Setup ​

Error Handling ​

Common Issues ​

Recovery Strategies ​

Integration Points ​

With Other Prompts ​

With MCP Tools ​

Best Practices ​

Advanced Usage ​

Custom Repository Features ​

Template Composition ​

Monorepo Setup ​

Tips ​

/create - Smart Project Initialization

Purpose

How It Actually Works

Use Cases

Argument Structure

Arguments

Examples

MakerKit License Notice

Technical Details

MCP Tool Integration

What Gets Created

Memory Usage

Created Memory Structure

Memory Content

Example Memory Entry

Workflow Examples

SaaS Application Setup

Custom Repository Workflow

Mobile App Creation

Intelligent Features

Smart Defaults

Dependency Resolution

Environment Setup

Error Handling

Common Issues

Recovery Strategies

Integration Points

With Other Prompts

With MCP Tools

Best Practices

Advanced Usage

Custom Repository Features

Template Composition

Monorepo Setup

Tips