@specverse/engines 5.0.2 → 5.2.0

package/assets/prompts/core/MIGRATION-v6-to-v7.md

@@ -1,379 +0,0 @@
-# Migration Guide: SpecVerse Prompts v6 → v7
-
-**Upgrade your AI workflows to the enhanced v7 prompts with data consistency and environment-adaptive generation**
-
-## 🎯 Overview
-
-SpecVerse v7 prompts represent a major upgrade focused on:
-- **Data consistency**: Multi-layer validation and type mapping
-- **Environment adaptation**: Output that scales with your needs
-- **Production readiness**: Battle-tested patterns and automation
-- **Real-world reliability**: Based on actual implementation experience
-
-## 📊 What's New in v7
-
-### Key Enhancements
-
-| Area | v6 | v7 |
-|------|----|----|
-| **Data Handling** | Basic column mapping | ✅ Snake_case ↔ CamelCase automation |
-| **Validation** | Client-side only | ✅ Database + API + Frontend |
-| **Error Handling** | Manual patterns | ✅ Comprehensive recovery patterns |
-| **Environments** | One-size-fits-all | ✅ Adaptive (dev/test/prod/enterprise) |
-| **Setup** | Manual configuration | ✅ Automated scripts (start.sh) |
-| **Testing** | Limited examples | ✅ Battle-tested with real applications |
-
-### New Features
-- **Database-level validation functions** for conflict detection
-- **Environment-aware deployment** configurations
-- **Comprehensive error handling** with recovery patterns
-- **Automated setup scripts** for instant productivity
-- **Multi-layer type safety** across all application layers
-
-## 🔄 Migration Steps
-
-### Step 1: Update File Paths
-
-**Before (v6):**
-```bash
-prompts/core/standard/v6/create.prompt.yaml
-prompts/core/standard/v6/materialise.prompt.yaml
-prompts/core/standard/v6/realize.prompt.yaml
-```
-
-**After (v7):**
-```bash
-prompts/core/standard/v7/create.prompt.yaml
-prompts/core/standard/v7/materialise.prompt.yaml
-prompts/core/standard/v7/realize.prompt.yaml
-```
-
-### Step 2: Update Variable Sets
-
-#### Materialise Prompt Variables
-
-**v6 Variables:**
-```yaml
-specificationFile: "spec.specly"
-targetFramework: "nextjs"
-implementationStyle: "modern"
-developmentEnvironment: "local"
-```
-
-**v7 Variables (Enhanced):**
-```yaml
-specificationFile: "spec.specly"
-targetFramework: "nextjs"
-implementationStyle: "modern"
-developmentEnvironment: "local"
-# NEW in v7:
-dataConsistencyLevel: "strict"          # basic/strict/paranoid
-errorHandlingStrategy: "comprehensive"  # minimal/standard/comprehensive
-validationDepth: "multi-layer"         # client-only/api-level/multi-layer/database-enforced
-setupAutomation: "full"                # manual/semi-automated/full
-```
-
-#### Realize Prompt Variables
-
-**v6 Variables:**
-```yaml
-cloudProvider: "aws"
-environmentType: "production"
-scaleRequirements: "standard"
-```
-
-**v7 Variables (Enhanced):**
-```yaml
-cloudProvider: "vercel"                 # Added vercel, netlify, local
-environmentType: "production"           # Now drives output complexity
-scaleRequirements: "auto"              # auto adjusts based on environment
-# NEW in v7:
-deploymentStrategy: "rolling"          # rolling/blue-green/canary/recreate
-databaseStrategy: "managed"            # managed/self-hosted/serverless/local
-localDevSupport: "full"               # none/basic/full
-automationLevel: "comprehensive"       # manual/basic/comprehensive
-```
-
-### Step 3: Update Prompt Templates
-
-#### Terminal Usage
-
-**v6 Terminal Prompt:**
-```
-Generate a complete implementation from this SpecVerse specification:
-
-[SPECIFICATION]
-
-Target Framework: nextjs
-Implementation Style: modern
-
-Please generate complete project structure and code.
-```
-
-**v7 Terminal Prompt (Enhanced):**
-```
-Generate a complete implementation from this SpecVerse specification:
-
-[SPECIFICATION]
-
-Target Framework: nextjs
-Implementation Style: modern
-Data Consistency Level: strict
-Error Handling Strategy: comprehensive
-Validation Depth: multi-layer
-Setup Automation: full
-
-Generate:
-1. Complete project structure with automated setup
-2. Database schema with multi-layer validation
-3. API routes with comprehensive error handling
-4. React components with type-safe data handling
-5. Setup scripts (start.sh) for instant development
-6. Production-ready configurations
-```
-
-### Step 4: Review Generated Output
-
-#### Enhanced Database Layer
-
-**v7 Generates:**
-```typescript
-// Enhanced with type mapping
-export async function getBookings(): Promise<Booking[]> {
-  const result = await query('SELECT * FROM bookings ORDER BY check_in')
-  // v7: Automatic snake_case to camelCase mapping
-  return result.rows.map(row => ({
-    id: row.id,
-    roomId: row.room_id,           // ← Automatic mapping
-    guestName: row.guest_name,     // ← Automatic mapping
-    checkIn: row.check_in,         // ← Automatic mapping
-    checkOut: row.check_out,       // ← Automatic mapping
-    notes: row.notes,
-    createdAt: row.created_at
-  }))
-}
-```
-
-#### Enhanced Error Handling
-
-**v7 Generates:**
-```typescript
-// Comprehensive error handling with recovery
-try {
-  const bookings = await getBookings()
-  return NextResponse.json(bookings)
-} catch (error) {
-  console.error('Error fetching bookings:', error)
-
-  // v7: Detailed error classification and recovery
-  if (error.code === 'ECONNREFUSED') {
-    return NextResponse.json(
-      { error: 'Database connection failed', retry: true },
-      { status: 503 }
-    )
-  }
-
-  return NextResponse.json(
-    { error: 'Internal server error', details: error.message },
-    { status: 500 }
-  )
-}
-```
-
-#### Environment-Adaptive Deployment
-
-**v7 Development Environment:**
-```yaml
-# Simple Docker Compose for development
-version: '3.8'
-services:
-  postgres:
-    image: postgres:15
-    environment:
-      POSTGRES_DB: guesthouse_dev
-      POSTGRES_USER: postgres
-      POSTGRES_PASSWORD: postgres
-    ports:
-      - "5432:5432"
-
-  app:
-    build: .
-    ports:
-      - "3000:3000"
-    depends_on:
-      - postgres
-```
-
-**v7 Production Environment:**
-```yaml
-# Full infrastructure with monitoring
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: guesthouse-app
-spec:
-  replicas: 3
-  strategy:
-    type: RollingUpdate
-    rollingUpdate:
-      maxUnavailable: 1
-      maxSurge: 1
-  template:
-    spec:
-      containers:
-      - name: app
-        image: guesthouse:latest
-        ports:
-        - containerPort: 3000
-        livenessProbe:
-          httpGet:
-            path: /api/health
-            port: 3000
-        readinessProbe:
-          httpGet:
-            path: /api/ready
-            port: 3000
-```
-
-## ⚠️ Breaking Changes
-
-### 1. Materialise Prompt Structure
-
-**Breaking Change:** Multi-phase template with data analysis
-```yaml
-# v7 requires analysis phase before implementation
-## PHASE 1: DATA ANALYSIS
-Analyze the specification for:
-- Data models and their relationships
-- Validation rules and constraints
-- Potential conflict scenarios
-
-## PHASE 2: IMPLEMENTATION GENERATION
-Generate implementation with data consistency focus
-```
-
-### 2. Realize Prompt Environment Logic
-
-**Breaking Change:** Conditional template based on environment
-```yaml
-# v7 uses conditional logic
-{% if environmentType == "development" %}
-Generate simple Docker Compose setup
-{% elif environmentType == "production" %}
-Generate production infrastructure
-{% endif %}
-```
-
-### 3. Enhanced Variable Requirements
-
-**Breaking Change:** New required variables for consistency
-- `dataConsistencyLevel` - Controls validation depth
-- `errorHandlingStrategy` - Defines error handling approach
-- `environmentType` - Drives output complexity
-
-## 🛠️ Troubleshooting Common Migration Issues
-
-### Issue: Data Not Displaying After Migration
-
-**Symptoms:**
-- API returns data but frontend shows empty
-- Database queries work but components don't render
-
-**v7 Solution:**
-```yaml
-# Use strict data consistency in materialise
-dataConsistencyLevel: "strict"
-validationDepth: "multi-layer"
-```
-
-**Result:** Automatic snake_case/camelCase mapping generated
-
-### Issue: Over-Engineered Development Environment
-
-**Symptoms:**
-- Complex infrastructure for local development
-- Unnecessary monitoring and compliance features
-
-**v7 Solution:**
-```yaml
-# Use development environment type
-environmentType: "development"
-localDevSupport: "full"
-```
-
-**Result:** Simple Docker Compose + start.sh script
-
-### Issue: Missing Error Handling
-
-**Symptoms:**
-- Application crashes on errors
-- No recovery mechanisms
-- Poor error messages
-
-**v7 Solution:**
-```yaml
-# Use comprehensive error handling
-errorHandlingStrategy: "comprehensive"
-```
-
-**Result:** Complete error handling with recovery patterns
-
-## ✅ Validation Checklist
-
-After migration, verify:
-
-- [ ] **File paths updated** to v7 directories
-- [ ] **New variables added** for data consistency and environment
-- [ ] **Generated code includes** type mapping functions
-- [ ] **Error handling is comprehensive** with recovery patterns
-- [ ] **Setup scripts work** (start.sh can launch application)
-- [ ] **Environment-appropriate complexity** (dev ≠ prod features)
-- [ ] **Database validation** functions are generated
-- [ ] **Multi-layer validation** across all boundaries
-
-## 📚 Learning Resources
-
-### Example Migration
-
-See the complete guesthouse booking system example that validated v7:
-- **Before**: Manual setup, data mapping issues, basic error handling
-- **After**: Automated setup, consistent data flow, comprehensive error handling
-
-### Key Files to Review
-
-1. **`lib/db.ts`** - Data mapping functions
-2. **`start.sh`** - Automated setup script
-3. **`schema.sql`** - Database constraints and functions
-4. **API routes** - Error handling patterns
-5. **Components** - Type-safe data handling
-
-## 🎯 Best Practices for v7
-
-### 1. Choose Appropriate Data Consistency
-- **Basic**: Simple applications, minimal validation
-- **Strict**: Business applications (recommended)
-- **Paranoid**: Financial/healthcare applications
-
-### 2. Environment-Specific Configuration
-- **Development**: Focus on speed and debugging
-- **Production**: Include monitoring and security
-- **Enterprise**: Full compliance and disaster recovery
-
-### 3. Gradual Migration Strategy
-1. Start with development environment
-2. Validate data consistency patterns
-3. Test error handling scenarios
-4. Migrate production configurations
-5. Update team documentation
-
-## 🚀 Next Steps
-
-1. **Update your prompts** to v7 syntax
-2. **Test with a small project** to validate migration
-3. **Review generated code** for quality improvements
-4. **Update team documentation** with v7 patterns
-5. **Enjoy enhanced productivity** with automated setup!
-
----
-
-**Need help?** Check the [troubleshooting section](README.md#troubleshooting) in the main README or review the [CHANGELOG](CHANGELOG.md) for detailed changes.

package/assets/prompts/core/base-terminal-prompt.md

@@ -1,201 +0,0 @@
-# SpecVerse Terminal Quick-Start Guide
-
-**For**: LLM Terminal Users (ChatGPT, Claude, Cursor, etc.)
-**Purpose**: Use SpecVerse standard prompts for specification generation and implementation
-**Version**: 7.0.0
-
-This guide shows how to use the **standard SpecVerse prompts** for terminal/chat-based AI interactions.
-
-## Available Standard Prompts (v7)
-
-SpecVerse provides four standard prompts with enhanced capabilities:
-
-1. **`create`** - Generate SpecVerse specifications from natural language requirements
-2. **`analyse`** - Extract specifications from existing codebases (reverse engineering)
-3. **`materialise`** - Generate complete implementations from specifications
-4. **`realize`** - Generate deployment configurations (environment-adaptive)
-
-Located in: `prompts/core/standard/v7/`
-
-## Quick Start: Using the Create Prompt
-
-The **create** prompt is your starting point for new projects:
-
-### Step 1: View the Full Prompt
-
-```bash
-cat prompts/core/standard/v7/create.prompt.yaml
-```
-
-### Step 2: Terminal-Ready Version
-
-Copy this complete prompt into your LLM:
-
-```
-You are a SpecVerse v3.2.0 specification creator that generates complete, well-structured specifications from natural language requirements.
-
-IMPORTANT: First, read these reference files if available:
-- node_modules/@specverse/lang/schema/SPECVERSE-SCHEMA-AI.yaml (AI guidance and examples)
-- node_modules/@specverse/lang/schema/MINIMAL-SYNTAX-REFERENCE.specly (complete syntax example)
-
-Your task is to:
-1. Analyze natural language requirements
-2. Extract core business entities and their relationships
-3. Generate complete SpecVerse specifications with:
-   - Models with attributes and behaviors
-   - Controllers with CURED operations
-   - Services with business logic
-   - Views for user interfaces
-   - Events for system communication
-   - Deployments for infrastructure
-   - Manifests for implementation details
-
-Use SpecVerse v3.2.0 syntax:
-- Attributes: name: Type modifiers
-- Types: String, Integer, UUID, Email, DateTime, Boolean, Money, Text
-- Modifiers: required, optional, unique, auto, searchable, indexed, default=value
-- Relations: hasMany, belongsTo, references
-
-Generate a SpecVerse specification from these requirements:
-
-Requirements: [YOUR REQUIREMENTS HERE]
-Project Type: [web-app/api/full-stack]
-Scale: [personal/startup/business/enterprise]
-Primary Technology: [nextjs/nestjs/express/auto]
-
-Please generate:
-1. Complete component specification with all models and relationships
-2. Implementation manifest with technology choices
-3. Deployment specification for the target environment
-```
-
-## Workflow Example: From Idea to Implementation
-
-### 1. Create Specification
-```
-Requirements: I need a guesthouse booking system where I can manage multiple properties, each with rooms that guests can book. Need to see bookings on a timeline and prevent double-booking.
-Project Type: full-stack
-Scale: business
-Primary Technology: nextjs
-```
-
-### 2. Generate Implementation (Materialise)
-After getting your specification, use the materialise prompt:
-
-```
-Generate a complete implementation from this SpecVerse specification:
-
-[PASTE YOUR SPECIFICATION HERE]
-
-Target Framework: nextjs
-Implementation Style: modern
-Data Consistency Level: strict
-Error Handling Strategy: comprehensive
-
-Generate:
-1. Complete project structure
-2. Database schema with migrations
-3. API routes with validation
-4. React components with state management
-5. Setup scripts (like start.sh)
-6. Documentation
-```
-
-### 3. Generate Deployment (Realize)
-For deployment configurations:
-
-```
-Generate deployment configurations from this SpecVerse specification:
-
-[PASTE YOUR SPECIFICATION HERE]
-
-Target Environment: [development/production/enterprise]
-Cloud Provider: [vercel/aws/local]
-
-For development: Generate Docker Compose and start.sh script
-For production: Generate infrastructure as code and CI/CD pipelines
-```
-
-## Complete Workflow Commands
-
-1. **Create** a specification from requirements
-2. **Save** as `spec.specly`
-3. **Materialise** into working code
-4. **Realize** deployment configurations
-5. **Run** with generated start scripts
-
-## Key Improvements in v7
-
-### Create (v7)
-- Better validation and type safety
-- Support for complex relationships
-- Event-driven architecture patterns
-- Modern deployment targets (Vercel, Netlify)
-
-### Materialise (v7)
-- **Data consistency focus** - Handles snake_case/camelCase mapping
-- **Multi-layer validation** - Database, API, and frontend
-- **Automated setup** - Generates start.sh style scripts
-- **Error handling** - Comprehensive error patterns
-
-### Realize (v7)
-- **Environment-adaptive** - Only generates what's needed
-- **Progressive enhancement** - Dev → Test → Prod → Enterprise
-- **Local dev support** - Quick start scripts and Docker Compose
-- **Zero-downtime** - Blue-green and canary deployments
-
-## Environment-Specific Generation
-
-### Development
-- Simple Docker Compose
-- start.sh quick-start script
-- Hot reload configuration
-- Basic debugging setup
-
-### Production
-- High availability infrastructure
-- Monitoring and alerting
-- Security hardening
-- Backup and recovery
-
-### Enterprise
-- Multi-region deployment
-- Compliance frameworks
-- Advanced security
-- Disaster recovery
-
-## Tips for Better Results
-
-1. **Be specific** about your requirements
-2. **Include examples** of the data you'll work with
-3. **Specify scale** to get appropriate architecture
-4. **Mention constraints** like compliance or performance
-5. **Describe user workflows** for better UX generation
-
-## Troubleshooting Common Issues
-
-### Data Mapping Issues
-If you see snake_case/camelCase problems:
-- Request "strict" data consistency level in materialise
-- Ask for explicit data mapping functions
-
-### Missing Bookings/Data
-Check for:
-- Database column name mapping (room_id vs roomId)
-- Date format conversions (ISO vs YYYY-MM-DD)
-- API response transformations
-
-### Connection Issues
-For database connections:
-- Use environment variables in scripts
-- Generate start.sh with explicit POSTGRES_URL
-- Include .env.example templates
-
-## Next Steps
-
-1. Start with the **create** prompt for your requirements
-2. Use **materialise** to generate implementation
-3. Apply **realize** for deployment setup
-4. Iterate based on your specific needs
-
-Remember: v7 prompts are environment-aware and will adapt their output to your actual needs!

package/assets/prompts/core/examples/example-usage.ts

@@ -1,140 +0,0 @@
-/**
- * Example usage of the SpecVerse Prompt System
- * Demonstrates how to load and process prompts with the PromptLoader
- */
-
-import { promptLoader } from '../src/prompts/prompt-loader';
-
-async function demonstratePromptUsage() {
-  console.log('SpecVerse Prompt System Demo\n');
-
-  try {
-    // 1. List all available prompts
-    console.log('📋 Available prompts:');
-    const prompts = await promptLoader.listPrompts();
-    prompts.forEach(({ path, definition }) => {
-      console.log(`  - ${path}: ${definition.description}`);
-    });
-    console.log('');
-
-    // 2. Load and process the 'create' prompt
-    console.log('🔧 Processing "create" prompt...');
-    const createPrompt = await promptLoader.processPrompt(
-      'standard/create',
-      {
-        requirements: 'Build a simple blog where users can write posts with titles and content. Posts should have tags for organization.',
-        scale: 'personal',
-        preferredTech: 'nextjs'
-      }
-    );
-
-    console.log('System Prompt Preview:');
-    console.log(createPrompt.system.substring(0, 200) + '...\n');
-
-    console.log('User Prompt Preview:');
-    console.log(createPrompt.user.substring(0, 300) + '...\n');
-
-    // 3. Load and process the 'analyse' prompt
-    console.log('🔍 Processing "analyse" prompt...');
-    const analysePrompt = await promptLoader.processPrompt(
-      'standard/analyse',
-      {
-        applicationPath: '/path/to/my-app',
-        frameworkType: 'nextjs',
-        directoryStructure: 'my-app/\n├── app/\n│   └── api/\n└── package.json',
-        filesContent: '=== package.json ===\n{ "name": "my-app" }'
-      }
-    );
-
-    console.log('Analysis Prompt Ready:');
-    console.log(`- System prompt length: ${analysePrompt.system.length} chars`);
-    console.log(`- User prompt length: ${analysePrompt.user.length} chars`);
-    console.log(`- Context includes: ${Object.keys(analysePrompt.context.includes).join(', ')}\n`);
-
-    // 4. Validate a prompt
-    console.log('✅ Validating prompt structure...');
-    const prompt = await promptLoader.loadPrompt('standard/create');
-    const validation = promptLoader.validatePrompt(prompt);
-    
-    console.log(`Validation result: ${validation.valid ? 'PASSED' : 'FAILED'}`);
-    if (!validation.valid) {
-      console.log('Errors:', validation.errors);
-    }
-
-  } catch (error) {
-    console.error('Error:', error.message);
-  }
-}
-
-async function exampleLLMIntegration() {
-  console.log('\n🤖 Example LLM Integration\n');
-
-  try {
-    // Simulate loading a prompt and sending to LLM
-    const prompt = await promptLoader.processPrompt(
-      'standard/create',
-      {
-        requirements: 'Create an e-commerce site with products and shopping cart',
-        scale: 'business'
-      }
-    );
-
-    // This is what you would send to an LLM provider
-    const llmRequest = {
-      messages: [
-        { role: 'system', content: prompt.system },
-        { role: 'user', content: prompt.user }
-      ],
-      max_tokens: prompt.context.max_tokens,
-      temperature: prompt.context.temperature,
-      top_p: prompt.context.top_p
-    };
-
-    console.log('LLM Request Structure:');
-    console.log(`- Messages: ${llmRequest.messages.length}`);
-    console.log(`- Max tokens: ${llmRequest.max_tokens}`);
-    console.log(`- Temperature: ${llmRequest.temperature}`);
-    console.log(`- Top P: ${llmRequest.top_p}`);
-
-    // Mock LLM response
-    const mockResponse = `
-components:
-  EcommercePlatform:
-    version: "1.0.0"
-    description: "E-commerce platform"
-    
-    models:
-      Product:
-        attributes:
-          name: String required searchable
-          price: Money required
-          inventory: Integer required default=0 min=0
-        relationships:
-          category: belongsTo Category required
-          
-      Category:
-        attributes:
-          name: String required unique
-        relationships:
-          products: hasMany Product
-    `;
-
-    console.log('\nMock LLM Response:');
-    console.log(mockResponse);
-
-  } catch (error) {
-    console.error('Error:', error.message);
-  }
-}
-
-async function runExamples() {
-  await demonstratePromptUsage();
-  await exampleLLMIntegration();
-}
-
-// Run examples if this file is executed directly
-if (require.main === module) {
-  runExamples().catch(console.error);
-}
-
-export { demonstratePromptUsage, exampleLLMIntegration };