@nebulit/embuilder 0.1.39

package/templates/frontend/tsconfig.app.json

@@ -0,0 +1,31 @@
+{
+  "compilerOptions": {
+    "types": ["vitest/globals"],
+    "target": "ES2020",
+    "useDefineForClassFields": true,
+    "lib": ["ES2020", "DOM", "DOM.Iterable"],
+    "module": "ESNext",
+    "skipLibCheck": true,
+
+    /* Bundler mode */
+    "moduleResolution": "bundler",
+    "allowImportingTsExtensions": true,
+    "isolatedModules": true,
+    "moduleDetection": "force",
+    "noEmit": true,
+    "jsx": "react-jsx",
+
+    /* Linting */
+    "strict": false,
+    "noUnusedLocals": false,
+    "noUnusedParameters": false,
+    "noImplicitAny": false,
+    "noFallthroughCasesInSwitch": false,
+
+    "baseUrl": ".",
+    "paths": {
+      "@/*": ["./src/*"]
+    }
+  },
+  "include": ["src"]
+}

package/templates/frontend/tsconfig.json

@@ -0,0 +1,16 @@
+{
+  "files": [],
+  "references": [{ "path": "./tsconfig.app.json" }, { "path": "./tsconfig.node.json" }],
+  "compilerOptions": {
+    "baseUrl": ".",
+    "paths": {
+      "@/*": ["./src/*"]
+    },
+    "noImplicitAny": false,
+    "noUnusedParameters": false,
+    "skipLibCheck": true,
+    "allowJs": true,
+    "noUnusedLocals": false,
+    "strictNullChecks": false
+  }
+}

package/templates/frontend/tsconfig.node.json

@@ -0,0 +1,22 @@
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "lib": ["ES2023"],
+    "module": "ESNext",
+    "skipLibCheck": true,
+
+    /* Bundler mode */
+    "moduleResolution": "bundler",
+    "allowImportingTsExtensions": true,
+    "isolatedModules": true,
+    "moduleDetection": "force",
+    "noEmit": true,
+
+    /* Linting */
+    "strict": true,
+    "noUnusedLocals": false,
+    "noUnusedParameters": false,
+    "noFallthroughCasesInSwitch": true
+  },
+  "include": ["vite.config.ts"]
+}

package/templates/frontend/vite.config.ts

@@ -0,0 +1,21 @@
+import { defineConfig } from "vite";
+import react from "@vitejs/plugin-react-swc";
+import path from "path";
+import { componentTagger } from "lovable-tagger";
+
+// https://vitejs.dev/config/
+export default defineConfig(({ mode }) => ({
+  server: {
+    host: "::",
+    port: 8080,
+    hmr: {
+      overlay: false,
+    },
+  },
+  plugins: [react(), mode === "development" && componentTagger()].filter(Boolean),
+  resolve: {
+    alias: {
+      "@": path.resolve(__dirname, "./src"),
+    },
+  },
+}));

package/templates/frontend/vitest.config.ts

@@ -0,0 +1,16 @@
+import { defineConfig } from "vitest/config";
+import react from "@vitejs/plugin-react-swc";
+import path from "path";
+
+export default defineConfig({
+  plugins: [react()],
+  test: {
+    environment: "jsdom",
+    globals: true,
+    setupFiles: ["./src/test/setup.ts"],
+    include: ["src/**/*.{test,spec}.{ts,tsx}"],
+  },
+  resolve: {
+    alias: { "@": path.resolve(__dirname, "./src") },
+  },
+});

package/templates/init.sh

@@ -0,0 +1 @@
+docker run -v $PWD:/workspace nebulit/generators

package/templates/prompt.md

