moflo 4.8.11 → 4.8.13

package/.claude/agents/browser/browser-agent.yaml

@@ -0,0 +1,182 @@
+# Browser Agent Configuration
+# AI-powered web browser automation using agent-browser
+#
+# Capabilities:
+# - Web navigation and interaction
+# - AI-optimized snapshots with element refs
+# - Form filling and submission
+# - Screenshot capture
+# - Network interception
+# - Multi-session coordination
+
+name: browser-agent
+description: Web automation specialist using agent-browser with AI-optimized snapshots
+version: 1.0.0
+
+# Routing configuration
+routing:
+  complexity: medium
+  model: sonnet  # Good at visual reasoning and DOM interpretation
+  priority: normal
+  keywords:
+    - browser
+    - web
+    - scrape
+    - screenshot
+    - navigate
+    - login
+    - form
+    - click
+    - automate
+
+# Agent capabilities
+capabilities:
+  - web-navigation
+  - form-interaction
+  - screenshot-capture
+  - data-extraction
+  - network-interception
+  - session-management
+  - multi-tab-coordination
+
+# Available tools (MCP tools with browser/ prefix)
+tools:
+  navigation:
+    - browser/open
+    - browser/back
+    - browser/forward
+    - browser/reload
+    - browser/close
+  snapshot:
+    - browser/snapshot
+    - browser/screenshot
+    - browser/pdf
+  interaction:
+    - browser/click
+    - browser/fill
+    - browser/type
+    - browser/press
+    - browser/hover
+    - browser/select
+    - browser/check
+    - browser/uncheck
+    - browser/scroll
+    - browser/upload
+  info:
+    - browser/get-text
+    - browser/get-html
+    - browser/get-value
+    - browser/get-attr
+    - browser/get-title
+    - browser/get-url
+    - browser/get-count
+  state:
+    - browser/is-visible
+    - browser/is-enabled
+    - browser/is-checked
+  wait:
+    - browser/wait
+  eval:
+    - browser/eval
+  storage:
+    - browser/cookies-get
+    - browser/cookies-set
+    - browser/cookies-clear
+    - browser/localstorage-get
+    - browser/localstorage-set
+  network:
+    - browser/network-route
+    - browser/network-unroute
+    - browser/network-requests
+  tabs:
+    - browser/tab-list
+    - browser/tab-new
+    - browser/tab-switch
+    - browser/tab-close
+    - browser/session-list
+  settings:
+    - browser/set-viewport
+    - browser/set-device
+    - browser/set-geolocation
+    - browser/set-offline
+    - browser/set-media
+  debug:
+    - browser/trace-start
+    - browser/trace-stop
+    - browser/console
+    - browser/errors
+    - browser/highlight
+    - browser/state-save
+    - browser/state-load
+  find:
+    - browser/find-role
+    - browser/find-text
+    - browser/find-label
+    - browser/find-testid
+
+# Memory configuration
+memory:
+  namespace: browser-sessions
+  persist: true
+  patterns:
+    - login-flows
+    - form-submissions
+    - scraping-patterns
+    - navigation-sequences
+
+# Swarm integration
+swarm:
+  roles:
+    - navigator      # Handles authentication and navigation
+    - scraper        # Extracts data using snapshots
+    - validator      # Verifies extracted data
+    - tester         # Runs automated tests
+    - monitor        # Watches for errors and network issues
+  topology: hierarchical  # Coordinator manages browser agents
+  max_sessions: 5
+
+# Hooks integration
+hooks:
+  pre_task:
+    - route         # Get optimal routing
+    - memory_search # Check for similar patterns
+  post_task:
+    - memory_store  # Save successful patterns
+    - post_edit     # Train on outcomes
+
+# Default configuration
+defaults:
+  timeout: 30000
+  headless: true
+  viewport:
+    width: 1280
+    height: 720
+
+# Example workflows
+workflows:
+  login:
+    description: Authenticate to a website
+    steps:
+      - open: "{url}/login"
+      - snapshot: { interactive: true }
+      - fill: { target: "@e1", value: "{username}" }
+      - fill: { target: "@e2", value: "{password}" }
+      - click: "@e3"
+      - wait: { url: "**/dashboard" }
+      - state-save: "auth-state.json"
+
+  scrape_list:
+    description: Extract data from a list page
+    steps:
+      - open: "{url}"
+      - snapshot: { interactive: true, compact: true }
+      - eval: "Array.from(document.querySelectorAll('{selector}')).map(el => el.textContent)"
+
+  form_submit:
+    description: Fill and submit a form
+    steps:
+      - open: "{url}"
+      - snapshot: { interactive: true }
+      - fill_fields: "{fields}"
+      - click: "{submit_button}"
+      - wait: { text: "{success_text}" }

package/.claude/guidance/moflo-bootstrap.md

