create-harness-vibe-coding 0.6.3 → 0.6.4

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/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 `Harness/PLAN.md` 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.
-
-## PLAN.md Updates
-
-Update `Harness/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/.claude/skills/wf-browser/SKILL.md

@@ -76,6 +76,36 @@ If you see `UnicodeEncodeError: 'gbk' codec can't encode character`, the install
 set PYTHONIOENCODING=utf-8
 ```
 
+### Windows Daemon Patches
+
+Browser Use v0.13.1 has two known issues on Windows that are auto-patched on install. If `browser-use open` fails with "Failed to start daemon" or socket timeout, re-apply:
+
+```bash
+python -c "
+import browser_use.skill_cli.main as m
+p = m.__file__
+c = open(p, encoding='utf-8').read()
+# Patch 1: auto-clean stale state on dead PID
+c = c.replace(
+    'probe = _probe_session(session)\n\n\t# Socket reachable',
+    'probe = _probe_session(session)\n\n\t# Auto-clean stale state\n\tif not probe.socket_reachable and not probe.pid_alive and probe.phase:\n\t\t_clean_session_files(session)\n\t\tprobe = _probe_session(session)\n\n\t# Socket reachable'
+)
+# Patch 2: auto-recover from stale session instead of erroring
+c = c.replace(
+    \"f'Error: Session {session!r} is alive (phase={probe.phase}) but socket unreachable.\",\"
+    \"f'Warning: Session {session!r} has stale state (phase={probe.phase}), auto-cleaning...\",\"
+)
+c = c.replace(
+    \"sys.exit(1)\n\n\t\telif probe.phase == 'shutting_down'\",
+    \"_terminate_pid(probe.pid)\n\t\t\t_clean_session_files(session)\n\n\t\telif probe.phase == 'shutting_down'\"
+)
+# Patch 3: extend daemon startup timeout (15s -> 30s)
+c = c.replace('deadline = time.time() + 15', 'deadline = time.time() + 30')
+open(p, 'w', encoding='utf-8').write(c)
+print('Patches applied')
+"
+```
+
 ### Requirements
 
 | Requirement | Version | Check |

package/templates/optional/skills/browser-e2e/docs/workflows/browser-e2e.md

@@ -46,7 +46,7 @@ If `browser-use` is not installed, fall back to:
 
 ## Integration Points
 
-- **wf-mode**: references this file at line 16 and 42 of `.claude/skills/wf-mode/SKILL.md`
+- **WF mode**: when browser-visible changes are made, follow the evidence contract in `Harness/WF.md#Browser And API Evidence`
 - **wf-browser**: the `/wf-browser` slash command loads this workflow + the skill via `.claude/commands/wf-browser.md`
 - **MEMORY.md**: registered as optional workflow skill
 - **README.md**: routing table row "Browser E2E testing or automation" → browser-e2e

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/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.
-- `Harness/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.
-
-## PLAN.md Updates
-
-Update `Harness/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/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.
-- `Harness/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.
-
-## PLAN.md Updates
-
-Update `Harness/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/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.
-- `Harness/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.
-
-## PLAN.md Updates
-
-Update `Harness/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/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.
-- `Harness/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.
-
-## PLAN.md Updates
-
-Update `Harness/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.

package/templates/common/.claude/skills/harness-build-loop/SKILL.md

@@ -1,23 +0,0 @@
----
-name: harness-build-loop
-description: Use for implementation, review, debugging, verification, and closing a feature.
----
-
-# Harness Build Loop
-
-Load:
-
-- `Harness/agent-workflow.md`
-- `Harness/subagents.md` when more than one agent, reviewer, or recovery pass is useful
-- `Harness/dispatch.md` when more than one agent is useful
-- `Harness/PROGRESS.md`
-- `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md` when available
-- current feature doc if present
-
-Follow:
-
-```text
-acceptance criteria -> failing test/manual check -> implementation -> verify -> review -> docs sync
-```
-
-Close only with recorded verification evidence.

package/templates/common/.claude/skills/harness-context/SKILL.md

@@ -1,26 +0,0 @@
----
-name: harness-context
-description: Use before spawning subagents, splitting work, or when context is growing.
----
-
-# Harness Context
-
-Load:
-
-- `Harness/subagents.md`
-- `Harness/context-loading.md`
-- `Harness/dispatch.md` when more than one agent is useful
-- `Harness/PROGRESS.md`
-- `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md` when available
-- current feature doc if present
-
-For each subagent or bounded pass, provide:
-
-- role
-- task
-- mode
-- read boundary
-- write boundary
-- dependency
-- injected docs
-- return format

package/templates/common/.claude/skills/harness-lifecycle/SKILL.md

@@ -1,20 +0,0 @@
----
-name: harness-lifecycle
-description: Use for raw ideas, vague product requests, 0-1 planning, PRD work, scope decisions, or feedback loops.
----
-
-# Harness Lifecycle
-
-Load:
-
-- `Harness/lifecycle.md`
-- `Harness/research/PRD.md`
-- `Harness/PROGRESS.md`
-- `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md` when available
-
-Output:
-
-- current phase
-- blocking questions or recorded assumptions
-- next artifact to fill
-- gate before coding

