Templates Guide

Orchestre V3 includes three production-ready templates that showcase the power of dynamic prompt orchestration. Each template is a complete knowledge pack with specialized commands that understand the unique patterns and requirements of their domain.

Overview

Templates in Orchestre are more than just boilerplate code - they're intelligent starting points that include:

• Domain-specific commands: Prompts that understand your technology stack
• Pattern recognition: Built-in knowledge of best practices
• Adaptive guidance: Commands that discover and adapt to your project
• Living documentation: Self-documenting through CLAUDE.md files

Available Templates

1. MakerKit Next.js - SaaS Development

Full-featured SaaS starter with authentication, teams, billing, and admin capabilities.

• Technology: Next.js 14+, TypeScript, Tailwind CSS, Prisma, Stripe
• Architecture: App Router, Server Components, API Routes
• Features: Multi-tenancy, subscription billing, team management
• Commands: 22 specialized SaaS commands
• License: MakerKit is a commercial product. Purchase a license at makerkit.dev

Learn more →

2. Cloudflare Hono - Edge-First APIs

High-performance API template optimized for Cloudflare Workers and edge computing.

• Technology: Hono, TypeScript, Cloudflare Workers, D1/KV
• Architecture: Edge-first, serverless, globally distributed
• Features: JWT auth, rate limiting, caching, WebSocket support
• Commands: 10 edge-optimized commands

Learn more →

3. React Native Expo - Mobile Applications

Modern mobile app template with shared backend integration and native features.

• Technology: React Native, Expo, TypeScript, React Navigation
• Architecture: Managed workflow, modular structure
• Features: Authentication, offline sync, push notifications
• Commands: 10 mobile-specific commands

Learn more →

Template Philosophy

Dynamic Over Static

Traditional templates give you static code to modify. Orchestre templates provide intelligent commands that:

• Discover your specific requirements
• Analyze your existing patterns
• Adapt their suggestions to your context
• Evolve with your project

Knowledge Packs

Each template is a complete knowledge system:

Living Documentation

Templates automatically maintain documentation through the distributed memory system:

• Pattern discoveries are saved
• Decisions are documented
• Context evolves with code
• Knowledge transfers between sessions

Choosing a Template

For SaaS Applications

Choose MakerKit when building:

• Multi-tenant SaaS products
• Subscription-based services
• Team collaboration tools
• Admin dashboards

/create my-saas makerkit-nextjs

For APIs and Services

Choose Cloudflare Hono when building:

• High-performance APIs
• Globally distributed services
• Real-time applications
• Microservices

/create my-api cloudflare-hono

For Mobile Apps

Choose React Native Expo when building:

• Cross-platform mobile apps
• Apps with backend integration
• Offline-first applications
• Native feature requirements

/create my-app react-native-expo

Template Commands

Each template includes specialized commands that understand its domain:

Common Patterns

All templates share certain command patterns:

• Feature Addition: /add-feature, /add-[component]
• Setup & Config: /setup-[service], /configure-[feature]
• Optimization: /optimize-performance, /security-audit
• Integration: /integrate-[service], /add-webhook

Template-Specific Intelligence

Commands adapt to their template's patterns:

# MakerKit understands SaaS patterns
/add-subscription-plan "Enterprise tier with SSO"

# Cloudflare understands edge patterns
/add-edge-function "Geolocation-based routing"

# React Native understands mobile patterns
/add-screen "Onboarding flow with permissions"

Working with Templates

1. Initialization

When you create a project, the template:

• Installs dependencies
• Sets up initial structure
• Configures development environment
• Documents decisions in CLAUDE.md

2. Discovery Phase

Use orchestration commands to understand your needs:

/orchestre:orchestrate (MCP)
# Then provide: "Build a team collaboration feature"

The command will:

• Analyze your requirements
• Discover existing patterns
• Generate an adaptive plan
• Suggest relevant commands

3. Implementation

Execute the plan with template-aware commands:

/orchestre:execute-task (MCP)
# Then provide: "Add team creation flow"

Commands understand:

• Template conventions
• Technology constraints
• Best practices
• Common patterns

4. Evolution

As your project grows, templates help maintain quality:

/orchestre:review (MCP)
# Reviews architecture and suggests improvements

/orchestre:discover-context (MCP)
# Then provide: patterns

Template Customization

Extending Commands

Add your own domain-specific commands:

<!-- .orchestre/commands/my-command.md -->
# /my-custom-command

Discover the project's current authentication setup and enhance it...

Pattern Library

Build on template patterns:

<!-- .orchestre/patterns/my-pattern.md -->
# Custom Authentication Flow

## Pattern
...

## Implementation
...

Memory Templates

Customize documentation structure:

<!-- .orchestre/memory-templates/feature.md -->
# Feature: {name}

## Decisions
...

## Patterns Used
...

Best Practices

1. Let Templates Guide You

Don't fight template conventions:

• Understand the architecture first
• Follow established patterns
• Extend rather than replace

2. Use Template Commands

Leverage specialized knowledge:

• Template commands know best practices
• They understand common pitfalls
• They maintain consistency

3. Document as You Go

Keep the memory system updated:

• Use /learn to capture insights
• Update CLAUDE.md files
• Document key decisions

4. Review Regularly

Maintain code quality:

• Use /review for template-aware analysis
• Run /validate-implementation
• Check /security-audit

Next Steps

1. Choose a template that matches your project type
2. Initialize your project with /create
3. Explore template commands in the reference
4. Start building with intelligent guidance

Ready to start? Check out our Quick Start Tutorial or dive into a specific template guide.