/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 moduleadd-api-endpoint- Create API routes with validationadd-database-table- Add Supabase tables with RLSadd-admin-feature- Add admin panel functionalityadd-team-feature- Add team collaboration features
Configuration & Setup
setup-stripe- Configure Stripe paymentssetup-oauth- Add OAuth providerssetup-mfa- Enable multi-factor authenticationsetup-monitoring- Add monitoring and analyticssetup-testing- Configure test suites
Integration & Deployment
add-webhook- Add webhook endpointsimplement-email-template- Create email templatesdeploy-production- Deploy to production
Cloudflare Hono (10 commands)
API Development
add-api-route- Add Hono API routesadd-middleware- Create custom middlewareimplement-queue- Add queue processing
Infrastructure
add-r2-storage- Configure R2 object storageadd-worker-cron- Set up scheduled jobssetup-analytics- Add Cloudflare Analytics
Deployment
deploy-worker- Deploy to Cloudflare Workers
React Native Expo (10 commands)
Screen & Navigation
add-screen- Add new app screensimplement-deep-linking- Set up deep links
Features
add-offline-sync- Add offline capabilitiesadd-in-app-purchase- Implement purchasessetup-push-notifications- Configure push notifications
Integration
add-api-client- Create API integrationsetup-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-membersCloudflare Examples
/template add-api-route /api/users GET,POST
/t setup-auth jwt
/template deploy-worker production
/t add-r2-storage user-uploadsReact Native Examples
/template add-screen ProfileSettings
/t setup-push-notifications firebase
/template add-offline-sync realm
/t implement-deep-linking product-detailHow It Works
- Command Discovery: Checks
.orchestre/template-prompts/for the command - Intelligent Matching: If exact command not found:
- Suggests similar commands
- Shows available commands by category
- Provides usage examples
- Pattern Integration: Uses patterns from
.orchestre/patterns/ - Task Tracking: Creates checklist in
.orchestre/tasks/ - 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 helpPattern Integration
Template commands use established patterns:
.orchestre/patterns/[template-name]/
├── core/ # Core patterns
├── features/ # Feature patterns
├── security/ # Security patterns
└── testing/ # Testing patternsTask Tracking
Each execution creates a task checklist:
.orchestre/tasks/2024-01-15-add-feature-billing-tasks.md
├── Expected Outcomes
├── Completion Status
└── Implementation NotesBest Practices
- Use Template Commands First: They're optimized for your stack
- Check Available Commands: Run
/tto see what's available - Follow Patterns: Commands use your template's patterns
- Review Task Lists: Check expected outcomes before starting
- 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-settingsSetting Up Authentication
/t setup-auth supabase
/t setup-oauth google,github
/t setup-mfa
/t add-webhook auth-eventsDeployment Pipeline
/t setup-testing
/t setup-monitoring
/t deploy-productionTemplate-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 Prompts | Template Commands |
|---|---|
| Generic implementation | Template-optimized |
| Discovers patterns | Uses template patterns |
| Any framework | Specific to your template |
| Flexible approach | Convention-based |
Error Handling
Commands handle common issues:
- Missing dependencies
- Configuration requirements
- Template version compatibility
- Pattern availability
Extending Templates
Add custom commands:
- Create
.orchestre/template-prompts/custom-command.md - Follow the template command format
- Access via
/template custom-command
Related Commands
/orchestrate- Plan before using template commands/discover-context- Understand template structure/extract-patterns- Find patterns to use/generate-implementation-tutorial- Coordinate multiple template commands
