Skip to content

/template (or /t)

Execute template-specific commands tailored to your project's template.

Overview

The /template prompt (shorthand: /t) provides access to 42 specialized commands designed for your specific project template. Whether you're using MakerKit for SaaS, Cloudflare for edge computing, or React Native for mobile apps, this prompt executes template-optimized commands.

When to Use

Use /template when you need to:

  • Add template-specific features (e.g., Stripe to MakerKit)
  • Follow template conventions and patterns
  • Use template-optimized implementations
  • Access template-specific utilities
  • Maintain consistency with your template

Syntax

/template <command> [arguments]
/t <command> [arguments]

Arguments

  • command (required): The template-specific command to execute
  • arguments (optional): Additional parameters for the command

Template Commands by Category

MakerKit NextJS (22 commands)

Feature Development

  • add-feature - Add a complete feature module
  • add-api-endpoint - Create API routes with validation
  • add-database-table - Add Supabase tables with RLS
  • add-admin-feature - Add admin panel functionality
  • add-team-feature - Add team collaboration features

Configuration & Setup

  • setup-stripe - Configure Stripe payments
  • setup-oauth - Add OAuth providers
  • setup-mfa - Enable multi-factor authentication
  • setup-monitoring - Add monitoring and analytics
  • setup-testing - Configure test suites

Integration & Deployment

  • add-webhook - Add webhook endpoints
  • implement-email-template - Create email templates
  • deploy-production - Deploy to production

Cloudflare Hono (10 commands)

API Development

  • add-api-route - Add Hono API routes
  • add-middleware - Create custom middleware
  • implement-queue - Add queue processing

Infrastructure

  • add-r2-storage - Configure R2 object storage
  • add-worker-cron - Set up scheduled jobs
  • setup-analytics - Add Cloudflare Analytics

Deployment

  • deploy-worker - Deploy to Cloudflare Workers

React Native Expo (10 commands)

Screen & Navigation

  • add-screen - Add new app screens
  • implement-deep-linking - Set up deep links

Features

  • add-offline-sync - Add offline capabilities
  • add-in-app-purchase - Implement purchases
  • setup-push-notifications - Configure push notifications

Integration

  • add-api-client - Create API integration
  • setup-shared-backend - Connect to backend

Examples

MakerKit Examples

/template add-feature billing
/t setup-stripe monthly-subscription
/template add-api-endpoint /api/webhooks/stripe
/t add-team-feature invite-members

Cloudflare Examples

/template add-api-route /api/users GET,POST
/t setup-auth jwt
/template deploy-worker production
/t add-r2-storage user-uploads

React Native Examples

/template add-screen ProfileSettings
/t setup-push-notifications firebase
/template add-offline-sync realm
/t implement-deep-linking product-detail

How It Works

  1. Command Discovery: Checks .orchestre/template-prompts/ for the command
  2. Intelligent Matching: If exact command not found:
    • Suggests similar commands
    • Shows available commands by category
    • Provides usage examples
  3. Pattern Integration: Uses patterns from .orchestre/patterns/
  4. Task Tracking: Creates checklist in .orchestre/tasks/
  5. Template Awareness: Follows template-specific conventions

Command Discovery

If a command isn't found, you'll see:

Template command 'add-api' not found.

Did you mean one of these?
• add-api-route - Add a new API endpoint
• add-api-endpoint - Create API with MakerKit
• add-api-client - Create API client

Available commands for your template:

Feature Development (8):
• /template add-feature - Add a new feature module
• /template add-api-endpoint - Create API routes
...

Template Indexes

Each template has an index of available commands:

  • .orchestre/template-prompts/index.md - Full command list
  • Organized by category
  • Includes examples and descriptions

View your template's commands:

/template
/t help

Pattern Integration

Template commands use established patterns:

.orchestre/patterns/[template-name]/
├── core/           # Core patterns
├── features/       # Feature patterns
├── security/       # Security patterns
└── testing/        # Testing patterns

Task Tracking

Each execution creates a task checklist:

.orchestre/tasks/2024-01-15-add-feature-billing-tasks.md
├── Expected Outcomes
├── Completion Status
└── Implementation Notes

Best Practices

  1. Use Template Commands First: They're optimized for your stack
  2. Check Available Commands: Run /t to see what's available
  3. Follow Patterns: Commands use your template's patterns
  4. Review Task Lists: Check expected outcomes before starting
  5. Chain Commands: Combine for complex features

Common Workflows

Adding a Complete Feature

/t add-feature user-settings
/t add-api-endpoint /api/settings
/t add-database-table user_preferences
/t setup-testing user-settings

Setting Up Authentication

/t setup-auth supabase
/t setup-oauth google,github
/t setup-mfa
/t add-webhook auth-events

Deployment Pipeline

/t setup-testing
/t setup-monitoring
/t deploy-production

Template-Specific Benefits

MakerKit

  • Pre-configured Supabase patterns
  • Stripe integration shortcuts
  • Multi-tenancy helpers
  • Admin panel components

Cloudflare

  • Worker-optimized code
  • Edge-first patterns
  • D1/R2/KV integration
  • Deployment automation

React Native

  • Platform-specific handling
  • Native module integration
  • Expo SDK helpers
  • Cross-platform patterns

Differences from Core Prompts

Core PromptsTemplate Commands
Generic implementationTemplate-optimized
Discovers patternsUses template patterns
Any frameworkSpecific to your template
Flexible approachConvention-based

Error Handling

Commands handle common issues:

  • Missing dependencies
  • Configuration requirements
  • Template version compatibility
  • Pattern availability

Extending Templates

Add custom commands:

  1. Create .orchestre/template-prompts/custom-command.md
  2. Follow the template command format
  3. Access via /template custom-command
  • /orchestrate - Plan before using template commands
  • /discover-context - Understand template structure
  • /extract-patterns - Find patterns to use
  • /generate-implementation-tutorial - Coordinate multiple template commands

Built with ❤️ for the AI Coding community, by Praney Behl