create-harness-vibe-coding 0.8.8 → 0.8.9

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

@@ -3,19 +3,21 @@
 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 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, newest first:
+Entry format (compact, default no date):
 
 ```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.
+- When <scenario>: <rule>. Avoid <over-application>. Signals: <signals>.
 ```
 
-Do not record ordinary chat. If the preference is ambiguous, ask before writing it. Never store secrets.
+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/optional/catalog.json

@@ -73,6 +73,14 @@
       "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",

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.

package/templates/optional/skills/browser-e2e/.opencode/commands/wf-browser.md

@@ -0,0 +1,15 @@
+---
+description: Run AI-driven browser automation and E2E testing via the wf-browser skill
+---
+
+# /wf-browser
+
+This is a **workflow command**, not a direct command. Do not execute it as a
+static help or script command.
+
+1. Load `CLAUDE.md`, `Harness/MEMORY.md` (index only per Memory Preflight), then `Harness/README.md`.
+2. Execute per the skill adapter `.claude/skills/wf-browser/SKILL.md` (mirror: `.agents/skills/wf-browser/SKILL.md`).
+3. Do not duplicate the workflow here. The skill adapter and `Harness/workflows/browser-e2e.md` are authoritative.
+
+If this runtime cannot invoke the skill directly, read
+`.claude/skills/wf-browser/SKILL.md` and follow it in place.

package/templates/optional/skills/github-pr-review/.claude/skills/github-pr-review/SKILL.md

@@ -1,40 +1,40 @@
----
-name: github-pr-review
-description: GitHub pull request review workflow using available GitHub CLI, local git diff, checks, and CI evidence.
----
-
-# GitHub PR Review
-
-## When To Use
-
-Use this skill when reviewing a GitHub pull request, responding to PR feedback, checking CI status, or summarizing review findings.
-
-## Docs To Load
-
-- `Harness/workflows/github-pr-review.md`
-- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
-- Repository contribution, test, and review guidelines.
-
-## Required Inputs
-
-- PR number, branch, or comparison range.
-- Review goal: bug hunt, approval readiness, CI diagnosis, or feedback response.
-- Expected test and check requirements.
-
-## Allowed Writes
-
-- Local files needed to address approved review feedback.
-- Review notes or evidence in existing docs only when requested.
-- Current task `tasks/<id>/PLAN.md` when tracking review work.
-
-## Output Format
-
-Return findings first by severity with file and line references, then open questions, tests/checks run, and change summary if edits were made.
-
-## PROGRESS.md & Task PLAN.md Updates
-
-Update `Harness/tasks/<task-id>/PLAN.md` only when the PR review is part of a tracked implementation plan.
-
-## dispatch.md Usage
-
-Use `Harness/dispatch.md` when independent review areas can be assigned separately, such as backend, frontend, and CI.
+---
+name: github-pr-review
+description: GitHub pull request review workflow using available GitHub CLI, local git diff, checks, and CI evidence.
+---
+
+# GitHub PR Review
+
+## When To Use
+
+Use this skill when reviewing a GitHub pull request, responding to PR feedback, checking CI status, or summarizing review findings.
+
+## Docs To Load
+
+- `Harness/workflows/github-pr-review.md`
+- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
+- Repository contribution, test, and review guidelines.
+
+## Required Inputs
+
+- PR number, branch, or comparison range.
+- Review goal: bug hunt, approval readiness, CI diagnosis, or feedback response.
+- Expected test and check requirements.
+
+## Allowed Writes
+
+- Local files needed to address approved review feedback.
+- Review notes or evidence in existing docs only when requested.
+- Current task `tasks/<id>/PLAN.md` when tracking review work.
+
+## Output Format
+
+Return findings first by severity with file and line references, then open questions, tests/checks run, and change summary if edits were made.
+
+## PROGRESS.md & Task PLAN.md Updates
+
+Update `Harness/tasks/<task-id>/PLAN.md` only when the PR review is part of a tracked implementation plan.
+
+## dispatch.md Usage
+
+Use `Harness/dispatch.md` when independent review areas can be assigned separately, such as backend, frontend, and CI.

package/templates/optional/skills/python-backend/.claude/skills/python-backend/SKILL.md