package/templates/common/.claude/skills/harness-research/SKILL.md

@@ -1,30 +0,0 @@
----
-name: harness-research
-description: Use for market, product, stack, dependency, API, pricing, legal, security, or open-source research before PRD or architecture decisions.
----
-
-# Harness Research
-
-Load:
-
-- `Harness/research/README.md`
-- `Harness/research/research-results.md`
-- `Harness/PROGRESS.md`
-- `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md` when available
-
-Define:
-
-- research question
-- decision needed
-- source boundaries
-- tool choice: local / GitHub / Tavily / TinyFish / built-in web search / user-provided sources
-- fallback when the preferred tool is unavailable
-- return format
-
-Return:
-
-- queries and tools used
-- sources with links and source type
-- adopted / rejected / watch decisions
-- risks and unknowns
-- patch-ready `Harness/research/research-results.md` update

package/templates/common/.claude/skills/harness-router/SKILL.md

@@ -1,16 +0,0 @@
----
-name: harness-router
-description: Use at the start of any task, or when unsure which harness document applies. Keeps context small by routing to one primary doc.
----
-
-# Harness Router
-
-1. Read `Harness/README.md`.
-2. Identify the current situation from "Load By Task".
-3. Apply routing priority before loading extra files:
-   - `/wf`, `wf mode`, `workflow mode`, `wk mode`, long, difficult, uncertain, repeated-failure, migration, architecture-heavy, browser-visible, or broad multi-agent implementation work routes to `wf-mode` first.
-   - Bounded subagent-only coordination routes to `subagent-orchestrator`.
-4. Load only the listed primary doc(s). Let `wf-mode` decide when to load subagent docs.
-5. If the task grows, update `Harness/tasks/<task-id>/PROGRESS.md` and use `harness-context`.
-
-Do not bulk-read `Harness/`.

package/templates/common/.claude/skills/wf-mode/SKILL.md

@@ -1,55 +0,0 @@
----
-name: wf-mode
-description: Use for /wf, wf mode, workflow mode, wk mode, long difficult tasks, multi-file or multi-agent work, low-confidence decisions, repeated failures, migrations, architecture-heavy changes, browser-visible work, or any task that needs exploration -> second plan -> implementation -> review -> verification -> recovery.
----
-
-# WF Mode
-
-Load:
-
-- `Harness/WF.md`
-- `Harness/PROGRESS.md`
-- `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md` when active
-- `Harness/agent-workflow.md` when implementation, review, or verification starts
-- `Harness/subagents.md`, `Harness/dispatch.md`, and `Harness/context-loading.md` immediately for explicit WF/WK mode; otherwise only when coordinating subagents or bounded role passes
-- current feature doc when one exists
-- `Harness/workflows/browser-e2e.md` when browser-visible behavior is affected and the workflow is installed
-
-Follow:
-
-```text
-intake + 95% confidence gate
--> parallel read-only exploration
--> synthesis and second plan
--> failing test or manual check
--> bounded implementation
--> review
--> verification
--> debugger recovery loop when verification fails (dispatch context-master then memory-master, or use /wf-learn)
--> context-master session analysis + knowledge extraction
--> memory-master consolidation
--> close with evidence
-```
-
-Rules:
-
-- Update `Harness/tasks/<task-id>/PROGRESS.md#Heartbeat` before long commands, after failures, before handoff, and at closeout.
-- Explicit `/wf`, `wf mode`, `workflow mode`, or `wk mode` MUST use `subagent-orchestrator` and spawn at least 3 distinct subagents from `.claude/agents/` before second planning.
-- Use the 7:3 collaboration bias from `Harness/WF.md`: default to multi-agent collaboration for substantial work; use solo mode only for clearly small/local tasks outside explicit WF/WK mode.
-- Use `subagent-orchestrator` and `Harness/subagents.md` when the task has broad reading, cross-layer impact, independent review needs, or repeated failures.
-- Subagents return findings and PLAN patch suggestions. Only the main agent writes to task PROGRESS.md and PLAN.md.
-- If subagents are unavailable, emulate the same roles as separate bounded passes.
-- Do not claim browser/UI acceptance without real-browser evidence from Chrome DevTools, CDP, Playwright, or documented manual browser checks.
-- If `Harness/workflows/browser-e2e.md` is not installed, use `Harness/WF.md#Browser And API Evidence` as the fallback evidence contract or ask the user before adding the optional workflow.
-- Before closeout, dispatch `context-master` then `memory-master` (or use `/wf-learn`) to extract and consolidate lessons. Do not skip — the auto-trigger is unreliable; make this a mandatory gate.
-
-Return:
-
-- changed files
-- agents or bounded passes used
-- memory-master / context-master dispatches
-- commands run
-- browser/API evidence when applicable
-- review findings
-- remaining risks
-- updated heartbeat status