dreamer 0.0.0-sandbox-20251210004407 → 0.0.0-sandbox-20260105024945

package/dist/template/.claude/may_edit.py

@@ -0,0 +1,59 @@
+#!/usr/bin/env python3
+"""
+File path validator for hook system.
+Ensures file operations only occur within src/ directories or PRD.md
+"""
+
+import json
+import sys
+
+
+def validate_file_path():
+    """
+    Validates that file operations are restricted to src/ directories.
+
+    Reads JSON from stdin, extracts file_path from tool_input,
+    and blocks operations outside of src/ directories.
+
+    Exit codes:
+        0: Path is allowed
+        2: Path is blocked
+    """
+    try:
+        # Read JSON input from stdin
+        data = json.load(sys.stdin)
+
+        # Extract file path from tool_input
+        file_path = data.get("tool_input", {}).get("file_path", "")
+
+        # Check if path is allowed (starts with 'src/' or contains '/src/', or is DATA-PLAN.md in planning/)
+        is_blocked = not (
+            file_path.startswith("src/")
+            or "/src/" in file_path
+            or file_path.endswith("PRD.md")
+            or file_path == "planning/DATA-PLAN.md"
+            or file_path.endswith("/DATA-PLAN.md")
+            or file_path.endswith("agent.yaml")
+        )
+
+        if is_blocked:
+            error_msg = (
+                f'File operation blocked: Path "{file_path}" is not allowed. '
+                f"Only files in src directories, agent.yaml, PRD.md, or planning/DATA-PLAN.md are allowed for editing."
+            )
+            print(error_msg, file=sys.stderr)
+            sys.exit(2)
+
+        # Path is allowed
+        sys.exit(0)
+
+    except json.JSONDecodeError as e:
+        print(f"Error parsing JSON input: {e}", file=sys.stderr)
+        sys.exit(1)
+    except Exception as e:
+        print(f"Unexpected error: {e}", file=sys.stderr)
+        sys.exit(1)
+
+
+if __name__ == "__main__":
+    validate_file_path()

package/dist/template/.claude/settings.json

@@ -0,0 +1,25 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bun install"
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Edit|MultiEdit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 .claude/may_edit.py"
+          }
+        ]
+      }
+    ]
+  }
+}

package/dist/template/.vscode/tasks.json

@@ -0,0 +1,19 @@
+{
+  "version": "2.0.0",
+  "tasks": [
+    {
+      "label": "Agent-code: Build and Push",
+      "type": "shell",
+      "command": "agent-code",
+      "args": ["push"],
+      "group": "build",
+      "presentation": {
+        "echo": true,
+        "reveal": "always",
+        "focus": false,
+        "panel": "shared"
+      },
+      "problemMatcher": []
+    }
+  ]
+}

package/dist/template/CLAUDE-DATA-PLANNING.md

@@ -0,0 +1,106 @@
+# Data Planning Phase
+Before implementing any agent that requires external data, you MUST complete a data planning phase. This is not optional - it ensures reliable data access and prevents common pitfalls.
+
+## Data Planning Requirements
+1. **Enumerate all external data dependencies** from the product requirements
+2. **Test each data-fetching tool** using `agent-code call-tool` (never test mutation tools)
+3. **Document the data plan** in `planning/DATA-PLAN.md`
+
+## Approved Data Sources
+**ALLOWED:**
+- Tools defined in `sdk-helpers/tools.ts` (weather services, email, calendar, web readers, search tools etc.)
+- Data persisted in KV store from previous tool calls
+
+**FORBIDDEN:**
+- Direct REST API calls using `fetch` (even if you found the API via search)
+- Hardcoded/mocked data (unless explicitly requested by user)
+- APIs requiring API keys not provided through tools
+- Any data source not accessible through tools.ts
+
+## Exception handling
+Sometimes, the user will ask you to make use of data you simply do not have access to. Never try to generate fake, example or synthetic data. If you cannot find a good strategy to apply real data to the problem you MUST stop the whole task you've been assigned and tell the user that it is not possible to find real data to complete the task. The user will be able to select additional tools to help you out.
+
+## Data Planning Process
+0. **Consult Existing Plan (if any)**: If there is already a plan under `planning/DATA-PLAN.md`
+keep it in mind for the next steps. It may already fulfill the data requirements.
+1. **Identify Requirements**: List every piece of external data needed
+2. **Tool Discovery**: Review `sdk-helpers/tools.ts` for relevant tools
+3. **Tool Testing**: Use `agent-code call-tool` to test ONLY data-fetching tools (never test mutation tools like send_email, create_task, etc.)
+4. **Output Analysis**: Examine actual outputs to understand data structure
+5. **Strategy**: Determine how you will use the the different tools in sequence to acheive the desired end result.
+6. **Processing Strategy**: Determine if you need:
+   - Direct property access
+   - Data transformation
+   - LLM inference (via `sdk.callLLM`) for extraction/classification
+7. **Documentation**: Create DATA-PLAN.md under `planning/DATA-PLAN.md`
+*** DON'T FORGET that if you cannot make a plan with real data you MUST stop and ask the user for further guidance. ***
+
+## DATA-PLAN.md Structure
+Create this file before implementing server functions under `planning/DATA-PLAN.md`:
+
+```md
+# Data Plan for [Agent Name]
+
+## External Data Requirements
+1. [Requirement 1 description]
+2. [Requirement 2 description]
+...
+
+## Data Sources
+
+### [Data Requirement 1]
+**Tool**: [tool_name from tools.ts]
+**Test Command**: `agent-code call-tool [tool_name] '[params]'`
+**Sample Arguments**:
+[Actual examples of successful arguments from testing]
+**Sample Output**:
+[Actual output from testing]
+
+**Processing Strategy**:
+- [How to extract needed data]
+- [Any LLM processing required]
+
+[Repeat for other tools needed for this Ddata Requrement...]
+
+### [Data Requirement 2]
+[Same structure...]
+
+## Rejected Approaches
+### [Approach that didn't work]
+**Why Tested**: [Reasoning]
+**Why Rejected**: [Specific failure reason]
+```
+
+## Common Data Planning Mistakes to Avoid
+
+### ❌ DON'T: Use fetch() with discovered APIs
+```typescript
+// WRONG - Even if you found this API through web search
+const weather = await fetch('https://api.weather.com/v1/...');
+```
+
+### ✅ DO: Use tools from tools.ts
+```typescript
+// CORRECT - Use the weather tool
+import { weather_api_service_getcurrentweather } from "@sdk-helpers/tools";
+const weather = await weather_api_service_getcurrentweather(sdk, { location: city }, schema);
+```
+
+### ❌ DON'T: Hardcode fallback data
+```typescript
+// WRONG - Using mock data as fallback
+const weather = toolResult || { temp: 72, condition: "sunny" };
+```
+
+### ✅ DO: Handle missing data gracefully
+```typescript
+// CORRECT - Show loading or error states
+if (!weather) return { error: "Weather data unavailable" };
+```
+
+### ❌ DON'T: Make up mock or sample data if you can't find real data.
+```
+// WRONG - Instead, stop, tell the user the problem and ask for their guidance.
+Since the PRD requires implementing a specific API that doesn't seem to exist, I'll create a
+mock implementation that simulates what such a service would provide
+```