菜单
Use for rule-engine and domain logic tests—VX-01~12 cross-consistency, W-EPC-01~17 linter, epc-coverage computeCoverage, deriveEpcSteps ordering. Table-driven; one positive and one negative case per rule minimum.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Goal-Loop methodology for multi-step agent work: strategy exploration, GOAL/GOALS/REPORT files, sub-goal state machine, iteration budgets, rollback, and decision logs. Use when the user asks for Goal-Loop, Goal Kit, GOAL.md, GOALS.md, REPORT.md, .hermes planning, multi-phase delivery with checkpoints, or structured goal decomposition before execution.
Use for tests/e2e smoke flows—ModelingWorkspace, business chain navigation, C workspace panels, derive/apply EPC. Tag @smoke; use waitFor; never mix vi.useFakeTimers with waitFor.
Use for tests/integration—React components with @testing-library/react, ScenarioWorkspace, panels, element-library. Focus on testids, tabs, empty states, and store wiring without full E2E.
Use before Coding (Unit step 3)—translate Unit Spec AC into Testing Cases with file paths, TC IDs, and pass/fail scenarios. Must complete before any production code for the Unit.
Use when orchestrating a US/Unit test effort—assigning subagents, defining exit criteria, and signing off only with fresh verification evidence. Test Lead does not write all tests; it plans, dispatches, and gates.
Use for tests/unit and store integration—pure functions (lib/*), Zustand store getters, and helpers. RED-GREEN with vitest; no React unless unavoidable.
| name | domain-rule-tester |
| description | Use for rule-engine and domain logic tests—VX-01~12 cross-consistency, W-EPC-01~17 linter, epc-coverage computeCoverage, deriveEpcSteps ordering. Table-driven; one positive and one negative case per rule minimum. |
业务规则即测试矩阵。 每条规则至少 1 正例 + 1 负例（或门禁空结果）。
| 域 | 文件 | 规则 |
|---|---|---|
| VX | epc-cross-consistency.spec.ts | VX-01~12 |
| W-EPC | business-epc-linter.spec.ts | W-EPC-01~17 |
| VM | epc-coverage.spec.ts | TC01–TC08 |
| 推导 | epc-derivation.spec.ts | E3 首尾、维度顺序 |
it('VX-09: trigger phrase without matching action → error', () => {
const issues = validateCrossConsistency(input).filter(i => i.code === 'VX-09');
expect(issues).toHaveLength(1);
expect(issues[0].severity).toBe('error');
});
it('VX-09: matching action → no issue', () => {
expect(validateCrossConsistency(input).filter(i => i.code === 'VX-09')).toHaveLength(0);
});
makeRecord, baseInput, step, makeMeta — 保持与 epc-cross-consistency.spec.ts 一致usageRef(epcId, stepId, scenarioId) — coverage store 测试confirmModule + saveModuleDraft — 确认快照后再 lintvalidateCrossConsistency / computeCoverage 空报告[] / empty reportnpx vitest run tests/unit/epc-cross-consistency.spec.ts # 28
npx vitest run tests/unit/business-epc-linter.spec.ts # 42
npx vitest run tests/unit/epc-coverage.spec.ts
npx vitest run tests/unit/epc-derivation.spec.ts
codetest-driven-developmentsystematic-debuggingdocs/.../testing-cases.md 对齐