@@ -1,40 +1,40 @@
----
-name: python-backend
-description: Python backend workflow for API changes, service logic, FastAPI-style routes, and unittest or pytest verification.
----
-
-# Python Backend
-
-## When To Use
-
-Use this skill when changing Python API routes, service logic, persistence boundaries, background jobs, or backend tests.
-
-## Docs To Load
-
-- `Harness/workflows/python-backend.md`
-- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
-- Project backend README, API docs, dependency files, and test configuration.
-
-## Required Inputs
-
-- Target behavior, endpoint, service, or bug.
-- Existing test command and runtime setup.
-- Database, environment variable, or fixture constraints.
-
-## Allowed Writes
-
-- Python source, tests, fixtures, and backend docs in the task scope.
-- Local evidence artifacts such as test output snippets.
-- Current task `tasks/<id>/PLAN.md` when the task requires plan tracking.
-
-## Output Format
-
-Return files changed, API or behavior summary, tests run, important logs, migration/config notes, and remaining risks.
-
-## PROGRESS.md & Task PLAN.md Updates
-
-Update `Harness/tasks/<task-id>/PLAN.md` only when executing a tracked plan item or recording required validation evidence.
-
-## dispatch.md Usage
-
-Use `Harness/dispatch.md` for separable backend work such as API implementation, database changes, and test coverage.
+---
+name: python-backend
+description: Python backend workflow for API changes, service logic, FastAPI-style routes, and unittest or pytest verification.
+---
+
+# Python Backend
+
+## When To Use
+
+Use this skill when changing Python API routes, service logic, persistence boundaries, background jobs, or backend tests.
+
+## Docs To Load
+
+- `Harness/workflows/python-backend.md`
+- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
+- Project backend README, API docs, dependency files, and test configuration.
+
+## Required Inputs
+
+- Target behavior, endpoint, service, or bug.
+- Existing test command and runtime setup.
+- Database, environment variable, or fixture constraints.
+
+## Allowed Writes
+
+- Python source, tests, fixtures, and backend docs in the task scope.
+- Local evidence artifacts such as test output snippets.
+- Current task `tasks/<id>/PLAN.md` when the task requires plan tracking.
+
+## Output Format
+
+Return files changed, API or behavior summary, tests run, important logs, migration/config notes, and remaining risks.
+
+## PROGRESS.md & Task PLAN.md Updates
+
+Update `Harness/tasks/<task-id>/PLAN.md` only when executing a tracked plan item or recording required validation evidence.
+
+## dispatch.md Usage
+
+Use `Harness/dispatch.md` for separable backend work such as API implementation, database changes, and test coverage.

package/templates/optional/skills/ts-react-frontend/.claude/skills/ts-react-frontend/SKILL.md

@@ -1,43 +1,43 @@
----
-name: ts-react-frontend
-description: TypeScript React frontend workflow for components, state, routing, typecheck, tests, builds, and browser smoke evidence.
----
-
-# TypeScript React Frontend
-
-## When To Use
-
-Use this skill when changing React components, hooks, routes, client state, styling, build configuration, or frontend tests.
-For user-visible changes, typecheck, build, and unit tests are not enough; include real-browser smoke or screenshot evidence before claiming acceptance.
-
-## Docs To Load
-
-- `Harness/workflows/ts-react-frontend.md`
-- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
-- Existing frontend README, package scripts, design system, and test setup.
-
-## Required Inputs
-
-- Screen, component, or flow being changed.
-- Expected behavior and acceptance criteria.
-- Existing package manager and verification commands.
-- 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
-
-- Frontend source, styles, tests, and focused docs in task scope.
-- Generated evidence such as screenshots or test reports in existing artifact paths.
-- Current task `tasks/<id>/PLAN.md` when tracking a plan item.
-
-## Output Format
-
-Return changed files, UI behavior summary, commands run, browser or test evidence, and unresolved risks.
-Include selectors added or verified for CDP/Playwright/manual checks.
-
-## PROGRESS.md & Task PLAN.md Updates
-
-Update `Harness/tasks/<task-id>/PLAN.md` only when executing a tracked task or recording required validation evidence.
-
-## dispatch.md Usage
-
-Use `Harness/dispatch.md` when independent frontend tasks can run in parallel, such as components, tests, and browser checks.
+---
+name: ts-react-frontend
+description: TypeScript React frontend workflow for components, state, routing, typecheck, tests, builds, and browser smoke evidence.
+---
+
+# TypeScript React Frontend
+
+## When To Use
+
+Use this skill when changing React components, hooks, routes, client state, styling, build configuration, or frontend tests.
+For user-visible changes, typecheck, build, and unit tests are not enough; include real-browser smoke or screenshot evidence before claiming acceptance.
+
+## Docs To Load
+
+- `Harness/workflows/ts-react-frontend.md`
+- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
+- Existing frontend README, package scripts, design system, and test setup.
+
+## Required Inputs
+
+- Screen, component, or flow being changed.
+- Expected behavior and acceptance criteria.
+- Existing package manager and verification commands.
+- 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
+
+- Frontend source, styles, tests, and focused docs in task scope.
+- Generated evidence such as screenshots or test reports in existing artifact paths.
+- Current task `tasks/<id>/PLAN.md` when tracking a plan item.
+
+## Output Format
+
+Return changed files, UI behavior summary, commands run, browser or test evidence, and unresolved risks.
+Include selectors added or verified for CDP/Playwright/manual checks.
+
+## PROGRESS.md & Task PLAN.md Updates
+
+Update `Harness/tasks/<task-id>/PLAN.md` only when executing a tracked task or recording required validation evidence.
+
+## dispatch.md Usage
+
+Use `Harness/dispatch.md` when independent frontend tasks can run in parallel, such as components, tests, and browser checks.

