Examples & Templates

Learn how to use Orchestre through our three powerful templates. Each template demonstrates best practices and real-world patterns.

Available Templates

Orchestre provides three production-ready templates to jumpstart your projects:

1. MakerKit Next.js - SaaS Template

A complete SaaS starter kit with everything you need to launch a subscription-based application.

Features:

• Multi-tenant architecture with team management
• Authentication (email/password, social login)
• Subscription billing with Stripe
• Admin dashboard
• User profiles and settings
• Responsive design with Tailwind CSS

Technologies: Next.js 14, Supabase, Stripe, Tailwind CSS

Get Started:

# Create a new MakerKit project
/orchestre:create (MCP)
# Select "makerkit-nextjs" template

2. Cloudflare Hono - API Template

A high-performance API template optimized for edge deployment with Cloudflare Workers.

Features:

• RESTful API structure
• Authentication middleware
• Database integration with D1
• File storage with R2
• Rate limiting and security
• OpenAPI documentation

Technologies: Hono, Cloudflare Workers, D1, R2

Get Started:

# Create a new Cloudflare API project
/orchestre:create (MCP)
# Select "cloudflare-hono" template

3. React Native Expo - Mobile Template

A cross-platform mobile app template with native features and modern development experience.

Features:

• Cross-platform (iOS & Android)
• Navigation setup
• Authentication flow
• Native device features
• Push notifications
• Offline support

Technologies: React Native, Expo, TypeScript

Get Started:

# Create a new React Native project
/orchestre:create (MCP)
# Select "react-native-expo" template

Working with Templates

Project Structure

All templates follow a consistent structure enhanced by Orchestre:

your-project/
├── CLAUDE.md           # Project memory and context
├── src/                # Source code
├── .orchestre/         # Orchestre configuration
│   ├── prompts.json    # Available commands
│   ├── CLAUDE.md       # Orchestration memory
│   ├── plans/          # Development plans
│   ├── reviews/        # Code review results
│   └── knowledge/      # Project insights
└── [template files]    # Template-specific structure

Using Orchestre Commands

Once your project is created, you can use these MCP prompts in Claude Code:

Planning & Development

• /orchestre:orchestrate (MCP) - Analyze requirements and create a development plan
• /orchestre:execute-task (MCP) - Execute specific development tasks
• /orchestre:compose-saas-mvp (MCP) - Rapid SaaS prototyping (MakerKit template)

Code Quality

• /orchestre:review (MCP) - Multi-LLM code review
• /orchestre:security-audit (MCP) - Security vulnerability scan

Documentation

• /orchestre:document-feature (MCP) - Create feature documentation
• /orchestre:discover-context (MCP) - Analyze existing codebase

Template-Specific Patterns

MakerKit SaaS Patterns

• Feature-based module organization
• Shared authentication context
• Subscription lifecycle management
• Team/organization data isolation

Cloudflare API Patterns

• Middleware composition
• Edge-optimized data fetching
• Durable Objects for state
• Worker-to-worker communication

React Native Patterns

• Component-driven architecture
• Cross-platform code sharing
• Native module integration
• Navigation state management

Learning Resources

Quick Start Guides

• Getting Started Tutorial - Build your first project with Orchestre
• Template Guide - Deep dive into each template
• Interactive Tutorial - Learn by doing

Best Practices

• Use /orchestre:discover-context (MCP) when starting with an existing codebase
• Run /orchestre:review (MCP) before major commits
• Document decisions in CLAUDE.md files
• Keep .orchestre/plans/ updated with your development progress

Common Workflows

Starting a New Feature

1. /orchestre:orchestrate (MCP) "Add user notifications"
2. Review the generated plan
3. /orchestre:execute-task (MCP) "Implement notification model"
4. /orchestre:review (MCP)
5. /orchestre:document-feature (MCP)

Analyzing an Existing Project

1. /orchestre:discover-context (MCP)
2. Review generated CLAUDE.md files
3. /orchestre:orchestrate (MCP) "Modernize authentication"

Security Hardening

1. /orchestre:security-audit (MCP)
2. Review findings in .orchestre/reviews/
3. /orchestre:execute-task (MCP) "Fix security vulnerabilities"

Next Steps

1. Choose a Template: Pick the template that best fits your project needs
2. Create Your Project: Use /orchestre:create (MCP) to get started
3. Explore Commands: Try different Orchestre prompts to see their capabilities
4. Build Something Amazing: Let Orchestre help you build faster and better

---

Need help? Check our Getting Started Guide or Troubleshooting Guide.