moflo 4.0.0 → 4.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,116 @@
|
|
|
1
|
+
# MoFlo Agent Bootstrap Guide
|
|
2
|
+
|
|
3
|
+
**Purpose:** Quick-start reference for subagents spawned by coordinators. Every subagent should follow this protocol before doing any work.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## 1. Search Memory FIRST
|
|
8
|
+
|
|
9
|
+
**Before reading any files or exploring code, search memory for guidance relevant to your task.**
|
|
10
|
+
|
|
11
|
+
### Two namespaces to search:
|
|
12
|
+
|
|
13
|
+
| Namespace | When to search | What it returns |
|
|
14
|
+
|-----------|---------------|-----------------|
|
|
15
|
+
| `guidance` | Understanding patterns, rules, conventions | Guidance docs, coding rules, domain context |
|
|
16
|
+
| `code-map` | Finding where code lives (files, types, services) | Project overviews, directory contents, type locations |
|
|
17
|
+
|
|
18
|
+
**Search `code-map` BEFORE using Glob/Grep for navigation.** It's faster and returns structured results.
|
|
19
|
+
|
|
20
|
+
### Option A: MCP Tools (Preferred)
|
|
21
|
+
|
|
22
|
+
If you have MCP tools available (check for `mcp__claude-flow__*`), use them directly:
|
|
23
|
+
|
|
24
|
+
| Tool | Purpose |
|
|
25
|
+
|------|---------|
|
|
26
|
+
| `mcp__claude-flow__memory_search` | Semantic search with domain-aware embeddings |
|
|
27
|
+
| `mcp__claude-flow__memory_store` | Store patterns with auto-vectorization |
|
|
28
|
+
| `mcp__claude-flow__hooks_route` | Get agent routing suggestions |
|
|
29
|
+
|
|
30
|
+
### Option B: CLI via Bash
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
npx moflo memory search --query "[describe your task]" --namespace guidance --limit 5
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
| Your task involves... | Search namespace | Example query |
|
|
37
|
+
|-----------------------|------------------|---------------|
|
|
38
|
+
| Database/entities | `guidance` | `"database entity migration"` |
|
|
39
|
+
| Frontend components | `guidance` | `"React frontend component"` |
|
|
40
|
+
| API endpoints | `guidance` | `"API route endpoint pattern"` |
|
|
41
|
+
| Authentication | `guidance` | `"auth middleware JWT"` |
|
|
42
|
+
| Unit tests | `guidance` | `"test mock vitest"` |
|
|
43
|
+
| Where is a file/type? | `code-map` | `"service entity location"` |
|
|
44
|
+
| What's in a directory? | `code-map` | `"back-office api routes"` |
|
|
45
|
+
|
|
46
|
+
Use results with score > 0.3. If no good results, fall back to reading project guidance docs.
|
|
47
|
+
|
|
48
|
+
---
|
|
49
|
+
|
|
50
|
+
## 2. Check Project Guidance
|
|
51
|
+
|
|
52
|
+
If memory search doesn't return useful results, look for project-level guidance:
|
|
53
|
+
|
|
54
|
+
```bash
|
|
55
|
+
# Check if project has guidance docs
|
|
56
|
+
ls .claude/guidance/ 2>/dev/null
|
|
57
|
+
|
|
58
|
+
# Check if project has a core index
|
|
59
|
+
cat .claude/guidance/core.md 2>/dev/null | head -50
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
Project guidance takes precedence over generic patterns.
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## 3. Universal Rules
|
|
67
|
+
|
|
68
|
+
### Memory Protocol
|
|
69
|
+
- Search memory before exploring files
|
|
70
|
+
- Store discoveries back to memory when done
|
|
71
|
+
- Use `patterns` namespace for solutions and gotchas
|
|
72
|
+
- Use `decisions` namespace for architectural choices
|
|
73
|
+
|
|
74
|
+
### Git/Branches
|
|
75
|
+
- Use conventional commit prefixes: `feat:`, `fix:`, `refactor:`, `test:`, `chore:`
|
|
76
|
+
- Use branch prefixes: `feature/`, `fix/`, `refactor/`
|
|
77
|
+
- Use kebab-case for branch names
|
|
78
|
+
|
|
79
|
+
### File Organization
|
|
80
|
+
- Never save working files to repository root
|
|
81
|
+
- Keep changes focused (3-10 files)
|
|
82
|
+
- Stay within feature scope
|
|
83
|
+
|
|
84
|
+
### Build & Test
|
|
85
|
+
- Build and test after code changes
|
|
86
|
+
- Never leave failing tests
|
|
87
|
+
|
|
88
|
+
---
|
|
89
|
+
|
|
90
|
+
## 4. Store Discoveries
|
|
91
|
+
|
|
92
|
+
If you discover something new (pattern, solution, gotcha), store it:
|
|
93
|
+
|
|
94
|
+
### MCP (Preferred):
|
|
95
|
+
```
|
|
96
|
+
mcp__claude-flow__memory_store
|
|
97
|
+
namespace: "patterns"
|
|
98
|
+
key: "brief-descriptive-key"
|
|
99
|
+
value: "1-2 sentence insight"
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
### CLI Fallback:
|
|
103
|
+
```bash
|
|
104
|
+
npx moflo memory store --namespace patterns --key "brief-descriptive-key" --value "1-2 sentence insight"
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
**Store:** Solutions to tricky bugs, patterns that worked, gotchas, workarounds
|
|
108
|
+
**Skip:** Summaries of retrieved guidance, general rules, file locations
|
|
109
|
+
|
|
110
|
+
---
|
|
111
|
+
|
|
112
|
+
## 5. When Complete
|
|
113
|
+
|
|
114
|
+
1. Report findings to coordinator
|
|
115
|
+
2. Store learnings if you discovered something new
|
|
116
|
+
3. Coordinator will mark your task as completed
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "moflo",
|
|
3
|
-
"version": "4.0.
|
|
3
|
+
"version": "4.0.1",
|
|
4
4
|
"description": "MoFlo — AI agent orchestration for Claude Code. Forked from ruflo/claude-flow with patches applied to source, plus feature-level orchestration.",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"type": "module",
|