@@ -0,0 +1,139 @@
+# Ralph Agent Instructions
+
+You are an autonomous coding agent working on a software project. You apply your skills to build software slices. You only work on one slice at a time.
+
+The structure defined in the Project-Skills is relevant.
+
+## Your Task
+
+0. Do not read the entire code base. Focus on the tasks in this description.
+1. Read the description at `.slices/index.json` (in the same directory as this file). Every item in status "planned" is a task.
+2. Read the progress log at `progress.txt` (check Codebase Patterns section first)
+3. Make sure you are on the right branch "feature/<slicename>", if unsure, start from main.
+5. Pick the **highest priority** slice where status is "planned" ( case insensitive ). This becomes your PRD. Set the status "InProgress" in the index.json. If no slice has status planned, reply with:
+   <promise>NO_TASKS</promise> and stop. Do not work on other slices.
+6. Pick the slice definition from the project root /.slices in <folder> defined in the prd. Never work on more than one slice per iteration.
+7. A slice can define additional prompts as codegen/backendPrompt. any additional prompts defined in backend are hints for the implementation of the slice and have to be taken into account. If you use the additional prompt, add a line in progress.txt
+7. Define the slice type and load the matching skill. If the processors-array is not empty, it´s an automation slice.
+8. Write a short progress one liner after each step to progress.txt
+9. Analyze and Implement that single slice, make use of the skills in the skills directory, but also your previsously collected
+   knowledge. Make a list TODO list for what needs to be done. Also make sure to adjust the implementation according to the json definition. Carefully inspect events, fields and compare against the implemented slice. JSON is the desired state. ATTENTION: A "planned" task can also be just added specifications. So always look at the slice itself, but also the specifications. If specifications were added in json, which are not on code, you need to add them in code.
+10. The slice in the json is always true, the code follows what is defined in the json
+11. slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in  JSON are implemented in code and it
+    fulfills the slice.json. There must be no specification in json, that has no equivalent in code.
+12. make sure to write the ui-prompt.md as defined if defined in the skill
+13. Run quality checks ( npm run build, npm run test ) - Attention - it´s enough to run the tests for the slice. Do not run all tests.
+14. even if the slice is fully implemented, run your test-analyzer skill and provide the code-slice.json file as defined in the skill
+15. Update the Slice in the index.json to either `status: Done` for the completed, 'status: Planned' if rework is necessary.
+16. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge ( update
+    first )
+17. Append your progress to `progress.txt` after each step in the iteration.
+18. append your new learnings to AGENTS.md in a compressed form, reusable for future iterations. Only add learnings if they are not already there.
+19. Finish the iteration.
+
+## Progress Report Format
+
+APPEND to progress.txt (never replace, always append):
+
+```
+## [Date/Time] - [Slice]
+
+- What was implemented
+- Files changed
+- **Learnings for future iterations:**
+  - Patterns discovered (e.g., "this codebase uses X for Y")
+  - Gotchas encountered (e.g., "don't forget to update Z when changing W")
+  - Useful context (e.g., "the evaluation panel is in component X")
+---
+```
+
+The learnings section is critical - it helps future iterations avoid repeating mistakes and understand the codebase
+better.
+
+## Consolidate Patterns
+
+If you discover a **reusable pattern** that future iterations should know, add it to the `## Codebase Patterns` section
+at the TOP of progress.txt (create it if it doesn't exist). This section should consolidate the most important
+learnings:
+
+```
+## Codebase Patterns
+- Example: Use `sql<number>` template for aggregations
+- Example: Always use `IF NOT EXISTS` for migrations
+- Example: Export types from actions.ts for UI components
+```
+
+Only add patterns that are **general and reusable**, not story-specific details.
+
+## Update AGENTS.md Files
+
+Before committing, check if any edited files have learnings worth preserving in nearby AGENTS.md files:
+
+1. **Identify directories with edited files** - Look at which directories you modified
+3. **Add valuable learnings that apply to all tasks** to the Agents.md - If you discovered something future developers/agents should know:
+    - API patterns or conventions specific to that module
+    - Gotchas or non-obvious requirements
+    - Dependencies between files
+    - Testing approaches for that area
+    - Configuration or environment requirements
+
+**Examples of good AGENTS.md additions:**
+
+- "When modifying X, also update Y to keep them in sync"
+- "This module uses pattern Z for all API calls"
+- "Tests require the dev server running on PORT 3000"
+- "Field names must match the template exactly"
+
+**Do NOT add:**
+
+- Slice specific implementation details
+- Story-specific implementation details
+- Temporary debugging notes
+- Information already in progress.txt
+- Task speecific learnings like "- Timesheet approval requires: submitted=true, reverted=false, approved=false, declined=false"
+
+Only update AGENTS.md if you have **genuinely reusable knowledge** that would help future work
+
+## Quality Requirements
+
+- ALL commits must pass your project's quality checks (typecheck, lint, test)
+- run 'npm run build'
+- run 'npm run test'
+- Do NOT commit broken code
+- Keep changes focused and minimal
+- Follow existing code patterns
+
+## Skills
+
+Use the provided skills in the skills folder as guidance.
+Update skill definitions if you find an improvement you can make.
+
+## Specifications
+
+For every specification added to the Slice, you need to implement one use executable Specification in Code.
+
+A Slice is not complete if specifications are missing or can´t be executed.
+
+## Stop Condition
+
+After completing a user story, check if ALL slices have `status: Done`.
+
+If ALL stories are complete and passing, reply with:
+<promise>COMPLETE</promise>
+
+If there are no stories with `status: Planned` (but not all are Done), reply with:
+<promise>NO_TASKS</promise>
+
+If there are still stories with `status: Planned`, end your response normally (another iteration will pick up the next
+story).
+
+## Important
+
+- Work on ONE slice per iteration
+- Commit frequently
+- update progress.txt frequently
+- Read the Codebase Patterns section in progress.txt before starting
+
+## When an iteration completes
+
+Use all the key learnings from the project.txt and update the Agends.md file with those learning.

package/templates/ralph.sh

@@ -0,0 +1,120 @@
+#!/bin/bash
+# Ralph - Long-running AI agent loop for event-model driven development
+# Usage: ./ralph.sh [max_iterations]
+
+set -euo pipefail
+
+MAX_ITERATIONS=${1:-10}
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+PROGRESS_FILE="$SCRIPT_DIR/progress.txt"
+ARCHIVE_DIR="$SCRIPT_DIR/archive"
+
+mkdir -p "$ARCHIVE_DIR"
+
+# ------------------------------------------------------------
+# Init progress file
+# ------------------------------------------------------------
+if [[ ! -f "$PROGRESS_FILE" ]]; then
+  echo "# Event Model Development Progress Log" > "$PROGRESS_FILE"
+  echo "Started: $(date)" >> "$PROGRESS_FILE"
+  echo "---" >> "$PROGRESS_FILE"
+fi
+
+echo "Starting Ralph – Max iterations: $MAX_ITERATIONS"
+
+# ------------------------------------------------------------
+# Main Ralph loop
+# ------------------------------------------------------------
+for i in $(seq 1 "$MAX_ITERATIONS"); do
+  echo
+  echo "═══════════════════════════════════════════════════════"
+  echo "  Ralph Iteration $i of $MAX_ITERATIONS"
+  echo "═══════════════════════════════════════════════════════"
+
+  echo
+  echo ">>> Running Claude at $(date)"
+  echo ">>> Iteration $i" >> "$PROGRESS_FILE"
+
+  TMP_OUTPUT=$(mktemp)
+
+  # ---- Run Claude safely -----------------
+  CLAUDE_SKIP=false
+  while true; do
+    cat "$SCRIPT_DIR/prompt.md" \
+       | claude --dangerously-skip-permissions 2>&1 \
+       | tee "$TMP_OUTPUT" | tee -a "$PROGRESS_FILE"
+    CLAUDE_EXIT=${PIPESTATUS[1]}  # exit code of 'claude', not 'tee'
+
+    if [[ $CLAUDE_EXIT -eq 0 ]]; then
+      # Success, break out of the retry loop
+      break
+    elif grep -q "No messages returned" "$TMP_OUTPUT" 2>/dev/null; then
+      # Transient error: no messages returned - skip iteration
+      echo
+      echo "⚠️ Claude returned no messages (transient). Skipping iteration..."
+      CLAUDE_SKIP=true
+      break
+    else
+      # Non-zero exit code: probably spending limit reached
+      echo
+      echo "⚠️ Claude exited with an error. Possibly spending limit reached."
+      echo "Waiting 5 minutes before retry..."
+      sleep 300  # 5 minutes
+    fi
+  done
+  if [[ "$CLAUDE_SKIP" == "true" ]]; then
+    continue
+  fi
+
+  OUTPUT=$(cat "$TMP_OUTPUT")
+  rm "$TMP_OUTPUT"
+
+  if [[ -z "$OUTPUT" ]]; then
+    echo "⚠️ Claude returned no output. Retrying in 1 minute..."
+    sleep 60
+    continue  # retry
+  fi
+
+  # ---- Check for commit review failure -------------------
+  if echo "$OUTPUT" | grep -q "❌ COMMIT REVIEW FAILED"; then
+    echo
+    echo "⚠️  Commit review failed - workspace has been reset"
+    echo "📄 Review failure details recorded in progress.txt"
+    echo "🔄 Continuing to next iteration..."
+    echo
+    echo "Review failed at iteration $i - continuing loop" >> "$PROGRESS_FILE"
+    echo "Continuing: $(date)" >> "$PROGRESS_FILE"
+    echo "---" >> "$PROGRESS_FILE"
+    sleep 5  # Brief pause before continuing
+    continue  # Continue to next iteration
+  fi
+
+  # ---- Completion check -----------------------------------
+  if echo "$OUTPUT" | grep -q "<promise>COMPLETE</promise>"; then
+    echo
+    echo "🎉 Ralph completed all tasks!"
+    echo "Completed at iteration $i of $MAX_ITERATIONS"
+
+    echo
+    echo "Completed: $(date)" >> "$PROGRESS_FILE"
+    exit 0
+  fi
+
+  # ---- No tasks available check ---------------------------
+  if echo "$OUTPUT" | grep -q "<promise>NO_TASKS</promise>"; then
+    echo
+    echo "⏳ No tasks available. Waiting 30 seconds before next check..."
+    sleep 30
+    continue
+  fi
+
+  echo
+  echo "Iteration $i complete. Continuing..."
+  sleep 2
+done
+
+echo
+echo "⚠️ Ralph reached max iterations ($MAX_ITERATIONS) without completing all tasks."
+echo "Check $PROGRESS_FILE for status."
+exit 1