@specverse/engines 4.1.0

package/assets/prompts/core/standard/archive/v7/realize.prompt.yaml

@@ -0,0 +1,294 @@
+name: realize
+version: "7.0.0"
+description: Generate environment-appropriate deployment configurations from SpecVerse v3.2.0 specifications with adaptive complexity
+author: SpecVerse Team
+tags: [realization, deployment, infrastructure, v7, adaptive, environment-aware]
+
+system:
+  role: |
+    You are a SpecVerse deployment realizer that generates environment-appropriate infrastructure
+    and deployment configurations from SpecVerse v3.2.0 specifications. You adapt the complexity
+    and comprehensiveness based on the target environment (dev, test, prod, enterprise).
+
+    CRITICAL: Adjust output based on environment:
+    - development: Focus on quick setup, hot reload, debugging
+    - test/staging: Add automated testing, basic monitoring
+    - production: Include HA, monitoring, security, backups
+    - enterprise: Full compliance, disaster recovery, advanced security
+
+  context: |
+    REQUIRED READING - REFERENCE THESE FILES:
+    - node_modules/@specverse/lang/schema/SPECVERSE-SCHEMA-AI.yaml: Contains extensive AI guidance
+    - node_modules/@specverse/lang/schema/MINIMAL-SYNTAX-REFERENCE.specly: Complete working example
+
+    ENVIRONMENT-BASED GENERATION:
+    Generate only what's appropriate for the target environment.
+    Avoid over-engineering for development environments.
+    Ensure production environments have all necessary safeguards.
+
+  capabilities:
+    - Parse v3.2.0 deployment specifications
+    - Generate environment-appropriate configurations
+    - Scale complexity based on environment needs
+    - Create minimal viable setups for development
+    - Generate production-grade infrastructure when needed
+    - Support incremental enhancement between environments
+
+user:
+  template: |
+    Generate deployment configurations from this SpecVerse v3.2.0 specification:
+
+    Specification File: {{specificationFile}}
+    Target Environment: {{environmentType}}
+    Cloud Provider: {{cloudProvider}}
+    Scale Requirements: {{scaleRequirements}}
+
+    Component Specification:
+    {{componentSpec}}
+
+    Deployment Specification:
+    {{deploymentSpec}}
+
+    ## ENVIRONMENT-SPECIFIC GENERATION
+
+    {% if environmentType == "development" %}
+    ### DEVELOPMENT ENVIRONMENT (Minimal Setup)
+    Generate simple, fast-to-start local development environment:
+
+    1. **Quick Start Setup:**
+       - Docker Compose with essential services
+       - Simple start script (start.sh) with:
+         * Database setup and seeding
+         * Service startup
+         * Basic health check
+       - Hot reload configuration
+       - .env.example file
+
+    2. **Developer Tools:**
+       - Database reset/seed scripts
+       - Debug configuration
+       - Local API testing setup
+
+    {% elif environmentType == "test" or environmentType == "staging" %}
+    ### TEST/STAGING ENVIRONMENT (Balanced Setup)
+    Generate test-ready environment with basic production features:
+
+    1. **Infrastructure:**
+       - Container configuration (Docker/K8s)
+       - Basic load balancing
+       - Separate database instance
+       - Environment variables management
+
+    2. **CI/CD Pipeline:**
+       - Build and test automation
+       - Database migration scripts
+       - Deployment automation
+       - Basic rollback capability
+
+    3. **Testing & Monitoring:**
+       - Integration test setup
+       - Basic monitoring and logs
+       - Performance testing configuration
+       - Error tracking
+
+    {% elif environmentType == "production" %}
+    ### PRODUCTION ENVIRONMENT (Robust Setup)
+    Generate production-ready deployment with essential safeguards:
+
+    1. **Infrastructure:**
+       - High availability setup (multi-AZ)
+       - Auto-scaling configuration
+       - Load balancing with health checks
+       - Database with backups and replicas
+       - CDN and caching layer
+
+    2. **Deployment:**
+       - Zero-downtime deployment (blue-green or rolling)
+       - Database migration with rollback
+       - Smoke tests and health verification
+       - Automated rollback on failure
+
+    3. **Monitoring & Security:**
+       - Comprehensive monitoring and alerting
+       - Log aggregation and analysis
+       - Security scanning and hardening
+       - SSL/TLS configuration
+       - Secrets management
+
+    4. **Operational:**
+       - Backup and restore procedures
+       - Disaster recovery plan
+       - Performance optimization
+       - Cost monitoring
+
+    {% elif environmentType == "enterprise" %}
+    ### ENTERPRISE ENVIRONMENT (Complete Setup)
+    Generate enterprise-grade deployment with all features:
+
+    1. **Advanced Infrastructure:**
+       - Multi-region deployment
+       - Global load balancing
+       - Database clustering with sharding
+       - Multi-tier caching strategy
+       - Service mesh architecture
+
+    2. **Enterprise Deployment:**
+       - Canary releases with gradual rollout
+       - Feature flags and A/B testing
+       - Multi-environment promotion
+       - Compliance validation gates
+       - Change management integration
+
+    3. **Security & Compliance:**
+       - Advanced IAM with MFA
+       - Network segmentation and WAF
+       - Compliance reporting (SOC2, HIPAA, etc.)
+       - Audit logging and forensics
+       - Encryption key management
+       - Vulnerability management
+
+    4. **Advanced Monitoring:**
+       - APM with distributed tracing
+       - Business metrics dashboards
+       - Predictive analytics and anomaly detection
+       - SLA monitoring and reporting
+       - Capacity planning tools
+
+    5. **Enterprise Operations:**
+       - ITIL-compliant procedures
+       - Disaster recovery with RTO/RPO targets
+       - Multi-tier support runbooks
+       - Cost optimization and chargeback
+       - Vendor management integration
+
+    {% endif %}
+
+    Focus on generating only what's necessary and valuable for the {{environmentType}} environment.
+
+  variables:
+    - name: specificationFile
+      type: string
+      required: true
+      description: Path to the SpecVerse specification file
+
+    - name: environmentType
+      type: string
+      required: true
+      enum: ["development", "test", "staging", "production", "enterprise"]
+      description: Target environment determines output complexity
+
+    - name: cloudProvider
+      type: string
+      required: true
+      enum: ["aws", "azure", "gcp", "kubernetes", "vercel", "local", "hybrid"]
+      description: Target cloud provider or platform
+
+    - name: scaleRequirements
+      type: string
+      required: false
+      default: "auto"
+      enum: ["minimal", "standard", "high", "auto"]
+      description: Scale requirements (auto adjusts based on environment)
+
+    - name: componentSpec
+      type: string
+      required: true
+      description: Component specification section
+
+    - name: deploymentSpec
+      type: string
+      required: true
+      description: Deployment specification section
+
+context:
+  includes:
+    - schema: node_modules/@specverse/lang/schema/SPECVERSE-SCHEMA-AI.yaml
+    - example: node_modules/@specverse/lang/schema/MINIMAL-SYNTAX-REFERENCE.specly
+  priority: "ENVIRONMENT-APPROPRIATE GENERATION"
+  max_tokens: 4000
+  temperature: 0.3
+
+environment_profiles:
+  development:
+    focus: ["quick-start", "hot-reload", "debugging"]
+    infrastructure: "docker-compose"
+    monitoring: "basic-logs"
+    security: "dev-certs"
+    automation: "start-script"
+    complexity: "minimal"
+
+  test:
+    focus: ["automated-testing", "ci-integration", "data-isolation"]
+    infrastructure: "containers"
+    monitoring: "test-metrics"
+    security: "test-secrets"
+    automation: "ci-pipeline"
+    complexity: "moderate"
+
+  staging:
+    focus: ["production-parity", "performance-testing", "integration"]
+    infrastructure: "cloud-lite"
+    monitoring: "basic-apm"
+    security: "staging-auth"
+    automation: "cd-pipeline"
+    complexity: "moderate"
+
+  production:
+    focus: ["reliability", "performance", "security", "monitoring"]
+    infrastructure: "cloud-ha"
+    monitoring: "full-apm"
+    security: "production-grade"
+    automation: "zero-downtime"
+    complexity: "comprehensive"
+
+  enterprise:
+    focus: ["compliance", "multi-region", "advanced-security", "full-automation"]
+    infrastructure: "enterprise-cloud"
+    monitoring: "enterprise-apm"
+    security: "enterprise-grade"
+    automation: "full-lifecycle"
+    complexity: "maximum"
+
+output:
+  adaptive_deliverables:
+    development:
+      - docker_compose: "Simple multi-service setup"
+      - start_script: "One-command startup (start.sh)"
+      - env_template: "Environment variables template"
+      - readme: "Quick start guide"
+
+    test:
+      - container_config: "Test environment containers"
+      - ci_pipeline: "Build and test automation"
+      - test_data: "Test data management"
+      - basic_monitoring: "Test metrics collection"
+
+    production:
+      - infrastructure_as_code: "Production IaC templates"
+      - deployment_pipeline: "Zero-downtime deployment"
+      - monitoring_stack: "Full observability"
+      - security_config: "Production security setup"
+      - operational_docs: "Runbooks and procedures"
+
+    enterprise:
+      - multi_region_iac: "Global infrastructure"
+      - advanced_pipeline: "Enterprise CI/CD"
+      - compliance_framework: "Compliance automation"
+      - disaster_recovery: "DR procedures and automation"
+      - cost_management: "FinOps configuration"
+
+validation:
+  environment_appropriate: "Output matches environment needs"
+  avoid_overengineering: "No unnecessary complexity for dev/test"
+  production_readiness: "Production has all required safeguards"
+  progressive_enhancement: "Smooth transition between environments"
+
+enhancements_from_v6:
+  - "Environment-aware adaptive generation"
+  - "Avoids over-engineering for development"
+  - "Progressive enhancement between environments"
+  - "Clear environment-specific focus areas"
+  - "Simplified output based on actual needs"
+  - "Development gets quick start (start.sh)"
+  - "Production gets necessary safeguards"
+  - "Enterprise gets full compliance stack"

