@ck123pm/harness-kit 0.1.2 → 0.1.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.
Files changed (4) hide show
  1. package/.claude/scheduled_tasks.lock +1 -0
  2. package/package.json +1 -1
  3. package/skills/harness-init/SKILL.md +23 -27
  4. package/skills/harness-update-spec/SKILL.md +7 -9
package/.claude/scheduled_tasks.lock ADDED
@@ -0,0 +1 @@
1
+ {"sessionId":"3f555614-8398-44a9-8eaf-c6392cea7744","pid":24940,"acquiredAt":1779795641460}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ck123pm/harness-kit",
3
- "version": "0.1.2",
3
+ "version": "0.1.4",
4
4
  "description": "CLI for installing and managing Claude Code harness capabilities",
5
5
  "type": "module",
6
6
  "bin": {
package/skills/harness-init/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: harness-init
3
- description: Initialize a project's .harness/ directory by deriving high-value project knowledge from the real codebase, splitting content into the expected index/rules/domain/decisions/guides/memory/human-docs structure, and avoiding facts that can be re-derived from source.
3
+ description: Initialize a project's .harness/ directory by exploring the real codebase and generating structured project knowledge docs. Use when starting harness for a new project or rebuilding stale .harness/ content.
4
4
  ---
5
5
 
6
6
  # Harness Init
@@ -15,16 +15,16 @@ Use this skill when the user wants to initialize a project's `.harness/` directo
15
15
  4. Put human-oriented docs in `human-docs/` as Markdown first, convert them to HTML with `md-to-html-doc`, then remove the Markdown source if the workflow requires generated HTML only.
16
16
  5. Never fabricate content that is not supported by the actual repository state.
17
17
 
18
- ## Target Directory Structure
18
+ ## Directory Structure and Content Routing
19
19
 
20
- Create this structure under `.harness/`:
20
+ The `.harness/` directory uses a category-based layout. The reference files below are **starting points** — create only files with real content, add new files when needed, and skip empty placeholders.
21
21
 
22
22
  ```text
23
23
  .harness/
24
- ├── README.md
24
+ ├── README.md # always create: explain injection routing via index/routing.md and priority via index/priority.md
25
25
  ├── index/
26
- │ ├── routing.md
27
- │ ├── priority.md
26
+ │ ├── routing.md # always create
27
+ │ ├── priority.md # always create
28
28
  │ ├── module-map.md
29
29
  │ └── project-profile.md
30
30
  ├── rules/
@@ -48,30 +48,26 @@ Create this structure under `.harness/`:
48
48
  │ ├── patterns.md
49
49
  │ └── lessons.md
50
50
  └── human-docs/
51
- ├── onboarding.html
52
- ├── architecture-intro.html
53
- └── operation-manual.html
51
+ └── ... # onboarding.html, architecture-intro.html, operation-manual.html
54
52
  ```
55
53
 
56
- ## Content Routing
57
-
58
- | Information type | Destination |
54
+ | Information type | Reference file |
59
55
  | --- | --- |
60
- | Project identity, tech stack, module structure, key constants | `index/project-profile.md` |
56
+ | Project identity, tech stack, module structure | `index/project-profile.md` |
61
57
  | Task-to-context routing | `index/routing.md` |
62
58
  | Injection priority and intensity | `index/priority.md` |
63
59
  | Module-to-spec mapping | `index/module-map.md` |
64
- | Architecture constraints, module boundaries, ownership, high-risk chains | `rules/architecture.md` |
65
- | Coding standards, serialization, locking, conventions | `rules/coding.md` |
66
- | Test framework, file layout, strategy, fast commands | `rules/testing.md` |
60
+ | Architecture constraints, boundaries, ownership | `rules/architecture.md` |
61
+ | Coding standards, conventions | `rules/coding.md` |
62
+ | Test framework, strategy, commands | `rules/testing.md` |
67
63
  | Security constraints | `rules/security.md` |
68
64
  | Domain terminology | `domain/glossary.md` |
69
65
  | Stable business rules | `domain/business-rules.md` |
70
- | Runtime semantics, state transitions, magic values | `domain/runtime-semantics.md` |
71
- | External-system runtime semantics, message flow, integration behavior | `guides/backend.md` |
72
- | Build, startup, logs, config, monitoring, troubleshooting | `guides/ops.md` |
73
- | ADRs and tradeoffs | `decisions/` |
74
- | Historical pitfalls, regressions, reusable patterns, lessons | `memory/` |
66
+ | Runtime semantics, state transitions | `domain/runtime-semantics.md` |
67
+ | External integrations, message flow | `guides/backend.md` |
68
+ | Build, config, monitoring, troubleshooting | `guides/ops.md` |
69
+ | ADRs, design tradeoffs | `decisions/` |
70
+ | Pitfalls, regressions, patterns, lessons | `memory/` |
75
71
 
76
72
  ## Exploration Strategy
77
73
 
@@ -83,10 +79,10 @@ Before writing files, inspect the repository in at least three passes:
83
79
 
84
80
  Prefer CodeGraph when it is available. Use local search only when you need literal text or filesystem details.
85
81
 
86
- ## Execution
82
+ ## Language
83
+
84
+ Before generating any content, determine the output language:
87
85
 
88
- 1. Explore the repository thoroughly and base all outputs on the current branch state.
89
- 2. Create the full `.harness/` tree, even if some files are initially brief.
90
- 3. Keep generated content concise and high-signal.
91
- 4. If `human-docs/` content is needed, write Markdown first, then use `md-to-html-doc` to produce HTML.
92
- 5. Verify the final `.harness/` tree is complete.
86
+ 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.
87
+ 2. If no language preference is found, match the language of the current conversation.
88
+ 3. All generated files in `.harness/` must use the same language consistently.
package/skills/harness-update-spec/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: harness-update-spec
3
- description: Analyze an existing project's .harness/ specs against the current codebase, identify incremental updates or missing specs, and propose focused changes without regenerating everything from scratch.
3
+ description: Analyze and incrementally update an existing project's .harness/ specs against the current codebase. Use when the codebase has changed and .harness/ content may be stale, or when the user wants to check spec freshness.
4
4
  ---
5
5
 
6
6
  # Harness Update Spec
@@ -41,7 +41,7 @@ Prefer CodeGraph when it is available.
41
41
 
42
42
  ### 3. Derive a diff matrix
43
43
 
44
- Map detected changes to spec targets:
44
+ Map detected changes to spec targets. These are reference mappings — create new files when the change doesn't fit an existing one.
45
45
 
46
46
  | Change type | Likely spec target |
47
47
  | --- | --- |
@@ -73,15 +73,13 @@ When updating:
73
73
  3. Keep internal references inside `.harness/` consistent after edits.
74
74
  4. Re-run a quick file list check to ensure the directory remains coherent.
75
75
 
76
- ## Content Routing
76
+ ## Language
77
77
 
78
- Reuse the same content-routing rules as `harness-init`:
78
+ Before generating or updating any content, determine the output language using the same rules as `harness-init`:
79
79
 
80
- - Project identity goes to `index/project-profile.md`.
81
- - Data flow and external runtime semantics go to `guides/backend.md`.
82
- - High-risk chains and boundaries go to `rules/architecture.md`.
83
- - Decisions and tradeoffs go to `decisions/`.
84
- - Historical pitfalls, regressions, and patterns go to `memory/`.
80
+ 1. Read the project's `CLAUDE.md` (or `.claude/CLAUDE.md`) if it exists. If it declares a language preference, follow that.
81
+ 2. If no preference is found, match the language of the current conversation.
82
+ 3. All generated files in `.harness/` must use the same language consistently and match the language of existing `.harness/` files.
85
83
 
86
84
  ## Human Docs
87
85