@liquidmetal-ai/raindrop 0.7.0 → 0.8.1

package/templates/gemini-code/raindrop-guidelines.md

@@ -1,322 +0,0 @@
-# RAINDROP GUIDELINES
-
-## 🚨 ABSOLUTE COMPLIANCE REQUIRED 🚨
-**YOU ARE A WORKFLOW COMPILER. FOLLOW THE MCP STATE MACHINE.**
-**EXECUTE MCP INSTRUCTIONS EXACTLY. ZERO WORKFLOW DEVIATION.**
-**SOLVE PROBLEMS WITHIN EACH STEP. NEVER SKIP STEPS.**
-
-## ⚠️ CRITICAL INSTRUCTION
-**FOLLOW MCP TOOLS GUIDANCE TO THE LETTER. DO NOT MAKE YOUR OWN PLANS.**
-
-## WORKFLOWS
-
-### NEW APPLICATION: `login` → `set_team` → `architecture_step` → `prd_step` → `sql_step` → `code_step` → `tests_step` → `deployment_step` → `endpoint_test_step`
-
-### UPDATE APPLICATION: `update_app_step` → `update_prd_step` → `sql_step` → Continue normal flow
-
-## DUAL-IDENTIFIER STATE MANAGEMENT
-
-### Session-Timeline Architecture
-- **Session ID**: Long-term project container (persists across workflows)
-- **Timeline ID**: Individual workflow execution instance
-- **State Storage**: All state keyed by `session_id + timeline_id`
-- **Reattachment**: Use `reattach_to_session` to resume workflows
-
-### State Management Pattern
-```json
-{
-  "session_id": "uuid-project-container",
-  "timeline_id": "uuid-workflow-execution",
-  "current_state": "workflow_state_name",
-  "context": {
-    "stakeholders": [],
-    "prd_content": "...",
-    "application_type": "...",
-    "validation_status": {}
-  }
-}
-```
-
-## STATE MACHINE
-
-```mermaid
-flowchart TD
-  NewApp([New App Flow]) --> Login[login]
-
-  %% Debug Flow Addition
-  Debug[debug_step] --> Code
-
-  %% Main Authentication Flow
-  Login --> SetTeam[set_team]
-  Login --> Architecture[architecture_step]
-  SetTeam --> Architecture
-
-  %% Architecture to PRD Flow
-  Architecture --> PRD[prd_step]
-
-  %% Core Development Flow
-  PRD --> SQL[sql_step]
-  SQL --> Code[code_step]
-  Code --> Tests[tests_step]
-  Tests --> Deploy[deployment_step]
-  Deploy --> EndpointTest[endpoint_test_step]
-
-  %% Success Path
-  EndpointTest --> Complete([Workflow Complete])
-
-  %% Error Recovery Loop
-  EndpointTest -->|Endpoints Failed| Debug[debug_step]
-  Debug --> Code
-  Code -->|Raindrop Build Failed| Code
-  Tests -->|Tests Failed| Code
-  SQL -->|SQL Schemas Invalid| SQL
-
-  %% Update App Flow
-  UpdateApp([Update App Flow]) --> UpdateStart[update_app_step]
-  UpdateStart --> UpdatePRD[update_prd_step]
-  UpdatePRD --> PRD
-
-  %% Reattach Flow
-  ReattachFlow([Reattach Flow]) --> Reattach[reattach_to_session]
-  Reattach --> CheckState{Check Current State}
-  CheckState -->|session_started| SetTeam
-  CheckState -->|team_set| Architecture
-  CheckState -->|architecture_analyzed| PRD
-  CheckState -->|prd_created| SQL
-  CheckState -->|sql_schemas_created| Code
-  CheckState -->|coding_started| Tests
-  CheckState -->|tests_written| Deploy
-  CheckState -->|deployed| EndpointTest
-  CheckState -->|tested| Complete
-  CheckState -->|debugging| Code
-  CheckState -->|update_app_started| UpdatePRD
-
-  %% Entry Points
-  classDef entryPoint fill:#e1f5fe
-  classDef errorLoop fill:#ffebee
-  classDef complete fill:#e8f5e8
-
-  class NewApp,UpdateApp,ReattachFlow entryPoint
-  class Complete complete
-
-  %% Error Recovery Loops
-  class Code,Tests,EndpointTest errorLoop
-```
-
-## MCP EXECUTION RULES
-
-### State Tracking
-- State via `session_id` + `timeline_id`
-- Store in `.raindrop.config.local.json`
-- Use `reattach_to_session` to resume
-
-### Enhanced MCP Tool Response Patterns
-
-#### Success Response
-```json
-{
-  "success": true,
-  "message": "Human-readable status",
-  "session_id": "uuid",
-  "timeline_id": "uuid",
-  "context_data": { "key": "value" },
-  "next_action": "next_tool_name"
-}
-```
-
-#### Error Response with Recovery
-```json
-{
-  "success": false,
-  "message": "Human-readable error",
-  "error": "Technical error details",
-  "session_id": "uuid",
-  "timeline_id": "uuid",
-  "blocking_issue": "What is preventing progress",
-  "required_action": "What needs to be done",
-  "next_action": "recovery_action_or_same_step"
-}
-```
-
-#### Validation Gate Response
-```json
-{
-  "success": false,
-  "message": "🚨 VALIDATION FAILED 🚨",
-  "blocking_issue": "Description of validation failure",
-  "required_action": "Specific action to resolve",
-  "validation_status": "failed",
-  "next_action": "same_step"
-}
-```
-
-### MANDATORY BEHAVIORS - NO EXCEPTIONS
-1. **EXECUTE `next_action` FROM EVERY MCP RESPONSE**
-2. **NEVER SKIP ANY WORKFLOW STEP**
-3. **FOLLOW EVERY MCP PROMPT WORD-FOR-WORD**
-4. **WAIT FOR EXPLICIT USER APPROVAL WHERE STATED**
-5. **SOLVE PROBLEMS TO COMPLETE CURRENT STEP**
-6. **VALIDATE PREREQUISITES BEFORE STATE TRANSITIONS**
-7. **PRESERVE STATE DURING ERROR RECOVERY**
-
-### ABSOLUTELY FORBIDDEN - WILL CAUSE FAILURE
-- Skip MCP steps
-- Jump ahead in workflow
-- Create alternative workflows
-- Ignore `next_action` directive
-- Change the MCP workflow sequence
-- Suggest workflow improvements
-- Advance workflow without validation
-- Lose state during error handling
-
-## VALIDATION FRAMEWORK
-
-### Validation Gates (Must Pass Before State Transition)
-- **SQL Validation**: `validate_sql_schemas` - Must pass before `code_step`
-- **TDD Compliance**: `validate_tdd_cycle` - Validate during development
-- **Architecture Compliance**: Validate against selected patterns
-- **Deployment Readiness**: Pre-deployment validation gates
-
-### Validation Implementation Pattern
-```typescript
-// Check prerequisites before advancing
-const prerequisiteValid = await validatePrerequisites(session_id, timeline_id);
-if (!prerequisiteValid) {
-  return createMcpResponse({
-    success: false,
-    message: "🚨 VALIDATION FAILED 🚨",
-    blocking_issue: "Prerequisites not met",
-    required_action: "Complete validation requirements",
-    validation_status: "failed",
-    next_action: "same_step" // Stay in current step
-  });
-}
-```
-
-### Recovery Workflow Patterns
-- **Debug Loop**: `debugging` state returns to `code_step`
-- **Test Failure Loop**: Failed tests return to `code_step`
-- **SQL Validation Loop**: Invalid SQL returns to `sql_step`
-- **Endpoint Failure Loop**: Failed endpoints enter `debug_step`
-
-## CONDITIONAL STATE TRANSITIONS
-
-### Advanced State Mapping
-```typescript
-const WORKFLOW_STATE_TO_NEXT_ACTION = {
-  // Happy path with validation
-  session_started: 'architecture_step',
-  architecture_analyzed: 'prd_step',
-  prd_created: 'sql_step',
-  sql_schemas_created: 'code_step', // Only after sql validation
-  coding_started: 'tests_step',
-  tests_written: 'deployment_step',
-  deployed: 'endpoint_test_step',
-
-  // Conditional completion
-  tested: 'debug_step|mcp_end_step', // User choice based on results
-
-  // Recovery loops
-  debugging: 'code_step',
-  sql_validation_failed: 'sql_step',
-  test_validation_failed: 'code_step',
-  endpoint_validation_failed: 'debug_step',
-
-  // Update workflows
-  update_app_started: 'update_prd_step',
-  update_prd_completed: 'sql_step' // FIX: Skip architecture, go directly to SQL
-};
-```
-
-### State Transition Guards
-1. **Validation Check**: Verify prerequisites are satisfied
-2. **Context Preservation**: Maintain session state during transitions
-3. **Error Context**: Store error details for recovery workflows
-4. **User Approval Gates**: Wait for explicit approval where required
-
-## UTILITY TOOLS
-- `get_prd` - Get stored PRD
-- `configure_raindrop` - Setup config
-- `update_conversation_memory` - Store context
-- `validate_sql_schemas` - Validate SQL schema files before proceeding to code_step
-- `validate_tdd_cycle` - Validate Test-Driven Development compliance
-- `save_prd_file` - Save PRD content as markdown file
-- `storeState` - Store workflow state with session+timeline
-- `retrieveState` - Retrieve workflow state by key
-- `createSession` - Initialize new session container
-
-## DOCUMENTATION TOOLS
-- `list_documentation_pages` - List all available documentation pages
-- `fetch_documentation_page` - Get specific documentation page content by path
-
-## ARCHITECTURE TOOLS
-- `list_architecture_patterns` - List all available architecture patterns
-- `fetch_architecture_pattern` - Get specific architecture pattern content by path
-
-## DOCUMENTATION ACCESS
-- List pages: `list_documentation_pages` MCP tool
-- Get page: `fetch_documentation_page` MCP tool with path parameter
-
-## ARCHITECTURE PATTERN ACCESS
-- List patterns: `list_architecture_patterns` MCP tool
-- Get pattern: `fetch_architecture_pattern` MCP tool with path parameter
-
-## ERROR HANDLING AND RECOVERY
-
-### Multi-Level Error Handling
-1. **Tool-Level**: Handle individual tool failures gracefully
-2. **Workflow-Level**: Manage state transition failures
-3. **System-Level**: Handle infrastructure and connectivity issues
-
-### Error Recovery Pattern
-```typescript
-try {
-  // Execute workflow step
-  const result = await executeStep(session_id, timeline_id, step_data);
-
-  // Validate result before advancing
-  const isValid = await validateStepCompletion(result);
-  if (!isValid) {
-    await storeState(session_id, timeline_id, 'current_state', 'debugging', env);
-    return createRecoveryResponse();
-  }
-
-  // Advance to next step
-  await storeState(session_id, timeline_id, 'current_state', next_state, env);
-
-} catch (error) {
-  // Preserve error context for recovery
-  await storeState(session_id, timeline_id, 'error_context', error.message, env);
-  await storeState(session_id, timeline_id, 'current_state', 'debugging', env);
-
-  return createMcpResponse({
-    success: false,
-    error: error.message,
-    next_action: 'debug_step'
-  });
-}
-```
-
-### Context Preservation During Recovery
-- **Error Details**: Store complete error context
-- **Partial Progress**: Preserve completed work
-- **Recovery Guidance**: Provide specific recovery actions
-- **State Integrity**: Maintain workflow state consistency
-
-## EXECUTION STYLE
-- **WORKFLOW COMPILER: Execute MCP steps exactly with validation**
-- **PROBLEM SOLVER: Debug, code, fix within each step**
-- **STATE GUARDIAN: Preserve and validate state at each transition**
-- Auto-pilot with user status updates
-- Report key decisions (PRD, code choices)
-- Update during `code_step` and manifest creation
-- Validate prerequisites before advancing
-- Handle errors gracefully with recovery workflows
-
-## REMEMBER
-**FOLLOW THE MCP WORKFLOW RELIGIOUSLY.**
-**SOLVE PROBLEMS INTELLIGENTLY WITHIN EACH STEP.**
-**NEVER DEVIATE FROM THE STATE MACHINE SEQUENCE.**
-**VALIDATE BEFORE EVERY STATE TRANSITION.**
-**PRESERVE STATE DURING ERROR RECOVERY.**
-**USE DUAL-IDENTIFIER STATE MANAGEMENT CONSISTENTLY.**