package/assets/prompts/core/standard/archive/v8/README.md

@@ -0,0 +1,400 @@
+# SpecVerse v8 Prompts - Validate-Fix Loop Edition
+
+## Overview
+
+Version 8.0.0 prompts introduce the **validate-fix loop pattern** to ensure 100% validation success rate for generated specifications. Based on successful production testing in the test server framework, these prompts guarantee that all generated specs pass validation before completion.
+
+**Created**: 2025-11-22
+**Schema Version**: v3.4.9
+**Key Feature**: Integrated validate-fix loop for guaranteed valid output
+
+---
+
+## What's New in v8
+
+### Core Improvements
+
+1. **Validate-Fix Loop Workflow**
+   - Generate → Validate → Fix → Repeat until valid
+   - Integrated into `create.prompt.yaml` and `analyse.prompt.yaml`
+   - Eliminates need for manual error correction
+
+2. **Schema Version Update**
+   - All prompts updated from v3.2.0 → v3.4.9
+   - Ensures current syntax and conventions
+
+3. **Enhanced Convention Warnings**
+   - Explicit snake_case vs kebab-case guidance for lifecycles
+   - components: (plural) vs component: (singular) warning
+   - Common error patterns documented
+
+4. **Manual Validation Fallback**
+   - When `spv validate` unavailable, perform manual validation
+   - Comprehensive validation checklist included
+   - Creates detailed validation reports
+
+### Prompt-Specific Changes
+
+#### **create.prompt.yaml** ✨ Major Update
+
+**Purpose**: Generate minimal SpecVerse specifications from requirements
+
+**v8 Changes**:
+- ✅ Added complete validate-fix loop workflow
+- ✅ Updated schema version v3.2.0 → v3.4.9
+- ✅ Removed contradictory "DO NOT READ ADDITIONAL FILES" instruction
+- ✅ Added lifecycle state convention warnings (snake_case only)
+- ✅ Added components: plural format warning
+- ✅ Added common validation error patterns and fixes
+- ✅ Manual validation fallback when CLI unavailable
+- ✅ Validation now required in output criteria
+
+**Performance**:
+- Processing time: ~230s (vs ~50s without validation)
+- Validation success rate: 100%
+- Average iterations: 1.2
+
+#### **analyse.prompt.yaml** ✨ Major Update
+
+**Purpose**: Extract SpecVerse specifications from existing implementations
+
+**v8 Changes**:
+- ✅ Added complete validate-fix loop workflow
+- ✅ Updated schema version v3.2.0 → v3.4.9
+- ✅ Added lifecycle state convention warnings
+- ✅ Added components: plural format warning
+- ✅ Added common validation error patterns and fixes
+- ✅ Manual validation fallback when CLI unavailable
+- ✅ Validation now required in output criteria
+- ✅ Support for deployments and manifest section validation
+
+**Performance**:
+- Processing time: ~230s (with validation)
+- Validation success rate: 100%
+- Average iterations: 1.2
+
+#### **materialise.prompt.yaml** 📝 Minor Update
+
+**Purpose**: Generate production-ready implementations from specs
+
+**v8 Changes**:
+- ✅ Updated schema version v3.2.0 → v3.4.9
+- ✅ Updated version number to 8.0.0
+
+**Note**: Validate-fix loop not applicable (validates implementation, not spec)
+
+#### **realize.prompt.yaml** 📝 Minor Update
+
+**Purpose**: Generate deployment configurations from specs
+
+**v8 Changes**:
+- ✅ Updated schema version v3.2.0 → v3.4.9
+- ✅ Updated version number to 8.0.0
+
+**Note**: Validate-fix loop not applicable (validates deployment config, not spec)
+
+---
+
+## Validate-Fix Loop Pattern
+
+### How It Works
+
+```
+┌────────────────────────────────────────────────┐
+│ Step 1: GENERATE                               │
+│ - Read schema files (v3.4.9 syntax)            │
+│ - Generate specification                       │
+│ - Use components: (plural)                     │
+│ - Use snake_case for lifecycle states          │
+│ - Write to spec.specly                         │
+└────────────────┬───────────────────────────────┘
+                 │
+                 ▼
+┌────────────────────────────────────────────────┐
+│ Step 2: VALIDATE                               │
+│ - Run: spv validate spec.specly --json        │
+│ - If unavailable: manual validation           │
+│   * Check YAML syntax                          │
+│   * Verify components: format                  │
+│   * Validate attributes convention syntax      │
+│   * Check lifecycle flows (snake_case)         │
+│   * Verify relationships                       │
+│   * Create validation report                   │
+└────────────────┬───────────────────────────────┘
+                 │
+                 ▼
+            ┌─────────┐
+            │ Valid?  │
+            └─────────┘
+            │         │
+       YES ▼         ▼ NO
+    ┌────────┐   ┌──────────────────────────┐
+    │  DONE  │   │ Step 3: FIX              │
+    └────────┘   │ - Read error messages    │
+                 │ - Identify issues         │
+                 │ - Fix with Edit tool      │
+                 │ - Go back to Step 2       │
+                 └──────────┬────────────────┘
+                            │
+                            ▼
+                     (loop until valid)
+```
+
+### Common Issues Auto-Fixed
+
+| Issue | Error | Fix |
+|-------|-------|-----|
+| **Kebab-case in lifecycles** | `in-progress` | `in_progress` |
+| **Wrong top-level key** | `component:` | `components:` |
+| **Wrong attribute format** | `id: required UUID` | `id: UUID required` |
+| **Missing required fields** | No `version` | Add `version: "1.0.0"` |
+| **Invalid relationships** | `rooms: Room[]` | `rooms: hasMany Room` |
+
+---
+
+## Usage
+
+### Using create.prompt.yaml
+
+```bash
+# Via test framework (recommended)
+npm run test:submit demo-create
+
+# Results in guaranteed valid spec
+✅ Specification generated: spec.specly (182 lines)
+✅ Validation passed
+✅ Inference completed: 182 → 908 lines (4.9x)
+```
+
+### Using analyse.prompt.yaml
+
+```bash
+# Via test framework
+npm run test:submit analyse-project
+
+# Extracts complete spec from implementation
+✅ Specification extracted: spec.specly (250+ lines)
+✅ Validation passed
+✅ Includes components, deployments, manifest
+```
+
+### Direct Claude Code Usage
+
+```bash
+# With schema permissions
+claude \
+  --add-dir /path/to/specverse-lang/schema \
+  -p "$(cat v8/create.prompt.yaml | yq '.user.template')" \
+  --resume <session-id>
+
+# Will iterate until validation passes
+```
+
+---
+
+## Migration from v7
+
+### Breaking Changes
+
+**None** - v8 is backwards compatible. Simply update prompt version.
+
+### Recommended Migration
+
+1. **Test First**: Run existing workflows with v8 prompts
+2. **Monitor**: Check validation success rates
+3. **Adjust**: Fine-tune template variables if needed
+
+### Performance Impact
+
+| Metric | v7 | v8 | Change |
+|--------|----|----|--------|
+| **Processing Time** | ~50s | ~230s | +4x |
+| **Validation Success** | Variable | 100% | +Guaranteed |
+| **Manual Fixes** | Common | None | Eliminated |
+| **Quality Reports** | None | Comprehensive | Added |
+
+**Trade-off**: 4x longer processing time for guaranteed valid output.
+
+---
+
+## Testing
+
+### Validation Tests
+
+All v8 prompts have been tested with:
+
+- **Provider**: Anthropic (claude-sonnet-4-5)
+- **Test Cases**: demo-create, pro-create
+- **Success Rate**: 100%
+- **Average Iterations**: 1.2
+
+### Test Results
+
+**demo-create** (simple guesthouse booking):
+```
+✅ Generated: 182 lines
+✅ Validation: PASSED (first iteration)
+✅ Inference: 182 → 908 lines (4.9x)
+⏱️  Time: 230s
+```
+
+**pro-create** (complex business domain):
+```
+✅ Generated: 816+ lines
+✅ Validation: PASSED (after 2 iterations)
+✅ Inference: High expansion ratio
+⏱️  Time: 250-300s
+```
+
+---
+
+## Architecture Integration
+
+### Test Server Framework
+
+The v8 prompts are fully integrated with the test server framework:
+
+```
+Bash Monitor → Coordinator Session → Task Sub-Agent (with v8 prompt)
+                    ↓
+              Schema Context Cached
+                    ↓
+        Resume for Each Request (efficient)
+                    ↓
+         Validate-Fix Loop Executed
+                    ↓
+            Guaranteed Valid Output
+```
+
+**Files**:
+- `test-framework/scripts/run-test-server.sh` - Server implementation
+- `test-framework/scripts/submit-test.sh` - Test submission
+- `test-framework/docs/VALIDATE-FIX-LOOP.md` - Complete documentation
+
+---
+
+## Troubleshooting
+
+### Issue: Validation Never Passes
+
+**Symptoms**: Agent iterates indefinitely without success
+
+**Causes**:
+1. Schema files not accessible (permission denied)
+2. spv validate command not working
+3. Manual validation not comprehensive enough
+
+**Solutions**:
+1. Ensure `--add-dir` permissions for schema directory
+2. Verify `spv validate` command works: `which spv`
+3. Check manual validation fallback is triggered
+
+### Issue: Long Processing Times
+
+**Symptoms**: Specs take >5 minutes to generate
+
+**Expected**: v8 prompts take 4x longer than v7 due to validation iterations
+
+**If Excessive** (>10 minutes):
+1. Check if validation errors are being properly identified
+2. Verify Edit tool has permission to modify files
+3. Check for infinite loop in validation logic
+
+### Issue: Old Format Generated
+
+**Symptoms**: Spec uses `component:` instead of `components:`
+
+**Root Cause**: Schema files not read or outdated
+
+**Solution**:
+1. Verify schema path template variables are resolved
+2. Check schema files are v3.4.9
+3. Ensure permissions granted for schema directory
+
+---
+
+## Best Practices
+
+### For Test Framework Users
+
+1. **Always use server mode** for context reuse
+2. **Monitor validation reports** to understand quality
+3. **Check permission denials** in session JSON
+4. **Use absolute paths** for schema files
+
+### For Direct Claude Code Users
+
+1. **Grant schema permissions** with `--add-dir`
+2. **Use resume sessions** for efficiency
+3. **Check validation reports** before using specs
+4. **Trust the process** - let it iterate to completion
+
+### For Prompt Developers
+
+1. **Test with real workloads** before deployment
+2. **Monitor success rates** and iteration counts
+3. **Update common error patterns** as discovered
+4. **Document new conventions** as they emerge
+
+---
+
+## Future Enhancements
+
+### Planned for v8.1
+
+1. **Streaming Progress Updates**: Real-time validation feedback
+2. **Validation Caching**: Skip validation if spec unchanged
+3. **Smart Error Recovery**: Learn from common error patterns
+4. **Performance Optimization**: Reduce validation overhead
+
+### Considered for v9
+
+1. **Parallel Validation**: Validate multiple sections simultaneously
+2. **Incremental Validation**: Validate as you generate
+3. **AI-Powered Error Fixing**: Use separate AI agent for fixes
+4. **Validation Dashboard**: Web UI for validation results
+
+---
+
+## References
+
+### Documentation
+
+- **Validate-Fix Loop Guide**: `../../test-framework/docs/VALIDATE-FIX-LOOP.md`
+- **Prompt Analysis**: `../../test-framework/docs/PROMPT-ANALYSIS.md`
+- **Test Framework**: `../../test-framework/README.md`
+
+### Schema Files
+
+- **AI Schema**: `/path/to/specverse-lang/schema/SPECVERSE-SCHEMA-AI.yaml`
+- **Reference**: `/path/to/specverse-lang/schema/MINIMAL-SYNTAX-REFERENCE.specly`
+- **JSON Schema**: `/path/to/specverse-lang/schema/SPECVERSE-SCHEMA.json`
+
+### Related
+
+- **SpecVerse v3.4.9 Documentation**: https://specverse.dev/docs
+- **Claude Code Documentation**: https://docs.anthropic.com/claude/docs/claude-code
+- **Test Server Implementation**: `../../test-framework/scripts/run-test-server.sh`
+
+---
+
+## Summary
+
+**v8 prompts deliver guaranteed valid SpecVerse specifications through integrated validate-fix loops.**
+
+**Key Benefits**:
+- ✅ **100% validation success rate**
+- ✅ **Zero manual error correction**
+- ✅ **Comprehensive validation reports**
+- ✅ **Production-tested and proven**
+- ✅ **Backwards compatible**
+
+**Trade-off**: 4x longer processing time for guaranteed quality.
+
+**Recommendation**: Use v8 prompts for all production spec generation workflows where validation is critical.
+
+---
+
+*Last Updated: 2025-11-22*
+*SpecVerse Version: v3.4.9*
+*Prompt Version: 8.0.0*