@@ -0,0 +1,129 @@
+<!-- AUTO-GENERATED by moflo session-start. Do not edit — changes will be overwritten. -->
+<!-- Source: node_modules/moflo/.claude/guidance/agent-bootstrap.md -->
+
+# MoFlo Agent Bootstrap Guide
+
+**Purpose:** Quick-start reference for subagents spawned by coordinators. Every subagent should follow this protocol before doing any work.
+
+---
+
+## 1. Search Memory FIRST
+
+**Before reading any files or exploring code, search memory for guidance relevant to your task.**
+
+### Three namespaces to search:
+
+| Namespace | When to search | What it returns |
+|-----------|---------------|-----------------|
+| `guidance` | Understanding patterns, rules, conventions | Guidance docs, coding rules, domain context |
+| `code-map` | Finding where code lives (files, types, services) | Project overviews, directory contents, type-to-file mappings |
+| `patterns` | Prior solutions, gotchas, implementation patterns | Learned patterns from previous task execution |
+
+**Always search `patterns` alongside `guidance`.** It contains solutions to problems already solved — skipping it means repeating past mistakes or re-discovering known approaches.
+
+**Search `code-map` BEFORE using Glob/Grep for navigation.** It's faster and returns structured results including file-level type mappings.
+
+### Option A: MCP Tools (Preferred)
+
+If you have MCP tools available (check for `mcp__moflo__*`), use them directly:
+
+| Tool | Purpose |
+|------|---------|
+| `mcp__moflo__memory_search` | Semantic search with domain-aware embeddings |
+| `mcp__moflo__memory_store` | Store patterns with auto-vectorization |
+| `mcp__moflo__hooks_route` | Get agent routing suggestions |
+
+### Option B: CLI via Bash
+
+```bash
+npx flo memory search --query "[describe your task]" --namespace guidance --limit 5
+```
+
+| Your task involves... | Search namespace | Example query |
+|-----------------------|------------------|---------------|
+| Database/entities | `guidance` + `patterns` | `"database entity migration"` |
+| Frontend components | `guidance` + `patterns` | `"React frontend component"` |
+| API endpoints | `guidance` + `patterns` | `"API route endpoint pattern"` |
+| Authentication | `guidance` + `patterns` | `"auth middleware JWT"` |
+| Unit tests | `guidance` + `patterns` | `"test mock vitest"` |
+| Prior solutions/gotchas | `patterns` | `"audit log service pattern"` |
+| Where is a file/type? | `code-map` | `"CompanyEntity file location"` |
+| What's in a directory? | `code-map` | `"back-office api routes"` |
+
+Use results with score > 0.3. If no good results, fall back to reading project guidance docs.
+
+---
+
+## 2. Check Project-Specific Bootstrap
+
+**After reading this file, check for a project-specific bootstrap:**
+
+```bash
+# Project-specific bootstrap (has domain rules, patterns, templates)
+cat .claude/guidance/agent-bootstrap.md 2>/dev/null | head -10
+```
+
+If `.claude/guidance/agent-bootstrap.md` exists, **read it next**. It contains project-specific rules (entity patterns, multi-tenancy, tech stack conventions) that override generic guidance.
+
+If no project bootstrap exists, look for general project guidance:
+
+```bash
+ls .claude/guidance/ 2>/dev/null
+cat .claude/guidance/core.md 2>/dev/null | head -50
+```
+
+Project guidance always takes precedence over generic patterns.
+
+---
+
+## 3. Universal Rules
+
+### Memory Protocol
+- Search memory before exploring files
+- Store discoveries back to memory when done
+- Use `patterns` namespace for solutions and gotchas
+- Use `decisions` namespace for architectural choices
+
+### Git/Branches
+- Use conventional commit prefixes: `feat:`, `fix:`, `refactor:`, `test:`, `chore:`
+- Use branch prefixes: `feature/`, `fix/`, `refactor/`
+- Use kebab-case for branch names
+
+### File Organization
+- Never save working files to repository root
+- Keep changes focused (3-10 files)
+- Stay within feature scope
+
+### Build & Test
+- Build and test after code changes
+- Never leave failing tests
+
+---
+
+## 4. Store Discoveries
+
+If you discover something new (pattern, solution, gotcha), store it:
+
+### MCP (Preferred):
+```
+mcp__moflo__memory_store
+  namespace: "patterns"
+  key: "brief-descriptive-key"
+  value: "1-2 sentence insight"
+```
+
+### CLI Fallback:
+```bash
+npx flo memory store --namespace patterns --key "brief-descriptive-key" --value "1-2 sentence insight"
+```
+
+**Store:** Solutions to tricky bugs, patterns that worked, gotchas, workarounds
+**Skip:** Summaries of retrieved guidance, general rules, file locations
+
+---
+
+## 5. When Complete
+
+1. Report findings to coordinator
+2. Store learnings if you discovered something new
+3. Coordinator will mark your task as completed

package/.claude/helpers/post-commit

@@ -0,0 +1,16 @@
+#!/bin/bash
+# Claude Flow Post-Commit Hook
+# Records commit metrics and trains patterns
+
+COMMIT_HASH=$(git rev-parse HEAD)
+COMMIT_MSG=$(git log -1 --pretty=%B)
+
+echo "📊 Recording commit metrics..."
+
+# Notify claude-flow of commit
+npx moflo hooks notify \
+  --message "Commit: $COMMIT_MSG" \
+  --level info \
+  --metadata '{"hash": "'$COMMIT_HASH'"}' 2>/dev/null || true
+
+echo "✅ Commit recorded"

package/.claude/helpers/pre-commit

@@ -0,0 +1,26 @@
+#!/bin/bash
+# Claude Flow Pre-Commit Hook
+# Validates code quality before commit
+
+set -e
+
+echo "🔍 Running Claude Flow pre-commit checks..."
+
+# Get staged files
+STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM)
+
+# Run validation for each staged file
+for FILE in $STAGED_FILES; do
+  if [[ "$FILE" =~ \.(ts|js|tsx|jsx)$ ]]; then
+    echo "  Validating: $FILE"
+    npx moflo hooks pre-edit --file "$FILE" --validate-syntax 2>/dev/null || true
+  fi
+done
+
+# Run tests if available
+if [ -f "package.json" ] && grep -q '"test"' package.json; then
+  echo "🧪 Running tests..."
+  npm test --if-present 2>/dev/null || echo "  Tests skipped or failed"
+fi
+
+echo "✅ Pre-commit checks complete"