package/templates/optional/skills/ui-ux-review/.claude/skills/ui-ux-review/SKILL.md

@@ -1,40 +1,40 @@
----
-name: ui-ux-review
-description: Screenshot-driven UI and UX review for responsive behavior, accessibility, visual polish, and task clarity.
----
-
-# UI/UX Review
-
-## When To Use
-
-Use this skill when reviewing or changing user-facing screens, layouts, visual hierarchy, interaction states, accessibility, or responsive behavior.
-
-## Docs To Load
-
-- `Harness/workflows/ui-ux-review.md`
-- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
-- Existing design system, component, or style documentation.
-
-## Required Inputs
-
-- Screens, routes, or components under review.
-- Target users and primary tasks.
-- Breakpoints, themes, and accessibility expectations.
-
-## Allowed Writes
-
-- UI code and style files already in scope for the task.
-- Screenshot or audit artifacts in existing evidence folders.
-- Current task `tasks/<id>/PLAN.md` when the review is part of a tracked plan.
-
-## Output Format
-
-Return prioritized findings with file or screen references, evidence, recommended fixes, commands run, and residual risks.
-
-## PROGRESS.md & Task PLAN.md Updates
-
-Update current task `tasks/<id>/PLAN.md` only for tracked review tasks or when recording required evidence.
-
-## dispatch.md Usage
-
-Use `Harness/dispatch.md` only for independent review streams such as separate routes or breakpoints.
+---
+name: ui-ux-review
+description: Screenshot-driven UI and UX review for responsive behavior, accessibility, visual polish, and task clarity.
+---
+
+# UI/UX Review
+
+## When To Use
+
+Use this skill when reviewing or changing user-facing screens, layouts, visual hierarchy, interaction states, accessibility, or responsive behavior.
+
+## Docs To Load
+
+- `Harness/workflows/ui-ux-review.md`
+- `Harness/PROGRESS.md` and current task `tasks/<id>/PLAN.md`
+- Existing design system, component, or style documentation.
+
+## Required Inputs
+
+- Screens, routes, or components under review.
+- Target users and primary tasks.
+- Breakpoints, themes, and accessibility expectations.
+
+## Allowed Writes
+
+- UI code and style files already in scope for the task.
+- Screenshot or audit artifacts in existing evidence folders.
+- Current task `tasks/<id>/PLAN.md` when the review is part of a tracked plan.
+
+## Output Format
+
+Return prioritized findings with file or screen references, evidence, recommended fixes, commands run, and residual risks.
+
+## PROGRESS.md & Task PLAN.md Updates
+
+Update current task `tasks/<id>/PLAN.md` only for tracked review tasks or when recording required evidence.
+
+## dispatch.md Usage
+
+Use `Harness/dispatch.md` only for independent review streams such as separate routes or breakpoints.