create-harness-vibe-coding 0.8.7 → 0.8.9

package/templates/common/memory/routes.md

@@ -0,0 +1,43 @@
+# Memory Routes (L3 Route Index)
+
+> L3 = 详细 durable memory 路由索引。不是详细 memory，而是命中规则索引。
+> 详细 memory 文件按 scenario 匹配后按需加载。
+
+| id | signals | load | avoid |
+| --- | --- | --- | --- |
+| explicit-user-preference | remember, next time, 下次, 记住, 不要再, never, always, I prefer | user-corrections-preferences.md | current-task-only notes, transient mood |
+| hooks-only-wf-auto | hook, runtime hook, .claude/settings.json, .codex/hooks.json, WF-AUTO.md | agent-lessons-patterns.md#only-wf-auto-may-use-runtime-hooks | non-runtime docs, broad hook designs |
+| tool-repeat-failure | same command fails 3x, error signature repeats | tool-usage-reflections.md | one-off command failures |
+| review-debug-lesson | reusable review/debug/validation pattern | agent-lessons-patterns.md | task-specific logs |
+| startup-digest | new session, startup | startup-hints.md | full MEMORY.md index |
+| wf-closeout | /wf-learn, workflow closeout | all memory files via context-master -> memory-master | premature writes before extraction |
+
+## Matching Algorithm
+
+1. 把当前请求压缩成 **scenario pack**: intent / files / commands / signals / risk
+2. 与上表 Signals 列匹配，计算 score:
+   - +4 exact file/path match
+   - +3 explicit trigger phrase match
+   - +3 command/error signature match
+   - +2 workflow/mode match
+   - +1 keyword overlap
+   - -4 avoid match
+3. 阈值:
+   - score >= 5: 加载对应 memory entry/file section
+   - score 3-4: 只加载 route 摘要，必要时再读详细文件
+   - score < 3: 不加载
+4. Hard trigger 优先:
+   - 用户显式记忆语句 -> user-corrections-preferences.md
+   - 同命令失败 3 次 -> tool-usage-reflections.md
+   - review/debug/validation 可复用 lesson -> agent-lessons-patterns.md
+   - 修改 hook 相关文件 -> 加载 only-wf-auto hook lesson
+   - /wf-learn -> 完整 learning cycle
+
+## Load Logging
+
+每次加载 memory hints 需说明原因:
+```
+memory hints loaded: <id> because <signal>
+```
+
+不使用 embedding；保持稳定、可解释、省 token。

package/templates/common/memory/startup-hints.md

@@ -0,0 +1,32 @@
+# Startup Hints (L2 Memory Digest)
+
+> L2 = 启动极简 memory digest。每次 Harness 会话启动可读此文件，但不要加载完整 Harness/MEMORY.md 或 Harness/README.md。
+
+## Core Principles
+
+- Memory 是短场景规则，不是 task log。
+- 时间戳默认不要写；只有 superseded / conflict / time-sensitive 才写。
+- Broad runtime hooks 禁止；只有 `/wf-auto` bounded tick hook 例外。
+- Direct mode 不加载完整 Harness router，但 startup-hints 是允许的轻量启动提示。
+- 详细 memory 仍按 `MEMORY_PROTOCOL.md` 场景命中后再读。
+
+## Memory Candidate Detection
+
+用户说以下触发词时，识别为 memory candidate：
+
+**英文**: remember, next time, don't, do not, never, always, I prefer, I want you to
+**中文**: 记住, 下次, 以后, 不要再, 总是, 永远不要, 我偏好, 我希望你以后
+
+## When to Write Memory
+
+- **Explicit user preference**: 清晰、安全、场景明确时，可立即写入 L3，不必等 `/wf-learn`。
+- **Repeated implicit correction**: 同一假设/模式被纠正 2+ 次。
+- **Tool/command failure**: 同类工具/命令失败 3+ 次。
+- **Review/debug lesson**: 只有可复用、能防回归时才写。
+
+## What NOT to Write
+
+- Task log、过程总结、一次性情绪
+- Raw logs、transcripts
+- Secrets, tokens, credentials, private data
+- 临时偏好、无复用价值的笔记

