@ck123pm/harness-kit 0.1.2 → 0.1.3
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.
package/package.json
CHANGED
|
@@ -83,6 +83,14 @@ Before writing files, inspect the repository in at least three passes:
|
|
|
83
83
|
|
|
84
84
|
Prefer CodeGraph when it is available. Use local search only when you need literal text or filesystem details.
|
|
85
85
|
|
|
86
|
+
## Language
|
|
87
|
+
|
|
88
|
+
Before generating any content, determine the output language:
|
|
89
|
+
|
|
90
|
+
1. Read the project's `CLAUDE.md` (or `.claude/CLAUDE.md`) if it exists. If it declares a language preference (e.g. `language: zh-CN`, "使用中文", "write in English"), follow that.
|
|
91
|
+
2. If no language preference is found, match the language of the current conversation.
|
|
92
|
+
3. All generated files in `.harness/` must use the same language consistently.
|
|
93
|
+
|
|
86
94
|
## Execution
|
|
87
95
|
|
|
88
96
|
1. Explore the repository thoroughly and base all outputs on the current branch state.
|
|
@@ -83,6 +83,14 @@ Reuse the same content-routing rules as `harness-init`:
|
|
|
83
83
|
- Decisions and tradeoffs go to `decisions/`.
|
|
84
84
|
- Historical pitfalls, regressions, and patterns go to `memory/`.
|
|
85
85
|
|
|
86
|
+
## Language
|
|
87
|
+
|
|
88
|
+
Before generating or updating any content, determine the output language using the same rules as `harness-init`:
|
|
89
|
+
|
|
90
|
+
1. Read the project's `CLAUDE.md` (or `.claude/CLAUDE.md`) if it exists. If it declares a language preference, follow that.
|
|
91
|
+
2. If no preference is found, match the language of the current conversation.
|
|
92
|
+
3. All generated files in `.harness/` must use the same language consistently and match the language of existing `.harness/` files.
|
|
93
|
+
|
|
86
94
|
## Human Docs
|
|
87
95
|
|
|
88
96
|
If you add or refresh `human-docs/` content, write Markdown first and then use `md-to-html-doc` to produce the HTML artifacts expected by the harness.
|