メニュー
Step 4 of the Weft TDD workflow. Use after /type-tests: writes co-located *.test.ts unit tests against the mocked surface, covering every acceptance criterion, error path, and edge case, then runs them and confirms they FAIL (red phase) before handing off to /implement.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Step 7 of the Weft TDD workflow. Use after /e2e: self-reviews the diff via the code-review skill (medium effort; high when packages/core or packages/dom public API is touched) plus a spec-conformance check, then fixes or explicitly rejects every finding and re-validates until clean. Hard gate: no commit until the review is clean. Named review-step to avoid the built-in /review (GitHub PR review).
Step 8 of the Weft TDD workflow. Use after /review-step is clean: full documentation sweep of everything touched, JSDoc on changed exports, specs.md sync, docs/ pages, package READMEs, example readme.md files. Prose docs are written by the weft-docs-author agent; JSDoc and specs.md sync by the main thread. Hard gate: no commit until docs are complete, then branch + PR (never push main).
Step 6 of the Weft TDD workflow. Use after /implement is green: writes *.browser.test.ts real-browser tests (Vitest browser mode + Playwright via vp run test:browser). Mandatory for every touched examples/* app; for package features only when behavior is browser-observable, otherwise records an explicit skip in specs.md.
Manage Weft's Effect 4 beta dependency: bump the tested floor, fix a red bump PR, keep peer ranges/docs/catalog in sync, and verify claims against the installed effect dist. Use for any effect version bump, peer-range question, or upstream beta breakage.
Step 5 of the Weft TDD workflow. Use after /unit-test's red phase: replaces the declare mocks with real code in-place, enforces signature parity with the mock surface, and loops vp check --fix → vp run check → vp run test until green. Finishes with graphify update.
Step 2 of the Weft TDD workflow. Use after /spec has produced an approved specs.md: writes the feature's complete API surface as declare-based mocks in the real source file location, to be replaced in-place by /implement. Refuses to run if the co-located specs.md is missing.
| name | unit-test |
| description | Step 4 of the Weft TDD workflow. Use after /type-tests: writes co-located *.test.ts unit tests against the mocked surface, covering every acceptance criterion, error path, and edge case, then runs them and confirms they FAIL (red phase) before handing off to /implement. |
Write the feature's unit tests against the mock surface, then prove they fail before any implementation exists.
/type-tests (test file written, or explicit skip recorded)./implement.vp run test executed, every new test failing. A new test that passes against declare mocks is a test bug and must be fixed before handoff.Read the spec. Tests are written against the acceptance criteria in the co-located specs.md and the mocked API surface. Nothing else.
Write co-located tests (feature.ts → feature.test.ts). __tests__/ directories are allowed for compound/integration tests and shared fixtures/helpers.
Naming: describe for grouping, it/test for cases. Test case names must match or reference acceptance criteria from specs.md. A reviewer should be able to trace every criterion to a test by name.
Coverage requirements (all mandatory):
specs.md.Effect testing: use Effect testing utilities for Effect code (e.g. Effect.runPromise/test clock/TestContext as appropriate). Follow repo idioms: pipe(effect, ...), specific imports, no import * as X.
Red phase (mandatory):
vp run test (never bare vp test: the pack rule).declare mocks have no runtime implementation, so failures are expected; a passing new test is vacuous (asserting nothing, or not exercising the surface). Fix the test.Hand off. Next step is /implement.
/spec + /mock first, then re-enter here./e2e (*.browser.test.ts files are excluded from vp run test).