package/templates/common/memory/tool-usage-reflections.md

@@ -1,21 +1,22 @@
-# Tool Usage Reflections
-
-Purpose: record repeated tool failures, better command patterns, and environment-specific fixes.
-
-Write here when:
-- The same tool/use pattern fails 3+ times in one task or across repeated tasks.
-- A more reliable command pattern replaces a brittle one.
-- The environment needs a durable fix, flag, path rule, shell syntax, or startup sequence.
-
-Entry format, newest first:
-
-```markdown
-## YYYY-MM-DD - Short Pattern Name
-
-- Trigger: what failed or repeated.
-- Better pattern: the command, tool usage, or sequence to use next time.
-- Evidence: command output summary, error text, or affected environment.
-- Scope: when this applies and when it does not.
-```
-
-Keep entries concise. Do not record secrets, credentials, private tokens, or one-off noise.
+# Tool Usage Reflections
+
+Purpose: record repeated tool failures, better command patterns, and environment-specific fixes.
+
+Write here when:
+- The same tool/use pattern fails 3+ times in one task or across repeated tasks.
+- A more reliable command pattern replaces a brittle one.
+- The environment needs a durable fix, flag, path rule, shell syntax, or startup sequence.
+
+Entry format (compact, default no date):
+
+```markdown
+- When <scenario>: <rule>. Avoid <over-application>. Signals: <signals>.
+```
+
+Only use date/timestamp headings when:
+- Entry supersedes prior conflicting guidance
+- Time-sensitive context (version, deprecation)
+- Conflict resolution needed
+
+Never record one-off command failures. Never store secrets, credentials, or private tokens.
+- Entry supersedes prior conflicting guidance: add date stamp.

package/templates/common/memory/user-corrections-preferences.md

@@ -1,21 +1,23 @@
-# User Corrections And Preferences
-
-Purpose: record repeated user corrections, durable preferences, and common-sense course corrections.
-
-Write here when:
-- The user says "remember", "never", "next time", "always", or "I prefer".
-- The user corrects the same assumption/pattern 2+ times.
-- A correction changes how future work should be scoped, explained, verified, or handed off.
-
-Entry format, newest first:
-
-```markdown
-## YYYY-MM-DD - Short Preference Name
-
-- Correction/preference: the durable instruction.
-- Trigger: what prompted the correction.
-- Apply when: future contexts where this should guide behavior.
-- Avoid: contexts where this should not be over-applied.
-```
-
-Do not record ordinary chat. If the preference is ambiguous, ask before writing it. Never store secrets.
+# User Corrections And Preferences
+
+Purpose: record repeated user corrections, durable preferences, and common-sense course corrections.
+
+Write here when:
+- The user says "remember", "never", "next time", "always", "I prefer", "记住", "下次", "不要再" etc.
+- Explicit, safe, scoped user preferences can be written immediately without `/wf-learn`.
+- The user corrects the same assumption/pattern 2+ times.
+- A correction changes how future work should be scoped, explained, verified, or handed off.
+
+Entry format (compact, default no date):
+
+```markdown
+- When <scenario>: <rule>. Avoid <over-application>. Signals: <signals>.
+```
+
+Only use date/timestamp headings when:
+- Entry supersedes prior conflicting guidance
+- Time-sensitive context (version, deprecation)
+- Conflict resolution needed
+
+Do not record ordinary chat, task logs, process summaries, one-time emotions, or transient preferences. If the preference is ambiguous, ask before writing it. Never store secrets.
+- Entry supersedes prior conflicting guidance: add date stamp.

package/templates/common/opencode.json

