@liquidmetal-ai/raindrop 0.7.0 → 0.8.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@liquidmetal-ai/raindrop",
   "description": "CLI for the Raindrop platform",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "author": "bosgood",
   "bin": {
     "raindrop": "./bin/run.js"
@@ -22,7 +22,9 @@
     "changeset": "^0.2.6",
     "cli-table3": "^0.6.5",
     "date-fns": "^4.1.0",
+    "es-module-lexer": "^1.5.4",
     "esbuild": "^0.24.0",
+    "glob": "^10.0.0",
     "handlebars": "^4.7.8",
     "hcl2-json-parser": "^1.0.1",
     "npx": "^10.2.2",
@@ -34,8 +36,8 @@
     "typescript": "^5",
     "zod": "^3.23.8",
     "zx": "^8.1.9",
-    "@liquidmetal-ai/drizzle": "0.7.0",
-    "@liquidmetal-ai/raindrop-framework": "0.7.0"
+    "@liquidmetal-ai/raindrop-framework": "0.8.0",
+    "@liquidmetal-ai/drizzle": "0.8.0"
   },
   "devDependencies": {
     "@changesets/cli": "^2.27.9",
@@ -70,6 +72,7 @@
   "files": [
     "/bin",
     "/dist",
+    "/bundle",
     "/oclif.manifest.json",
     "/templates"
   ],
@@ -83,7 +86,7 @@
   "oclif": {
     "bin": "raindrop",
     "dirname": "raindrop",
-    "commands": "./dist/commands",
+    "commands": "./bundle/commands",
     "plugins": [
       "@oclif/plugin-help",
       "@oclif/plugin-plugins"
@@ -111,7 +114,7 @@
     }
   },
   "scripts": {
-    "build": "tsc -b",
+    "build": "node scripts/build.js && tsc -b",
     "clean": "shx rm -rf dist",
     "format": "prettier --write \"**/*.{ts,tsx,md}\"",
     "lint": "eslint . --max-warnings=0",

package/templates/claude-code/debug-raindrop-app.md

@@ -0,0 +1,89 @@
+---
+allowed-tools: mcp__raindrop-mcp, Read, Bash, WebFetch
+description: Debug an existing deployed Raindrop application
+argument-hint: [session_id]
+---
+
+WARNING: If you cannot find the "raindrop-mcp" server or the "get-prompt" tool for the "raindrop-mcp" server, respond with:
+"Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
+
+Before debugging, run `raindrop auth login` to authenticate. When the command returns, authentication is complete.
+
+After authentication:
+
+1. If session_id is provided as $ARGUMENTS, use it and skip to step 5
+
+2. Otherwise, read `~/.raindrop/index.json` to get applications and sessions:
+   - File format:
+     ```json
+     {
+       "applications": {
+         "my-app": {
+           "latest_session_id": "sess_abc123",
+           "sessions": [...]
+         }
+       },
+       "sessions": {
+         "sess_abc123": {
+           "session_id": "sess_abc123",
+           "timeline_id": "timeline_456",
+           "created_at": "...",
+           "current_state": "...",
+           "application_name": "my-app"
+         }
+       }
+     }
+     ```
+
+3. Handle application selection:
+   - If no applications exist, respond: "No Raindrop applications found. Use /new-raindrop-app to create one."
+   - If one application exists, use its `latest_session_id`
+   - If multiple applications exist:
+     * List all application names with their current state and last updated time
+     * Ask user: "Which application would you like to debug?"
+     * Use the selected application's `latest_session_id`
+
+4. If no session_id found, ask the user for it
+
+5. Call mcp__raindrop-mcp__get-prompt with session_id to rehydrate session context
+
+6. Spawn a diagnostic subagent with this prompt:
+   "You are debugging a deployed Raindrop application.
+
+   Session ID: [session_id from step 5]
+   Timeline ID: [timeline_id from step 5]
+   Application Name: [application_name from step 5]
+   Application Type: [application_type from step 5]
+
+   Your task:
+   1. Ask user: 'What issues are you experiencing with your deployed application?'
+   2. Gather diagnostic information:
+      - Run: raindrop logs [application_name] --tail 100
+      - Based on application_type, test endpoints/tools:
+        * For API: Test endpoints from interface_design
+        * For MCP: Test MCP tools
+        * For CLI: Test commands
+      - Record failures and error messages
+   3. Aggregate test results into this format:
+      {
+        total_endpoints: X,
+        passing: Y,
+        failing: Z,
+        failure_details: ['endpoint/tool: error message', ...]
+      }
+   4. Call mcp__raindrop-mcp__update-state with:
+      - session_id: [session_id]
+      - timeline_id: [timeline_id]
+      - artifacts: {
+          current_state: 'debug_analyze',
+          is_debugging: true,
+          test_results: [results from step 3]
+        }
+      - status: 'complete'
+   5. Call mcp__raindrop-mcp__get-prompt with session_id
+   6. Return the orchestrator_instructions from the response
+
+   Do not output messages to user beyond the initial question. Work autonomously and return orchestrator instructions."
+
+7. Wait for the subagent to return orchestrator_instructions
+8. The orchestrator will take over and spawn subagents for debug_analyze → debug_fix → retesting → redeployment

package/templates/claude-code/new-raindrop-app.md

@@ -1,9 +1,13 @@
-# ~/.claude/commands/new-raindrop-app.md
+allowed-tools: mcp\_\_raindrop-mcp, Write, Bash
+description: Create a new Raindrop application from scratch
 
-Create a new Raindrop application from scratch.
+WARNING: If you cannot find the "raindrop-mcp" server or the "get-prompt" tool for the "raindrop-mcp" server, respond with:
+"Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
 
-- Call the raindrop-mcp:login MCP tool to start a new development session.
-- Do whatever the MCP endpoint returns and continue with the flow it defines
+Before starting the workflow, run `raindrop auth login` to authenticate. When the command returns, authentication is complete.
 
-WARNING: If you cannot find the "raindrop-mcp" server or the "login" tool for the "raindrop-mcp" server, respond with:
-"Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
+After authentication, call the mcp**raindrop-mcp**get-prompt function without any parameters to start a new development session. This will automatically create a new session and return initial workflow instructions.
+
+The workflow will create a session cache directory at ~/.raindrop/<session_id>/ to store all artifacts and session metadata locally.
+
+Follow the instructions returned and continue with the development workflow, using mcp**raindrop-mcp**update-state to report task completion.

package/templates/claude-code/reattach-raindrop-session.md

@@ -1,12 +1,50 @@
-Reattach to an existing Raindrop development session.
-
-Steps
-1. Parse the arguments
-  - Split by whitespace to get individual values
-  - First value = session_id (if provided)
-  - Second value = old_timeline_id (if provided)
-
-2. If no timeline and session ID provided check the `.raindrop.config.local.json` file to determine the last session_id and old_timeline id
-3. If no input provided and no `.raindrop.config.local.json` file exists ask the user for input.
-4. Call the `reattach_to_session` MCP endpoint.
-5. Do whatever the MCP endpoint returns and continue with the flow it defines
+---
+allowed-tools: mcp__raindrop-mcp, Read
+description: Reattach to an existing Raindrop development session
+argument-hint: [session_id]
+---
+
+WARNING: If you cannot find the "raindrop-mcp" server or the "get-prompt" tool for the "raindrop-mcp" server, respond with:
+"Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
+
+Before reattaching, run `raindrop auth login` to authenticate. When the command returns, authentication is complete.
+
+After authentication:
+
+1. If session_id is provided as $ARGUMENTS, use it and skip to step 5
+
+2. Otherwise, read `~/.raindrop/index.json` to get applications and sessions:
+   - File format:
+     ```json
+     {
+       "applications": {
+         "my-app": {
+           "latest_session_id": "sess_abc123",
+           "sessions": [...]
+         }
+       },
+       "sessions": {
+         "sess_abc123": {
+           "session_id": "sess_abc123",
+           "timeline_id": "timeline_456",
+           "created_at": "...",
+           "current_state": "...",
+           "application_name": "my-app"
+         }
+       }
+     }
+     ```
+
+3. Handle application selection:
+   - If no applications exist, respond: "No Raindrop applications found. Use /new-raindrop-app to create one."
+   - If one application exists, use its `latest_session_id`
+   - If multiple applications exist:
+     * List all application names with their current state and last updated time
+     * Ask user: "Which application would you like to reattach to?"
+     * Use the selected application's `latest_session_id`
+
+4. If no session_id found, ask the user for it
+
+5. Call mcp__raindrop-mcp__get-prompt with the session_id parameter
+
+6. Follow the instructions returned and continue with the development workflow

package/templates/claude-code/update-raindrop-app.md

@@ -1,11 +1,63 @@
-Update an existing Raindrop application with new features or changes.
+---
+allowed-tools: mcp__raindrop-mcp, Read, Bash
+description: Add new features to an existing Raindrop application
+argument-hint: [session_id]
+---
 
-Steps
-1. Parse the arguments
-  - Split by whitespace to get individual values
-  - First value = session_id (if provided)
-  - Second value = old_timeline_id (if provided)
+WARNING: If you cannot find the "raindrop-mcp" server or the "get-prompt" tool for the "raindrop-mcp" server, respond with:
+"Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
 
-2. If no timeline and session ID provided check the `.raindrop.config.local.json` file to determine the last session_id and old_timeline id
-3. If no input provided and no `.raindrop.config.local.json` file exists ask the user for input.
-4. Call the `update_app_step` MCP endpoint.
+Before updating, run `raindrop auth login` to authenticate. When the command returns, authentication is complete.
+
+After authentication:
+
+1. If session_id is provided as $ARGUMENTS, use it and skip to step 5
+
+2. Otherwise, read `~/.raindrop/index.json` to get applications and sessions:
+   - File format:
+     ```json
+     {
+       "applications": {
+         "my-app": {
+           "latest_session_id": "sess_abc123",
+           "sessions": [...]
+         }
+       },
+       "sessions": {
+         "sess_abc123": {
+           "session_id": "sess_abc123",
+           "timeline_id": "timeline_456",
+           "created_at": "...",
+           "current_state": "...",
+           "application_name": "my-app"
+         }
+       }
+     }
+     ```
+
+3. Handle application selection:
+   - If no applications exist, respond: "No Raindrop applications found. Use /new-raindrop-app to create one."
+   - If one application exists, use its `latest_session_id`
+   - If multiple applications exist:
+     * List all application names with their current state and last updated time
+     * Ask user: "Which application would you like to add features to?"
+     * Use the selected application's `latest_session_id`
+
+4. If no session_id found, ask the user for it
+
+5. Get the timeline_id from the session entry in index.json
+
+6. Call mcp__raindrop-mcp__update-state with the session_id, timeline_id, and these parameters:
+   ```json
+   {
+     "artifacts": {
+       "current_state": "merge_features"
+     },
+     "status": "complete"
+   }
+   ```
+   This jumps the workflow to the merge_features state for adding features.
+
+7. Call mcp__raindrop-mcp__get-prompt with the session_id parameter
+
+8. Follow the instructions returned and continue with the feature addition workflow

package/templates/db/node_modules/.bin/prisma

@@ -6,9 +6,9 @@ case `uname` in
 esac
 
 if [ -z "$NODE_PATH" ]; then
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/build/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/build/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules"
 else
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/build/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/build/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
 fi
 if [ -x "$basedir/node" ]; then
   exec "$basedir/node"  "$basedir/../../../../../../node_modules/.pnpm/prisma@6.10.1_typescript@5.9.2/node_modules/prisma/build/index.js" "$@"

package/templates/db/node_modules/.bin/prisma-kysely

@@ -6,9 +6,9 @@ case `uname` in
 esac
 
 if [ -z "$NODE_PATH" ]; then
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/dist/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/dist/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules"
 else
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/dist/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/dist/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/prisma-kysely@1.8.0/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
 fi
 if [ -x "$basedir/node" ]; then
   exec "$basedir/node"  "$basedir/../../../../../../node_modules/.pnpm/prisma-kysely@1.8.0/node_modules/prisma-kysely/dist/bin.js" "$@"

package/templates/db/node_modules/.bin/tsc

@@ -6,9 +6,9 @@ case `uname` in
 esac
 
 if [ -z "$NODE_PATH" ]; then
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules"
 else
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
 fi
 if [ -x "$basedir/node" ]; then
   exec "$basedir/node"  "$basedir/../../../../../../node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/tsc" "$@"

package/templates/db/node_modules/.bin/tsserver

@@ -6,9 +6,9 @@ case `uname` in
 esac
 
 if [ -z "$NODE_PATH" ]; then
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules"
 else
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/typescript@5.9.2/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
 fi
 if [ -x "$basedir/node" ]; then
   exec "$basedir/node"  "$basedir/../../../../../../node_modules/.pnpm/typescript@5.9.2/node_modules/typescript/bin/tsserver" "$@"

package/templates/db/node_modules/.bin/zx

@@ -6,9 +6,9 @@ case `uname` in
 esac
 
 if [ -z "$NODE_PATH" ]; then
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules/zx/build/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules/zx/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules/zx/build/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules/zx/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules"
 else
-  export NODE_PATH="/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules/zx/build/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules/zx/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules:/Users/mattbarto/code/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
+  export NODE_PATH="/Users/ian/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules/zx/build/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules/zx/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/zx@8.6.0/node_modules:/Users/ian/liquidmetal/node_modules/.pnpm/node_modules:$NODE_PATH"
 fi
 if [ -x "$basedir/node" ]; then
   exec "$basedir/node"  "$basedir/../../../../../../node_modules/.pnpm/zx@8.6.0/node_modules/zx/build/cli.js" "$@"

package/templates/gemini-code/debug-raindrop-app.toml

@@ -0,0 +1,86 @@
+description = "Debug an existing deployed Raindrop application"
+prompt = """
+WARNING: If you cannot find the "raindrop-mcp" server or the "get-prompt" tool for the "raindrop-mcp" server, respond with:
+"Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
+
+Before debugging, run `raindrop auth login` to authenticate. When the command returns, authentication is complete.
+
+After authentication:
+
+1. If session_id is provided in {{args}}, use it and skip to step 5
+
+2. Otherwise, read `~/.raindrop/index.json` to get applications and sessions:
+   - File format:
+     ```json
+     {
+       "applications": {
+         "my-app": {
+           "latest_session_id": "sess_abc123",
+           "sessions": [...]
+         }
+       },
+       "sessions": {
+         "sess_abc123": {
+           "session_id": "sess_abc123",
+           "timeline_id": "timeline_456",
+           "created_at": "...",
+           "current_state": "...",
+           "application_name": "my-app"
+         }
+       }
+     }
+     ```
+
+3. Handle application selection:
+   - If no applications exist, respond: "No Raindrop applications found. Use /new-raindrop-app to create one."
+   - If one application exists, use its `latest_session_id`
+   - If multiple applications exist:
+     * List all application names with their current state and last updated time
+     * Ask user: "Which application would you like to debug?"
+     * Use the selected application's `latest_session_id`
+
+4. If no session_id found, ask the user for it
+
+5. Call the `get-prompt` tool (from raindrop-mcp server) with session_id to rehydrate session context
+
+6. Spawn a diagnostic subagent with this prompt:
+   "You are debugging a deployed Raindrop application.
+
+   Session ID: [session_id from step 5]
+   Timeline ID: [timeline_id from step 5]
+   Application Name: [application_name from step 5]
+   Application Type: [application_type from step 5]
+
+   Your task:
+   1. Ask user: 'What issues are you experiencing with your deployed application?'
+   2. Gather diagnostic information:
+      - Run: raindrop logs [application_name] --tail 100
+      - Based on application_type, test endpoints/tools:
+        * For API: Test endpoints from interface_design
+        * For MCP: Test MCP tools
+        * For CLI: Test commands
+      - Record failures and error messages
+   3. Aggregate test results into this format:
+      {
+        total_endpoints: X,
+        passing: Y,
+        failing: Z,
+        failure_details: ['endpoint/tool: error message', ...]
+      }
+   4. Call the `update-state` tool (from raindrop-mcp server) with:
+      - session_id: [session_id]
+      - timeline_id: [timeline_id]
+      - artifacts: {
+          current_state: 'debug_analyze',
+          is_debugging: true,
+          test_results: [results from step 3]
+        }
+      - status: 'complete'
+   5. Call the `get-prompt` tool with session_id
+   6. Return the orchestrator_instructions from the response
+
+   Do not output messages to user beyond the initial question. Work autonomously and return orchestrator instructions."
+
+7. Wait for the subagent to return orchestrator_instructions
+8. The orchestrator will take over and spawn subagents for debug_analyze → debug_fix → retesting → redeployment
+"""

package/templates/gemini-code/new-raindrop-app.toml

@@ -1,8 +1,12 @@
 description = "Create a new Raindrop application from scratch"
 prompt = """
-Call the raindrop-mcp:login MCP tool to start a new development session.
-Do whatever the MCP endpoint returns and continue with the flow it defines.
-
-WARNING: If you cannot find the "raindrop-mcp" server or the "login" tool for the "raindrop-mcp" server, respond with:
+WARNING: If you cannot find the "raindrop-mcp" server or the "get-prompt" tool for the "raindrop-mcp" server, respond with:
 "Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
-"""
+
+Before starting the workflow, run `raindrop auth login` to authenticate. When the command returns, authentication is complete.
+
+After authentication, call the `get-prompt` tool (from the raindrop-mcp server) without any parameters to start a new development session. This will automatically create a new session and return initial workflow instructions.
+
+Follow the instructions returned and continue with the development workflow, using `update-state` to report task completion.
+"""
+

package/templates/gemini-code/reattach-raindrop-session.toml

@@ -1,17 +1,15 @@
 description = "Reattach to an existing Raindrop development session"
 prompt = """
-Reattach to an existing Raindrop development session following these steps:
+WARNING: If you cannot find the "raindrop-mcp" server or the "get-prompt" tool for the "raindrop-mcp" server, respond with:
+"Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
 
-1. Parse the arguments {{args}}:
-   - Split by whitespace to get individual values
-   - First value = session_id (if provided)
-   - Second value = old_timeline_id (if provided)
+Before reattaching, run `raindrop auth login` to authenticate. When the command returns, authentication is complete.
 
-2. If no timeline and session ID provided, check the `.raindrop.config.local.json` file to determine the last session_id and old_timeline_id
+After authentication, reattach to an existing Raindrop development session following these steps:
 
-3. If no input provided and no `.raindrop.config.local.json` file exists, ask the user for input
-
-4. Call the `reattach_to_session` MCP endpoint
-
-5. Do whatever the MCP endpoint returns and continue with the flow it defines
+1. If session_id is provided in {{args}}, use it
+2. Otherwise, read `.raindrop.config.local.json` to get the last session_id
+3. If no session_id found, ask the user for it
+4. Call the `get-prompt` tool (from raindrop-mcp server) with the session_id parameter
+5. Follow the instructions returned and continue with the development workflow
 """

package/templates/gemini-code/update-raindrop-app.toml

@@ -1,15 +1,60 @@
-description = "Update an existing Raindrop application with new features or changes"
+description = "Add new features to an existing Raindrop application"
 prompt = """
-Update an existing Raindrop application following these steps:
+WARNING: If you cannot find the "raindrop-mcp" server or the "get-prompt" tool for the "raindrop-mcp" server, respond with:
+"Please check your raindrop-mcp server status by running /mcp, and reauthenticate"
 
-1. Parse the arguments {{args}}:
-   - Split by whitespace to get individual values
-   - First value = session_id (if provided)
-   - Second value = old_timeline_id (if provided)
+Before updating, run `raindrop auth login` to authenticate. When the command returns, authentication is complete.
 
-2. If no timeline and session ID provided, check the `.raindrop.config.local.json` file to determine the last session_id and old_timeline_id
+After authentication:
 
-3. If no input provided and no `.raindrop.config.local.json` file exists, ask the user for input
+1. If session_id is provided in {{args}}, use it and skip to step 5
 
-4. Call the `update_app_step` MCP endpoint with the appropriate parameters
-"""
+2. Otherwise, read `~/.raindrop/index.json` to get applications and sessions:
+   - File format:
+     ```json
+     {
+       "applications": {
+         "my-app": {
+           "latest_session_id": "sess_abc123",
+           "sessions": [...]
+         }
+       },
+       "sessions": {
+         "sess_abc123": {
+           "session_id": "sess_abc123",
+           "timeline_id": "timeline_456",
+           "created_at": "...",
+           "current_state": "...",
+           "application_name": "my-app"
+         }
+       }
+     }
+     ```
+
+3. Handle application selection:
+   - If no applications exist, respond: "No Raindrop applications found. Use /new-raindrop-app to create one."
+   - If one application exists, use its `latest_session_id`
+   - If multiple applications exist:
+     * List all application names with their current state and last updated time
+     * Ask user: "Which application would you like to add features to?"
+     * Use the selected application's `latest_session_id`
+
+4. If no session_id found, ask the user for it
+
+5. Get the timeline_id from the session entry in index.json
+
+6. Call the `update-state` tool (from raindrop-mcp server) with the session_id, timeline_id, and these parameters:
+   ```json
+   {
+     "artifacts": {
+       "current_state": "merge_features"
+     },
+     "status": "complete"
+   }
+   ```
+   This jumps the workflow to the merge_features state for adding features.
+
+7. Call the `get-prompt` tool (from raindrop-mcp server) with the session_id parameter
+
+8. Follow the instructions returned and continue with the feature addition workflow
+"""