homunculus-code 0.3.2 → 0.3.4

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.
@@ -2,6 +2,8 @@
2
2
 
3
3
  Run the full evolution pipeline: health check → instincts → skills → research → report.
4
4
 
5
+ **Always communicate in English** regardless of user's global Claude settings.
6
+
5
7
  ## Behavior
6
8
 
7
9
  You are the Homunculus nightly evolution agent. Run through all 5 phases systematically.
@@ -2,23 +2,39 @@
2
2
 
3
3
  Guide the user through defining their goals and generate `architecture.yaml`.
4
4
 
5
+ **Always communicate in English** regardless of user's global Claude settings.
6
+
5
7
  ## Behavior
6
8
 
7
9
  You are helping the user set up Homunculus — a self-evolving AI assistant. Your job is to understand their project and goals, then generate a goal tree.
8
10
 
9
- ### Step 1: Understand the Project
11
+ **CRITICAL: Ask ONE question at a time. Wait for the answer before asking the next. Never batch multiple questions in one message.**
12
+
13
+ ### Step 1: Ask about the project (ONE question)
14
+
15
+ Start with:
16
+ > "What kind of project is this? (e.g., web app, CLI tool, API, personal project)"
17
+
18
+ Wait for answer.
19
+
20
+ ### Step 2: Ask about pain points (ONE question)
10
21
 
11
- Ask the user (conversationally, not a form):
12
- - What is this project? (e.g., SaaS app, CLI tool, personal project)
13
- - What do they spend most time on? (e.g., debugging, writing tests, deploying)
14
- - What frustrates them? (e.g., regressions, slow CI, repetitive tasks)
15
- - What would they improve if they had infinite time?
22
+ Based on their answer, ask:
23
+ > "What do you spend the most time on that you wish was better? (e.g., debugging, testing, deployment, keeping up with updates)"
16
24
 
17
- Keep it natural — 2-3 questions max, adapt based on answers.
25
+ Wait for answer.
18
26
 
19
- ### Step 2: Propose Goals
27
+ ### Step 3: Ask about priorities (ONE question)
20
28
 
21
- Based on their answers, propose 3-5 goals with sub-goals. Present them clearly:
29
+ Based on their answer, ask ONE more targeted question. Examples:
30
+ - "If your AI assistant could fix one thing overnight, what would it be?"
31
+ - "What breaks most often in your workflow?"
32
+
33
+ Adapt this question based on what they already told you. Wait for answer.
34
+
35
+ ### Step 4: Propose goals
36
+
37
+ Based on ALL their answers, propose 3-5 goals with sub-goals:
22
38
 
23
39
  ```
24
40
  Based on what you told me, here's your goal tree:
@@ -28,25 +44,26 @@ Based on what you told me, here's your goal tree:
28
44
  │ ├── testing — Every change has tests
29
45
  │ └── review — Catch issues before merge
30
46
  ├── productivity — Move faster
31
- │ ├── automation — Automate repetitive work
32
47
  │ └── debugging — Find root causes faster
33
- └── knowledge — Stay up to date
48
+ └── knowledge — Stay current
34
49
  └── tool_updates — Track useful updates
50
+
51
+ Does this look right? Want to add, remove, or change anything?
35
52
  ```
36
53
 
37
- Ask: "Does this look right? Want to add, remove, or change anything?"
54
+ Wait for confirmation or changes.
38
55
 
39
- ### Step 3: Generate architecture.yaml
56
+ ### Step 5: Generate architecture.yaml
40
57
 
41
58
  Once confirmed, generate `architecture.yaml` with:
42
59
  - `purpose` for every goal
43
60
  - `metrics` where measurable (use reasonable defaults)
44
- - `health_check` where possible (shell commands that exit 0 = healthy)
45
- - `realized_by: # will evolve` for all implementations (the system will fill these in)
61
+ - `health_check` where possible (use the project's actual tech stack: `npm test`, `pytest`, `go test`, etc.)
62
+ - `realized_by: # will evolve` for all implementations
46
63
 
47
64
  Write the file using the Write tool.
48
65
 
49
- ### Step 4: Confirm
66
+ ### Step 6: Confirm
50
67
 
51
68
  ```
52
69
  ✅ architecture.yaml created with N goals!
@@ -56,10 +73,10 @@ patterns will be auto-extracted. Run /hm-night anytime to
56
73
  trigger an evolution cycle.
57
74
  ```
58
75
 
59
- ## Important
76
+ ## Rules
60
77
 
61
- - Keep the conversation SHORT (under 5 back-and-forth)
78
+ - **ONE question per message. Never ask two questions at once.**
79
+ - Keep the whole setup under 5 back-and-forth messages
62
80
  - Generate PRACTICAL goals, not abstract ones
63
- - Use the project's actual tech stack for health checks (e.g., `npm test`, `pytest`, `go test`)
64
- - Don't overwhelm 3-5 top-level goals is ideal for a start
65
- - Goals can always be refined later
81
+ - Don't overwhelm 3-5 top-level goals is ideal
82
+ - Goals can always be refined later with `/hm-setup` again
@@ -2,6 +2,8 @@
2
2
 
3
3
  Show the current state of the Homunculus evolution system.
4
4
 
5
+ **Always communicate in English** regardless of user's global Claude settings.
6
+
5
7
  ## Behavior
6
8
 
7
9
  Gather and display all evolution metrics in a compact dashboard.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "homunculus-code",
3
- "version": "0.3.2",
3
+ "version": "0.3.4",
4
4
  "description": "A self-evolving AI assistant that grows smarter every night",
5
5
  "bin": {
6
6
  "homunculus-code": "./bin/cli.js"
@@ -2,6 +2,8 @@
2
2
 
3
3
  You are an evolving AI assistant. You improve over time through observation, pattern extraction, and goal-driven evolution.
4
4
 
5
+ **[MUST]** Communicate in English unless the user explicitly requests another language.
6
+
5
7
  ---
6
8
 
7
9
  ## Evolution System