@@ -0,0 +1,19 @@
+{
+  "$schema": "https://opencode.ai/config.json",
+  "instructions": [".claude/rules/ecc/common.md"],
+  "permission": {
+    "bash": {
+      "*": "ask",
+      "rm -rf *": "deny",
+      "sudo *": "deny",
+      "curl *": "deny",
+      "wget *": "deny"
+    },
+    "read": {
+      "**/.env*": "deny",
+      "**/secrets/**": "deny",
+      "**/*.key": "deny",
+      "**/*.pem": "deny"
+    }
+  }
+}

package/templates/optional/catalog.json

@@ -1,41 +1,41 @@
-{
-  "skills": [
-    {
+{
+  "skills": [
+    {
       "id": "browser-e2e",
       "title": "Browser E2E",
       "description": "Mandatory real-browser smoke workflow using Playwright, Chrome DevTools/CDP, or documented manual evidence.",
       "files": ["skills/browser-e2e"],
       "tags": ["e2e", "browser", "playwright", "cdp"]
-    },
-    {
-      "id": "ui-ux-review",
-      "title": "UI/UX Review",
-      "description": "Screenshot-driven responsive, accessibility, and visual polish review workflow.",
-      "files": ["skills/ui-ux-review"],
-      "tags": ["ui", "ux", "accessibility", "review"]
-    },
-    {
-      "id": "github-pr-review",
-      "title": "GitHub PR Review",
-      "description": "GitHub CLI based PR diff, checks, review findings, and CI evidence workflow.",
-      "files": ["skills/github-pr-review"],
-      "tags": ["github", "pr", "review", "ci"]
-    },
-    {
-      "id": "python-backend",
-      "title": "Python Backend",
-      "description": "Python backend workflow for FastAPI or similar APIs with unittest or pytest verification.",
-      "files": ["skills/python-backend"],
-      "tags": ["python", "fastapi", "unittest", "pytest", "api"]
-    },
-    {
-      "id": "ts-react-frontend",
-      "title": "TypeScript React Frontend",
-      "description": "TypeScript React workflow for typecheck, component tests, builds, and browser smoke.",
-      "files": ["skills/ts-react-frontend"],
-      "tags": ["typescript", "react", "vite", "frontend"]
-    }
-  ],
+    },
+    {
+      "id": "ui-ux-review",
+      "title": "UI/UX Review",
+      "description": "Screenshot-driven responsive, accessibility, and visual polish review workflow.",
+      "files": ["skills/ui-ux-review"],
+      "tags": ["ui", "ux", "accessibility", "review"]
+    },
+    {
+      "id": "github-pr-review",
+      "title": "GitHub PR Review",
+      "description": "GitHub CLI based PR diff, checks, review findings, and CI evidence workflow.",
+      "files": ["skills/github-pr-review"],
+      "tags": ["github", "pr", "review", "ci"]
+    },
+    {
+      "id": "python-backend",
+      "title": "Python Backend",
+      "description": "Python backend workflow for FastAPI or similar APIs with unittest or pytest verification.",
+      "files": ["skills/python-backend"],
+      "tags": ["python", "fastapi", "unittest", "pytest", "api"]
+    },
+    {
+      "id": "ts-react-frontend",
+      "title": "TypeScript React Frontend",
+      "description": "TypeScript React workflow for typecheck, component tests, builds, and browser smoke.",
+      "files": ["skills/ts-react-frontend"],
+      "tags": ["typescript", "react", "vite", "frontend"]
+    }
+  ],
   "presets": {
     "web-app": ["ts-react-frontend", "browser-e2e", "ui-ux-review"],
     "fullstack": ["ts-react-frontend", "python-backend", "browser-e2e", "github-pr-review"]
@@ -72,6 +72,22 @@
       "installMode": "recommend-only",
       "url": "https://github.com/colbymchenry/codegraph",
       "tags": ["code graph", "architecture", "analysis"]
+    },
+    {
+      "id": "grill-me",
+      "title": "Grill Me",
+      "description": "External Matt Pocock skill for relentlessly interviewing a plan or design before implementation.",
+      "installMode": "recommend-only",
+      "url": "https://github.com/mattpocock/skills/tree/main/skills/productivity/grill-me",
+      "tags": ["planning", "design", "interview", "skills"]
+    },
+    {
+      "id": "oh-my-openagent",
+      "title": "oh-my-openagent",
+      "description": "Community OpenCode plugin harness: curated agents (Sisyphus/Prometheus/Hephaestus), lifecycle hooks, hash-anchored edits, and Team Mode. For OpenCode and Codex CLI.",
+      "installMode": "recommend-only",
+      "url": "https://github.com/code-yeongyu/oh-my-openagent",
+      "tags": ["opencode", "agents", "harness", "ecosystem"]
     }
   ]
 }

package/templates/optional/skills/browser-e2e/.claude/skills/browser-e2e/SKILL.md

@@ -1,42 +1,42 @@
----
-name: browser-e2e
-description: Mandatory real-browser smoke and end-to-end verification using Playwright, Chrome DevTools/CDP, or documented manual browser evidence.
----
-
-# Browser E2E
-
-## When To Use
-
-Use this skill when a change affects browser-visible behavior, navigation, forms, routing, layout, or client-side integration. Web/UI acceptance requires loading the app in a real browser before claiming the UI is done.
-
-## Docs To Load
-
-- `Harness/workflows/browser-e2e.md`
-- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
-- Existing project test, build, and run instructions.
-
-## Required Inputs
-
-- Target URL or command to start the app.
-- User flows or pages to verify.
-- Expected behavior and supported viewport/browser scope.
-- Selector contract: stable accessible labels/roles and `data-testid` hooks for critical inputs, buttons, filters, rows, empty/error/loading states, and other targetable UI states.
-
-## Allowed Writes
-
-- Browser test files in the project's existing test locations.
-- Evidence artifacts such as screenshots, traces, or reports in existing artifact folders.
-- Notes in current task plan when the active task asks for plan tracking.
-
-## Output Format
-
-Return changed files, commands run, browser evidence paths, verified flows, failures, and follow-up risks.
-Include the selectors used for CDP/Playwright/manual verification.
-
-## PROGRESS.md & Task PLAN.md Updates
-
-Update `Harness/tasks/<task-id>/PLAN.md` only when executing a tracked plan item or recording evidence requested by the current task.
-
-## dispatch.md Usage
-
-Use `Harness/dispatch.md` only when splitting independent browser checks across workers is explicitly useful.
+---
+name: browser-e2e
+description: Mandatory real-browser smoke and end-to-end verification using Playwright, Chrome DevTools/CDP, or documented manual browser evidence.
+---
+
+# Browser E2E
+
+## When To Use
+
+Use this skill when a change affects browser-visible behavior, navigation, forms, routing, layout, or client-side integration. Web/UI acceptance requires loading the app in a real browser before claiming the UI is done.
+
+## Docs To Load
+
+- `Harness/workflows/browser-e2e.md`
+- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
+- Existing project test, build, and run instructions.
+
+## Required Inputs
+
+- Target URL or command to start the app.
+- User flows or pages to verify.
+- Expected behavior and supported viewport/browser scope.
+- Selector contract: stable accessible labels/roles and `data-testid` hooks for critical inputs, buttons, filters, rows, empty/error/loading states, and other targetable UI states.
+
+## Allowed Writes
+
+- Browser test files in the project's existing test locations.
+- Evidence artifacts such as screenshots, traces, or reports in existing artifact folders.
+- Notes in current task plan when the active task asks for plan tracking.
+
+## Output Format
+
+Return changed files, commands run, browser evidence paths, verified flows, failures, and follow-up risks.
+Include the selectors used for CDP/Playwright/manual verification.
+
+## PROGRESS.md & Task PLAN.md Updates
+
+Update `Harness/tasks/<task-id>/PLAN.md` only when executing a tracked plan item or recording evidence requested by the current task.
+
+## dispatch.md Usage
+
+Use `Harness/dispatch.md` only when splitting independent browser checks across workers is explicitly useful.